[jira] [Updated] (PHOENIX-6831) Remove bogus Ant dependency from hive connector test util
[ https://issues.apache.org/jira/browse/PHOENIX-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6831: - Description: We're throwing an unchecked Exceptioon from Ant for no discernible reason. Replace it with IllegalArgumentException. > Remove bogus Ant dependency from hive connector test util > - > > Key: PHOENIX-6831 > URL: https://issues.apache.org/jira/browse/PHOENIX-6831 > Project: Phoenix > Issue Type: Task > Components: connectors, hive-connector >Affects Versions: connectors-6.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Labels: test > > We're throwing an unchecked Exceptioon from Ant for no discernible reason. > Replace it with IllegalArgumentException. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-6831) Remove bogus Ant dependency from hive connector test util
[ https://issues.apache.org/jira/browse/PHOENIX-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6831: - Summary: Remove bogus Ant dependency from hive connector test util (was: Remove Bogus Ant dependency from hive connector test util) > Remove bogus Ant dependency from hive connector test util > - > > Key: PHOENIX-6831 > URL: https://issues.apache.org/jira/browse/PHOENIX-6831 > Project: Phoenix > Issue Type: Task > Components: connectors, hive-connector >Affects Versions: connectors-6.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Labels: test > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-6831) Remove Bogus Ant dependency from hive connector test util
[ https://issues.apache.org/jira/browse/PHOENIX-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6831: - Labels: test (was: ) > Remove Bogus Ant dependency from hive connector test util > - > > Key: PHOENIX-6831 > URL: https://issues.apache.org/jira/browse/PHOENIX-6831 > Project: Phoenix > Issue Type: Task > Components: connectors, hive-connector >Affects Versions: connectors-6.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Labels: test > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (PHOENIX-6831) Remove Bogus Ant dependency from hive connector test util
Istvan Toth created PHOENIX-6831: Summary: Remove Bogus Ant dependency from hive connector test util Key: PHOENIX-6831 URL: https://issues.apache.org/jira/browse/PHOENIX-6831 Project: Phoenix Issue Type: Task Components: connectors, hive-connector Affects Versions: connectors-6.0.0 Reporter: Istvan Toth Assignee: Istvan Toth -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-6485) Clean up classpath in .py scripts
[ https://issues.apache.org/jira/browse/PHOENIX-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanuj Khurana updated PHOENIX-6485: --- Fix Version/s: 5.1.3 > Clean up classpath in .py scripts > - > > Key: PHOENIX-6485 > URL: https://issues.apache.org/jira/browse/PHOENIX-6485 > Project: Phoenix > Issue Type: Task >Reporter: Richárd Antal >Assignee: Richárd Antal >Priority: Major > Fix For: 5.2.0, 5.1.3 > > > Clean up classpath in .py scripts and replace all phoenix-client JARs with > phoenix-client-embedded + log4j backend jar -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-6752) Duplicate expression nodes in extract nodes during WHERE compilation phase leads to poor performance.
[ https://issues.apache.org/jira/browse/PHOENIX-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanuj Khurana updated PHOENIX-6752: --- Fix Version/s: 5.1.3 > Duplicate expression nodes in extract nodes during WHERE compilation phase > leads to poor performance. > - > > Key: PHOENIX-6752 > URL: https://issues.apache.org/jira/browse/PHOENIX-6752 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.0, 5.1.0, 4.16.1, 5.2.0 >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Critical > Fix For: 5.2.0, 5.1.3 > > Attachments: test-case.txt > > > SQL queries using the OR operator were taking a long time during the WHERE > clause compilation phase when a large number of OR clauses (~50k) are used. > The key observation was that during the AND/OR processing, when there are a > large number of OR expression nodes the same set of extracted nodes was > getting added. > Thus bloating the set size and slowing down the processing. > [code|https://github.com/apache/phoenix/blob/0c2008ddf32566c525df26cb94d60be32acc10da/phoenix-core/src/main/java/org/apache/phoenix/compile/WhereOptimizer.java#L930] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-6752) Duplicate expression nodes in extract nodes during WHERE compilation phase leads to poor performance.
[ https://issues.apache.org/jira/browse/PHOENIX-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanuj Khurana updated PHOENIX-6752: --- Fix Version/s: (was: 5.1.3) > Duplicate expression nodes in extract nodes during WHERE compilation phase > leads to poor performance. > - > > Key: PHOENIX-6752 > URL: https://issues.apache.org/jira/browse/PHOENIX-6752 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.0, 5.1.0, 4.16.1, 5.2.0 >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Critical > Fix For: 5.2.0 > > Attachments: test-case.txt > > > SQL queries using the OR operator were taking a long time during the WHERE > clause compilation phase when a large number of OR clauses (~50k) are used. > The key observation was that during the AND/OR processing, when there are a > large number of OR expression nodes the same set of extracted nodes was > getting added. > Thus bloating the set size and slowing down the processing. > [code|https://github.com/apache/phoenix/blob/0c2008ddf32566c525df26cb94d60be32acc10da/phoenix-core/src/main/java/org/apache/phoenix/compile/WhereOptimizer.java#L930] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-6454) Add feature to SchemaTool to get the DDL in specification mode
[ https://issues.apache.org/jira/browse/PHOENIX-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanuj Khurana updated PHOENIX-6454: --- Fix Version/s: 5.1.3 > Add feature to SchemaTool to get the DDL in specification mode > -- > > Key: PHOENIX-6454 > URL: https://issues.apache.org/jira/browse/PHOENIX-6454 > Project: Phoenix > Issue Type: Improvement >Reporter: Swaroopa Kadam >Assignee: Swaroopa Kadam >Priority: Major > Fix For: 4.17.0, 5.2.0, 5.1.3 > > > Currently, SchemExtractionTool uses PTable representation to get the > effective DDL on the cluster. > Rename SchemaExtractionTool to SchemaTool, add a feature that accepts create > DDL and alter DDL to give effective DDL without using PTable implementation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-6665) PreparedStatement#getMetaData() fails on parametrized "select next ? values for SEQ"
[
https://issues.apache.org/jira/browse/PHOENIX-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tanuj Khurana updated PHOENIX-6665:
---
Fix Version/s: 5.1.3
(was: 5.13)
> PreparedStatement#getMetaData() fails on parametrized "select next ? values
> for SEQ"
> -
>
> Key: PHOENIX-6665
> URL: https://issues.apache.org/jira/browse/PHOENIX-6665
> Project: Phoenix
> Issue Type: Bug
> Components: core
>Affects Versions: 5.2.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 4.17.0, 5.2.0, 4.16.2, 5.1.3
>
>
>
> {code:java}
> PreparedStatement nextStmt = conn.prepareStatement("SELECT NEXT ? VALUES FOR
> SEQ_TABLE");
> nextStmt.getMetaData();{code}
> Fails.
> According to the PreparedStatement javadoc, this should work:
> {quote}
> Because a {{PreparedStatement}} object is precompiled, it is possible to know
> about the {{ResultSet}} object that it will return without having to execute
> it. Consequently, it is possible to invoke the method {{getMetaData}} on a
> {{PreparedStatement}} object rather than waiting to execute it and then
> invoking the {{ResultSet.getMetaData}} method on the {{ResultSet}} object
> that is returned.
> {quote}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (PHOENIX-6771) Allow only "squash and merge" from GitHub UI
[ https://issues.apache.org/jira/browse/PHOENIX-6771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanuj Khurana updated PHOENIX-6771: --- Fix Version/s: 5.1.3 > Allow only "squash and merge" from GitHub UI > > > Key: PHOENIX-6771 > URL: https://issues.apache.org/jira/browse/PHOENIX-6771 > Project: Phoenix > Issue Type: Bug >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: connectors-6.0.0, 5.2.0, 5.1.3, queryserver-6.0.1, > thirdparty-2.0.1 > > > Github has three possible merging modes from the UI: > [https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges] > Of those, we want "squash and merge" 99% of the time, but sometimes other > methods are chosen, resulting in a less than ideal commit graph. > This is configurable via .asf.yml : > https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Mergebuttons > I propose that we disable the "merge" and "rebase" options for every Phoenix > repo via the .asf.yml file. > This only applies to the GitHub Web UI, the other methods can still be used > via the standard git operations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-6830) Upgrade reload4j due to XXE vulnerability
[ https://issues.apache.org/jira/browse/PHOENIX-6830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6830: - Fix Version/s: (was: 5.2.0) > Upgrade reload4j due to XXE vulnerability > - > > Key: PHOENIX-6830 > URL: https://issues.apache.org/jira/browse/PHOENIX-6830 > Project: Phoenix > Issue Type: Bug > Components: core >Reporter: Rajeshbabu Chintaguntla >Assignee: Rajeshbabu Chintaguntla >Priority: Major > Fix For: 5.1.3 > > > https://github.com/qos-ch/reload4j/issues/53 fixed in reload4j 1.2.22 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (PHOENIX-6830) Upgrade reload4j due to XXE vulnerability
Rajeshbabu Chintaguntla created PHOENIX-6830: Summary: Upgrade reload4j due to XXE vulnerability Key: PHOENIX-6830 URL: https://issues.apache.org/jira/browse/PHOENIX-6830 Project: Phoenix Issue Type: Bug Components: core Reporter: Rajeshbabu Chintaguntla Assignee: Rajeshbabu Chintaguntla Fix For: 5.2.0, 5.1.3 https://github.com/qos-ch/reload4j/issues/53 fixed in reload4j 1.2.22 -- This message was sent by Atlassian Jira (v8.20.10#820010)
