Skip to content
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

Can't run ParquetMR tests in IDEs #52

Open
asfimport opened this issue May 13, 2022 · 0 comments
Open

Can't run ParquetMR tests in IDEs #52

asfimport opened this issue May 13, 2022 · 0 comments

Comments

@asfimport
Copy link
Collaborator

asfimport commented May 13, 2022

ParquetMR contains a suite of self-tests. When one of those self-tests fails, it would be nice to be able to pull up the test in an IDE like IntelliJ. Then we can use the debugger and track down what the problem is. Unfortunately, this is impossible due to some unfortunate design choices.

If I open a test source file in IntelliJ and tell the IDE to run it, the first errors I get is a bunch of errors in org.apache.parquet.VersionTest, which evidently cannot find a bunch of symbols. If I hack VersionTest to no longer depend on those symbols, the next thing that happens is this error:

/home/theosib/packages/PARQUET-2069/parquet-mr/parquet-column/src/main/java/org/apache/parquet/io/MessageColumnIO.java:43:46
java: cannot find symbol
  symbol:   class IncrementallyUpdatedFilterPredicateBuilder
  location: package org.apache.parquet.filter2.recordlevel

Evidently, IncrementallyUpdatedFilterPredicateBuilder doesn't exist. Instead, it is auto-generated during the maven build process, but the code is stashed away somewhere where IntelliJ can't find it, and this is the end of the road.

If we want more people to be able to contribute to ParquetMR, I think we should work towards making it easier to debug.

Environment: In my case, IntelliJ IDEA.
Reporter: Timothy Miller / @theosib-amazon

Note: This issue was originally created as PARQUET-2147. Please see the migration documentation for further details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant