-
Notifications
You must be signed in to change notification settings - Fork 72
[Compiler plugin] join operations support #1139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
2a17323
to
bccd01e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice :)
|
||
internal data class ColumnMatchApproximation(val left: ColumnsResolver, val right: ColumnsResolver) | ||
internal data class ColumnMatchApproximation( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you give me a hint, what does Approximation mean. I see a lot in naming, but could not understand the idea
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In library we have ColumnMatch, and operations work with this class. We implement the same operation in compiler plugin, but we cannot cover 100% of usages, for example if some variable is used instead of constant, and we cannot refer to DataFrame - instead we have more limited PluginDataFrameSchema, etc. So it wouldn't be fair to just name it "ColumnMatch". Approximation indicates that it's "compile-time ColumnMatch". Something like this
} | ||
|
||
internal class ColumnListImpl<C>(override val columns: List<ColumnsResolver<C>>) : | ||
ColumnSet<C>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wow, formatting looks weird to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately this is the only way the linter allows it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The implementation is clear for me, but I'm not sure that all required test paths are covered, could you please answer
bccd01e
to
9440640
Compare
In first commit i adapted
ColumnMatch
andColumnList
to embed them into compiler plugin column resolving mechanismNew util functions designed to make sure all column names generated by compiler plugin in join are exactly as in runtime, and make sure there are no missing columns. They can however sometimes have nullability where runtime narrows the type to non-nullable