[
https://issues.apache.org/jira/browse/PHOENIX-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser reassigned PHOENIX-4814:
-----------------------------------
Assignee: Josh Elser
> performance.py fails with "Error: Invalid or corrupt jarfile"
> -------------------------------------------------------------
>
> Key: PHOENIX-4814
> URL: https://issues.apache.org/jira/browse/PHOENIX-4814
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.0
> Reporter: Albert Chu
> Assignee: Josh Elser
> Priority: Major
>
> I recently hit
> {noformat}
> Error: Invalid or corrupt jarfile /var/tmp/achu/data_ylzK6q.csv
> {noformat}
> with the apache-phoenix-4.14.0-HBase-1.2/1.3/1.4-bin packages released.
> But I did NOT hit it with apache-phoenix-4.14.0-HBase-1.1-bin release.
> I noticed issue PHOENIX-4510 introduced a fix related to this error message
> and noticed that the change in that fix did not propogate into each release
> of 4.14.0. It did not get into the 4.14.0-HBase-1.1-bin release. Probably
> not a coincidence?
>
> {noformat}
> >grep PHOENIX_TESTS_JAR_PATTERN apache-phoenix-4.14.*/bin/phoenix_utils.py |
> >grep findFile
> apache-phoenix-4.14.0-HBase-1.1-bin/bin/phoenix_utils.py: testjar =
> findFileInPathWithoutRecursion(PHOENIX_TESTS_JAR_PATTERN,
> os.path.join(current_dir, ".."))
> apache-phoenix-4.14.0-HBase-1.2-bin/bin/phoenix_utils.py: testjar =
> findFileInPathWithoutRecursion(PHOENIX_TESTS_JAR_PATTERN,
> os.path.join(current_dir, "..", 'lib'))
> apache-phoenix-4.14.0-HBase-1.3-bin/bin/phoenix_utils.py: testjar =
> findFileInPathWithoutRecursion(PHOENIX_TESTS_JAR_PATTERN,
> os.path.join(current_dir, "..", 'lib'))
> apache-phoenix-4.14.0-HBase-1.4-bin/bin/phoenix_utils.py: testjar =
> findFileInPathWithoutRecursion(PHOENIX_TESTS_JAR_PATTERN,
> os.path.join(current_dir, "..", 'lib'))
> {noformat}
>
> PHOENIX-4510 says the patch was released for 4.13.0, but it does not appear
> to be applied in those releases either (and tests passed with 4.13.0 when
> they were released).
> I have not looked at this beyond this simple level, but perhaps the patch in
> PHOENIX-4510 is not the right fix?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
