Change type of KillStatement jobId #2344
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -509,10 +506,8 @@ public Object visitParameterExpression(ParameterExpression node, Object context) | |||
|
|
|||
| @Test | |||
| public void testKillJob() { | |||
| Statement stmt = SqlParser.createStatement("KILL '6a3d6fb6-1401-4333-933d-b38c9322fca7'"); | |||
There was a problem hiding this comment.
is there still one test that uses a string literal?
There was a problem hiding this comment.
Yes, KillAnalyzerTest.testAnalyzeKillJobWithLiteral
|
ack |
kovrus
force-pushed
the
r/kill-statement-parser
branch
from
3dd4644
to
fa6d64c
Compare
kovrus
added a commit
that referenced
this pull request
Jul 21, 2015
Change type of KillStatement jobId
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.