By the way, this should also be released with Java 7 because 1.8.x uses Java 7.
On Fri, Apr 20, 2018 at 9:35 AM, Ryan Blue <[email protected]> wrote: > I don't think we need to re-open the issues, but it would be good to link > them as blockers for the 1.8.3 release issue and update the Fix Version > once they're committed. That would help keep track of what goes in. > > I don't think we want PARQUET-852. This release is intended for a Spark > patch release, so we should be careful about what goes in and make sure the > changes are important bug fixes. This issue looks like a minor performance > improvement, so it probably isn't worth the risk. > > Have you gone through the 1.10.0 changes to see what other bug fixes > should be included? I think there was one about closing files that would be > useful. > > On Thu, Apr 19, 2018 at 11:32 PM, Gabor Szadovszky < > [email protected]> wrote: > >> Hi All, >> >> Zoltan and I are planning to do the maintenance release 1.8.3 of >> parquet-mr. I’ve created the usual JIRA for it: PARQUET-1277 < >> https://issues.apache.org/jira/browse/PARQUET-1277> >> We would like to backport PARQUET-1217 <https://issues.apache.org/jir >> a/browse/PARQUET-1217> and PARQUET-1246 <https://issues.apache.org/jir >> a/browse/PARQUET-1246>. >> >> What is the usual way of handing such backports in the JIRA? Simply use >> the same JIRA id and add the version 1.8.3 to these JIRAs? Should we >> re-open them? Or create separate backport JIRAs? >> >> We have found an existing change on the branch parquet-1.8.x: >> https://github.com/apache/parquet-mr/commit/d59b32a9120ad40e >> 2a9f6651b680e84dae1747a6 <https://github.com/apache/par >> quet-mr/commit/d59b32a9120ad40e2a9f6651b680e84dae1747a6>. This change is >> the fix of the “minor improvement” PARQUET-852 < >> https://issues.apache.org/jira/browse/PARQUET-852>. Do we want to add >> this change to a maintenance release? >> >> Regards, >> Gabor > > > > > -- > Ryan Blue > Software Engineer > Netflix > -- Ryan Blue Software Engineer Netflix
