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.
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
Detect multiple jars on the classpath when init plugin [databricks] #9654
Detect multiple jars on the classpath when init plugin [databricks] #9654
Changes from 31 commits
2f1fae2
0c5df62
742b508
47ef387
171c016
e29e37d
0441f53
ded091e
42fc474
6bbedfb
d9264d8
5c108bb
c2a0402
14c536d
b099358
74010e0
fd129c9
5e292c4
15022d7
28c8dcd
3dc12e4
14fe6fc
5dcc15f
08f4088
0ca06b5
c7ca0ad
a833c73
f5bd0c9
405bf05
7d11a4f
c4eef25
bf4477a
39e0b56
c3279f4
70b1247
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Not too easy to follow but I get it now. In the comment can you add an example of the submodule vs main dist artifact you are looking for.
However, now it looks like we NEVER will never find out where we put submodule jars for tests by accident?
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.
How about adding another config mode like RECURISIVE to detect all jars on classpath and print a warning log? Just need to skip this filter under that mode.
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.
What do you mean by RECURSIVE?
if RECURSIVE means going down a directory level inside a jar file, I think we already established that we should only look at the root entries
ending with
"!/" + propName
if RECURSIVE means including the check to all sub-module artitfact id prefixed with
rapids-4-spark-
I realize that we do not have a good story now that change of the version info file name to contain the artifact Id is not part of the PR. Let us defer this to the followup issue you were going to file.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.
Yes, I mean this way. I will add it to the follow-up issue too.