[
https://issues.apache.org/jira/browse/PHOENIX-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17788012#comment-17788012
]
Nihal Jain commented on PHOENIX-7116:
-------------------------------------
Phoenix [https://github.com/apache/phoenix/tree/5.1] does not have PHOENIX-6588
but the same was pushed to
[4.17.0|https://issues.apache.org/jira/issues/?jql=project+%3D+PHOENIX+AND+fixVersion+%3D+4.17.0]
and
[5.2.0|https://issues.apache.org/jira/issues/?jql=project+%3D+PHOENIX+AND+fixVersion+%3D+5.2.0]
Not sure if this was missed mistakenly or deliberately, created this Jira to
backport/discuss the same.
CC: [[email protected]], [~stoty]
> Backport "PHOENIX-6588 Update to phoenix-thirdparty 2.0.0" to branch 5.1
> ------------------------------------------------------------------------
>
> Key: PHOENIX-7116
> URL: https://issues.apache.org/jira/browse/PHOENIX-7116
> Project: Phoenix
> Issue Type: Improvement
> Components: core
> Environment: Phoenix-thirparty now includes the upstream 1.5.0
> release instead of a patched 1.4 release.
> The upstream 1.5.0 has the same option to fix parsing double quotes as the
> patched 1.4 used previously, but uses a different API to activate it.
> This is a breaking API change.
> Reporter: Nihal Jain
> Assignee: Nihal Jain
> Priority: Major
>
> In phoenix-thirdparty 1.1 we've added a patch to fix CLI-254 which has been
> plagueing Phoenix since forever.
> commons-cli 1.5.0 includes the same fix, but uses a different API to enable
> it.
> PHOENIX-6575 tracks the commons-cli update in phoenix-thirdparty, and this
> ticket tracks the API update in phoenix.
> This requires bumping the phoenix-thirdparty version as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
