hmm. that clean maven build is the first thing I do every day, , and did try it again here. I have a whole set of fish functions to make this easier https://github.com/steveloughran/engineering-proposals/blob/trunk/qualifying-an-SDK-upgrade.md#fish-functions-for-a-happier-maven
I think I'll modify the build to skip that parquet shading to see if that helps... On Thu, 5 Jun 2025 at 10:37, Cheng Pan <[email protected]> wrote: > I hit the exactly same issue yesterday, and got resolved after running > > ./mvnw clean install -DskipTests > > Not sure if it is caused by the recent versions of Intellij IDEA > change[1], the behavior is a little different when the > target/module-version.jar exists. > > [1] https://youtrack.jetbrains.com/issue/IDEA-93855 > > Thanks, > Cheng Pan > > > > > On Jun 5, 2025, at 02:40, Steve Loughran <[email protected]> > wrote: > > > > I'm trying to run a test through Intellij to identify why buffers aren't > > being released. But when I do this, > > > > java.lang.NoSuchMethodError: > 'shaded.parquet.org.apache.thrift.TFieldIdEnum > > org.apache.parquet.format.LogicalType.getSetField()' > > > > at > > > org.apache.parquet.format.converter.ParquetMetadataConverter.getLogicalTypeAnnotation(ParquetMetadataConverter.java:1291) > > at > > > org.apache.parquet.format.converter.ParquetMetadataConverter.buildChildren(ParquetMetadataConverter.java:2012) > > at > > > org.apache.parquet.format.converter.ParquetMetadataConverter.fromParquetSchema(ParquetMetadataConverter.java:1960) > > at > > > org.apache.parquet.format.converter.ParquetMetadataConverter.fromParquetMetadata(ParquetMetadataConverter.java:1790) > > at > > > org.apache.parquet.format.converter.ParquetMetadataConverter.readParquetMetadata(ParquetMetadataConverter.java:1749) > > at > > > org.apache.parquet.hadoop.ParquetFileReader.readFooter(ParquetFileReader.java:634) > > at > > > org.apache.parquet.hadoop.ParquetFileReader.<init>(ParquetFileReader.java:939) > > at > > > org.apache.parquet.hadoop.ParquetFileReader.<init>(ParquetFileReader.java:930) > > > > I've tried handing off the build to maven, but the same problem surfaces > > > > Is there a secret to this? it's clearly shaded dependency related, which > is > > always a source of trouble. But it is a missing method, not missing > class.. > > > > steve > >
