MODE-1985 Teiid DDL parser throws exception parsing column with object datatype #876
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
…t datatype Modified Teiid datatype parser to allow length on a type of "OBJECT." This is a new Teiid change.
|
Added the @rule and @SkipLongRunning tags to the new teiid sequencer test. |
|
Merged into the 'master' branch, and cherry-picked into the '3.3.x' branch. |
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.
Exception only occurred when the "OBJECT" data type had a length. Allowing a length to the "object" data type is a new requirement to the Teiid BNF. Changed TeiidDataTypeParser to now allow length for the data type of "OBJECT." Added a data type parser test and sequencer test to parse DDL attached to issue.