switch sample_mflix fixture config to use new boolean expression metadata #93
Conversation
This file contains hidden or 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
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.
These changes only affect integration tests and the preconfigured dev environment. The fixture metadata configures two MongoDB connectors: one using MongoDB's sample_mlfix sample data set, the other using a Chinook data set.
Updates object types and scalar types in metadata configuration for both connectors to use
BooleanExpressionTypeinstead ofObjectBooleanExpressionType.I also moved the scalar type metadata so that it is shared between the sample_mflix and chinook connectors. Now we are using the same set of scalar types with both connectors instead of having
Chinook_-prefixed types for the chinook connector.References NDC-381