Re: [VOTE] Release of Apache Phoenix 4.16.1 RC2

2021-05-14 Thread Viraj Jasani
Thanks Justin and Ankit. Ankit has already raised PR to revert this checkin
in LICENSE.

This RC (RC2) is anyways sunk as per the reason mentioned by Xinyi. On his
behalf, I have raised another RC (RC10) on another thread.
Ankit, once you confirm, I can either merge the PR in all active branches
and recreate RC (sink RC10) or we can take it up in subsequent release as
PR will be merged soon anyways, it’s upto you.


On Sat, 15 May 2021 at 9:36 AM, Justin Mclean  wrote:

> Hi,
>
> > Thanks Justin for checking the release and I agree with you. so my vote
> is
> > -1 (binding),  Let's fix the LICENSE file under PHOENIX-6471 and roll
> out a
> > new RC.
>
> I don't think these are major issues, you could just fix it in the next
> release if you wanted to, but up to you.
>
> Thanks,
> Justin
>


Re: [VOTE] Release of Apache Phoenix 4.16.1 RC2

2021-05-14 Thread Justin Mclean
Hi,

> Thanks Justin for checking the release and I agree with you. so my vote is
> -1 (binding),  Let's fix the LICENSE file under PHOENIX-6471 and roll out a
> new RC.

I don't think these are major issues, you could just fix it in the next release 
if you wanted to, but up to you.

Thanks,
Justin


[jira] [Assigned] (PHOENIX-6471) Revert PHOENIX-5387 to remove unneeded CPL 1.0 license

2021-05-14 Thread Ankit Singhal (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ankit Singhal reassigned PHOENIX-6471:
--

Assignee: Ankit Singhal

> Revert PHOENIX-5387 to remove unneeded CPL 1.0 license
> --
>
> Key: PHOENIX-6471
> URL: https://issues.apache.org/jira/browse/PHOENIX-6471
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.16.1
>Reporter: Ankit Singhal
>Assignee: Ankit Singhal
>Priority: Blocker
>
> As [~jmclean] pointed on release vote [1] and after checking the code , we 
> don't include any source or bundle the below dependency requiring CPL license 
> in any of the artifacts we distribute, so we shoud be avoiding it's 
> unnecessary mention in our LICENSE for both source and convenience binaries 
> as per the ASF policy [2][3]
> {code:java}
>  
> com.github.stefanbirkner
> system-rules
> 1.8.0
> 
>  {code}
> [1] 
> [https://lists.apache.org/x/thread.html/r903c814a13acf996309b9996262b14d85d219aaace22a39ea7233ef1@%3Cdev.phoenix.apache.org%3E]
> [2][https://www.apache.org/legal/resolved.html#category-b]
> [3][https://infra.apache.org/licensing-howto.html#guiding]
> FYI [~yanxinyi], [~vjasani]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: [VOTE] Release of Apache Phoenix 4.16.1 RC10

2021-05-14 Thread Ankit Singhal
-1 (binding), sorry Viraj but we need to fix PHOENIX-6471 as Justin pointed
out a licensing issue.


On Fri, May 14, 2021 at 11:22 PM Viraj Jasani  wrote:

> Here is my +1 (non-binding) vote.
>
> * Signature: ok
> * Checksum : ok
> * Rat check (1.8.0_171): ok
>  - mvn clean apache-rat:check
> * Built from source (1.8.0_171): ok
>  - mvn clean install  -DskipTests
> * Unit tests pass (1.8.0_171): ok (carry-forwarded from RC2)
>  - mvn clean package  && mvn verify  -Dskip.embedded
>
> Unit tests result carry-forwarded from 4.16.1RC2 as there is no additional
> changes included in this RC.
>
>
> On 2021/05/14 17:13:14, Viraj Jasani  wrote:
> > Please vote on this Apache phoenix release candidate,
> > phoenix-4.16.1RC10
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache phoenix 4.16.1
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 4.16.1RC10:
> >
> >   https://github.com/apache/phoenix/tree/4.16.1RC10
> >
> > Commit ID: 61c83f74fa555f79127193c9928d3720ed26a87b
> >
> > The release files, including signatures, digests, as well as CHANGES.md
> > and RELEASENOTES.md included in this RC can be found at:
> >
> >   https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.16.1RC10/
> >
> > Maven artifacts are available in a staging repository at:
> >
> >
> https://repository.apache.org/content/repositories/orgapachephoenix-1235/
> >
> > Artifacts were signed with the 1C8ADFD5 key which can be found in:
> >
> >   https://dist.apache.org/repos/dist/release/phoenix/KEYS
> >
> > To learn more about Apache phoenix, please see
> >
> >   https://phoenix.apache.org/
> >
> > Thanks,
> > Your Phoenix Release Manager
> >
>


Re: [VOTE] Release of Apache Phoenix 4.16.1 RC2

2021-05-14 Thread Ankit Singhal
Thanks Justin for checking the release and I agree with you. so my vote is
-1 (binding),  Let's fix the LICENSE file under PHOENIX-6471 and roll out a
new RC.

Sorry for the churn on the vote but we need to fix the licensing issues to
conform to ASF policy.


On Fri, May 14, 2021 at 2:11 PM Justin Mclean  wrote:

> Hi,
>
> > As the note in the LICENSE file mentions, the library is used as a binary
> > dependency, included via maven. We don't build or distribute the source
> of
> > the library ourselves.
>
> In that case it should not be mentioned in the LICENSE, only things that
> are bundled or included in the release need be mentioned in LICENSE.
>
> Thanks,
> Justin
>


[jira] [Created] (PHOENIX-6471) Revert PHOENIX-5387 to remove unneeded CPL 1.0 license

2021-05-14 Thread Ankit Singhal (Jira)
Ankit Singhal created PHOENIX-6471:
--

 Summary: Revert PHOENIX-5387 to remove unneeded CPL 1.0 license
 Key: PHOENIX-6471
 URL: https://issues.apache.org/jira/browse/PHOENIX-6471
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.16.1
Reporter: Ankit Singhal


As [~jmclean] pointed on release vote [1] and after checking the code , we 
don't include any source or bundle the below dependency requiring CPL license 
in any of the artifacts we distribute, so we shoud be avoiding it's unnecessary 
mention in our LICENSE for both source and convenience binaries as per the ASF 
policy [2][3]
{code:java}
 
com.github.stefanbirkner
system-rules
1.8.0

 {code}
[1] 
[https://lists.apache.org/x/thread.html/r903c814a13acf996309b9996262b14d85d219aaace22a39ea7233ef1@%3Cdev.phoenix.apache.org%3E]

[2][https://www.apache.org/legal/resolved.html#category-b]

[3][https://infra.apache.org/licensing-howto.html#guiding]

FYI [~yanxinyi], [~vjasani]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[VOTE] Release of phoenixdb 1.0.1 RC0

2021-05-14 Thread Istvan Toth
Hello Everyone,

This is a call for a vote on phoenixdb 1.0.1 RC0.

PhoenixDB is native Python driver for accessing Phoenix via Phoenix Query
Server.

This version contains the following improvements compared to the previous
1.0.0 release

- Restore default GSS OID to "SPNEGO" to improve compatibility
- Use HTTP sessions to handle cookies for sticky load balancer support

The source release consists of the contents of the python-phoenixdb
directory of the phoenix-queryserver repository.

The source tarball, including signatures, digests, etc can be found at:

https://dist.apache.org/repos/dist/dev/phoenix/python-phoenixdb-1.0.1.rc0/src/

Artifacts are signed with my "CODE SIGNING KEY":
825203A70405BC83AECF5F7D97351C1B794433C7

KEYS file available here:
https://dist.apache.org/repos/dist/dev/phoenix/KEYS


The hash and tag to be voted upon:
https://gitbox.apache.org/repos/asf?p=phoenix-queryserver.git;a=commit;h=d983b86a541c65938a4344f79b2dbe70c38ea905

https://gitbox.apache.org/repos/asf?p=phoenix-queryserver.git;a=tag;h=refs/tags/python-phoenixdb-1.0.1.rc0

The vote will be open for at least 72 hours. Please vote:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
Istvan


[jira] [Updated] (PHOENIX-6085) Remove duplicate calls to getSysMutexPhysicalTableNameBytes() during the upgrade path

2021-05-14 Thread Lars Hofhansl (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Hofhansl updated PHOENIX-6085:
---
Fix Version/s: 5.1.2

> Remove duplicate calls to getSysMutexPhysicalTableNameBytes() during the 
> upgrade path
> -
>
> Key: PHOENIX-6085
> URL: https://issues.apache.org/jira/browse/PHOENIX-6085
> Project: Phoenix
>  Issue Type: Improvement
>Affects Versions: 5.0.0, 4.15.0
>Reporter: Chinmay Kulkarni
>Assignee: Richárd Antal
>Priority: Minor
>  Labels: phoenix-hardening, quality-improvement
> Fix For: 4.17.0, 5.2.0, 5.1.2
>
> Attachments: PHOENIX-6085.4.x.v1.patch, PHOENIX-6085.master.v1.patch
>
>
> We already make this call inside 
> [CQSI.acquireUpgradeMutex()|https://github.com/apache/phoenix/blob/1922895dfe5960dc025709b04acfaf974d3959dc/phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java#L4220]
>  and then call writeMutexCell() which calls this again 
> [here|https://github.com/apache/phoenix/blob/1922895dfe5960dc025709b04acfaf974d3959dc/phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java#L4244].
>  
> We should move this to inside writeMutexCell() itself and throw 
> UpgradeInProgressException if required there to avoid unnecessary expensive 
> HBase admin API calls.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (PHOENIX-5346) SaltedIndexIT is flapping

2021-05-14 Thread Lars Hofhansl (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Hofhansl updated PHOENIX-5346:
---
Fix Version/s: (was: 5.2.0)
   (was: 4.17.0)

> SaltedIndexIT is flapping
> -
>
> Key: PHOENIX-5346
> URL: https://issues.apache.org/jira/browse/PHOENIX-5346
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.15.0
>Reporter: Lars Hofhansl
>Priority: Critical
>  Labels: disabled-test
>
> {code}
> [ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 14.042 s <<< FAILURE! - in org.apache.phoenix.end2end.index.SaltedIndexIT
> [ERROR] 
> testMutableTableIndexMaintanenceSaltedSalted(org.apache.phoenix.end2end.index.SaltedIndexIT)
>   Time elapsed: 4.661 s  <<< FAILURE!
> org.junit.ComparisonFailure: expected:<[y]> but was:<[x]>
>   at 
> org.apache.phoenix.end2end.index.SaltedIndexIT.testMutableTableIndexMaintanence(SaltedIndexIT.java:129)
>   at 
> org.apache.phoenix.end2end.index.SaltedIndexIT.testMutableTableIndexMaintanenceSaltedSalted(SaltedIndexIT.java:74)
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: [VOTE] Release of Apache Phoenix 4.16.1 RC10

2021-05-14 Thread Viraj Jasani
Here is my +1 (non-binding) vote.

* Signature: ok
* Checksum : ok
* Rat check (1.8.0_171): ok
 - mvn clean apache-rat:check 
* Built from source (1.8.0_171): ok
 - mvn clean install  -DskipTests
* Unit tests pass (1.8.0_171): ok (carry-forwarded from RC2)
 - mvn clean package  && mvn verify  -Dskip.embedded

Unit tests result carry-forwarded from 4.16.1RC2 as there is no additional 
changes included in this RC.


On 2021/05/14 17:13:14, Viraj Jasani  wrote: 
> Please vote on this Apache phoenix release candidate,
> phoenix-4.16.1RC10
> 
> The VOTE will remain open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache phoenix 4.16.1
> [ ] -1 Do not release this package because ...
> 
> The tag to be voted on is 4.16.1RC10:
> 
>   https://github.com/apache/phoenix/tree/4.16.1RC10
> 
> Commit ID: 61c83f74fa555f79127193c9928d3720ed26a87b
> 
> The release files, including signatures, digests, as well as CHANGES.md
> and RELEASENOTES.md included in this RC can be found at:
> 
>   https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.16.1RC10/
> 
> Maven artifacts are available in a staging repository at:
> 
>   https://repository.apache.org/content/repositories/orgapachephoenix-1235/
> 
> Artifacts were signed with the 1C8ADFD5 key which can be found in:
> 
>   https://dist.apache.org/repos/dist/release/phoenix/KEYS
> 
> To learn more about Apache phoenix, please see
> 
>   https://phoenix.apache.org/
> 
> Thanks,
> Your Phoenix Release Manager
> 


[VOTE] Release of Apache Phoenix 4.16.1 RC10

2021-05-14 Thread Viraj Jasani
Please vote on this Apache phoenix release candidate,
phoenix-4.16.1RC10

The VOTE will remain open for at least 72 hours.

[ ] +1 Release this package as Apache phoenix 4.16.1
[ ] -1 Do not release this package because ...

The tag to be voted on is 4.16.1RC10:

  https://github.com/apache/phoenix/tree/4.16.1RC10

Commit ID: 61c83f74fa555f79127193c9928d3720ed26a87b

The release files, including signatures, digests, as well as CHANGES.md
and RELEASENOTES.md included in this RC can be found at:

  https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.16.1RC10/

Maven artifacts are available in a staging repository at:

  https://repository.apache.org/content/repositories/orgapachephoenix-1235/

Artifacts were signed with the 1C8ADFD5 key which can be found in:

  https://dist.apache.org/repos/dist/release/phoenix/KEYS

To learn more about Apache phoenix, please see

  https://phoenix.apache.org/

Thanks,
Your Phoenix Release Manager


[jira] [Resolved] (PHOENIX-6470) Bump Tephra to 0.16.1 in 4.x

2021-05-14 Thread Istvan Toth (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth resolved PHOENIX-6470.
--
Fix Version/s: 4.16.2
   4.17.0
   Resolution: Fixed

> Bump Tephra to 0.16.1 in 4.x
> 
>
> Key: PHOENIX-6470
> URL: https://issues.apache.org/jira/browse/PHOENIX-6470
> Project: Phoenix
>  Issue Type: Improvement
>  Components: core, tephra
>Affects Versions: 4.16.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 4.17.0, 4.16.2
>
>
> In PHOENIX-6442 depends on Tephra 0.16.1 on master, and includes the version 
> bump.
> On 4.x, PHOENIX-6442 works with Tephra 0.16, so I didn't (actually forgot to) 
> bump Tephra to 0.16.1.
> However, for consistency's sake, we should upgrade to Tephra 0.16.1 in 4.x, 
> too. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Closed] (OMID-208) Pass additional options to omid.sh

2021-05-14 Thread Jira


 [ 
https://issues.apache.org/jira/browse/OMID-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richárd Antal closed OMID-208.
--
Resolution: Fixed

> Pass additional options to omid.sh
> --
>
> Key: OMID-208
> URL: https://issues.apache.org/jira/browse/OMID-208
> Project: Phoenix Omid
>  Issue Type: Task
>Reporter: Richárd Antal
>Assignee: Richárd Antal
>Priority: Major
>
> Make it possible to create an OMID_OPTS environment variable and use it when 
> running the omid.sh



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[GitHub] [phoenix-omid] richardantal merged pull request #94: OMID-208 Pass additional options to omid.sh

2021-05-14 Thread GitBox


richardantal merged pull request #94:
URL: https://github.com/apache/phoenix-omid/pull/94


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [phoenix-omid] richardantal opened a new pull request #94: OMID-208 Pass additional options to omid.sh

2021-05-14 Thread GitBox


richardantal opened a new pull request #94:
URL: https://github.com/apache/phoenix-omid/pull/94


   Change-Id: I3922f89d8723350b2c3b6e8ae36615e7ba6c2fe5


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[jira] [Created] (OMID-208) Pass additional options to omid.sh

2021-05-14 Thread Jira
Richárd Antal created OMID-208:
--

 Summary: Pass additional options to omid.sh
 Key: OMID-208
 URL: https://issues.apache.org/jira/browse/OMID-208
 Project: Phoenix Omid
  Issue Type: Task
Reporter: Richárd Antal
Assignee: Richárd Antal


Make it possible to create an OMID_OPTS environment variable and use it when 
running the omid.sh



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: [VOTE] Release of Apache Phoenix 4.16.1 RC2

2021-05-14 Thread Justin Mclean
Hi,

> As the note in the LICENSE file mentions, the library is used as a binary
> dependency, included via maven. We don't build or distribute the source of
> the library ourselves.

In that case it should not be mentioned in the LICENSE, only things that are 
bundled or included in the release need be mentioned in LICENSE.

Thanks,
Justin


[jira] [Updated] (PHOENIX-6419) Unused getResolverForQuery() in QueryCompiler.verifySCN()

2021-05-14 Thread Viraj Jasani (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani updated PHOENIX-6419:
--
Fix Version/s: (was: 4.16.1)
   4.16.2

> Unused getResolverForQuery() in QueryCompiler.verifySCN()
> -
>
> Key: PHOENIX-6419
> URL: https://issues.apache.org/jira/browse/PHOENIX-6419
> Project: Phoenix
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.1.0, 4.16.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Trivial
> Fix For: 4.17.0, 5.2.0, 5.1.2, 4.16.2
>
>
> in org.apache.phoenix.compile.QueryCompiler.verifySCN()
> we create a resolver that we don't use.
> {code:java}
> ColumnResolver resolver =
> FromCompiler.getResolverForQuery(select, conn);
> {code}
> AFAICT this has no side effects that we need, and should be removed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (PHOENIX-6427) Create sequence fails in lowercase schema

2021-05-14 Thread Viraj Jasani (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani updated PHOENIX-6427:
--
Fix Version/s: (was: 4.16.1)
   4.16.2

> Create sequence fails in lowercase schema
> -
>
> Key: PHOENIX-6427
> URL: https://issues.apache.org/jira/browse/PHOENIX-6427
> Project: Phoenix
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.1.0, 4.16.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 4.17.0, 5.2.0, 5.1.2, 4.16.2
>
>
> The following sequence:
> {noformat}
> CREATE SCHEMA "lower";
> create sequence "lower"."seq";
> {noformat}
> fails with a SchemaNotFoundException when namespace mapping is enabled.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (PHOENIX-6442) Phoenix should depend on the appropriate tephra-hbase-compat-x.y module

2021-05-14 Thread Viraj Jasani (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani updated PHOENIX-6442:
--
Fix Version/s: (was: 4.16.1)
   4.16.2

> Phoenix should depend on the appropriate tephra-hbase-compat-x.y module
> ---
>
> Key: PHOENIX-6442
> URL: https://issues.apache.org/jira/browse/PHOENIX-6442
> Project: Phoenix
>  Issue Type: Bug
>  Components: core, tephra
>Affects Versions: 5.1.0, 5.1.1, 4.16.0, 4.16.1
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 4.17.0, 5.2.0, 5.1.2, 4.16.2
>
>
> For the master branch, we depend on tephra-hbase-compat-2.0 dependency which 
> doesn't actually work with any of the supported HBase releases.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (PHOENIX-6357) Change all command line tools to use the fixed commons-cli constructor

2021-05-14 Thread Viraj Jasani (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani resolved PHOENIX-6357.
---
Fix Version/s: (was: 4.16.1)
   4.16.2
   Resolution: Fixed

> Change all command line tools to use the fixed commons-cli constructor
> --
>
> Key: PHOENIX-6357
> URL: https://issues.apache.org/jira/browse/PHOENIX-6357
> Project: Phoenix
>  Issue Type: Improvement
>  Components: core
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 4.17.0, 5.2.0, 5.1.2, 4.16.2
>
>
> Creating DefaultParser with the new DefaultParser(true, false) or 
> DefaultParser(false, false) 
> constructors will not mangle the double quotes for our tools.
> Change all tools to use that.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (PHOENIX-6422) Remove CorrelatePlan

2021-05-14 Thread Viraj Jasani (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani resolved PHOENIX-6422.
---
Fix Version/s: (was: 4.16.1)
   4.16.2
   Resolution: Fixed

> Remove CorrelatePlan
> 
>
> Key: PHOENIX-6422
> URL: https://issues.apache.org/jira/browse/PHOENIX-6422
> Project: Phoenix
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.1.0, 4.16.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Minor
> Fix For: 4.17.0, 5.2.0, 5.1.2, 4.16.2
>
>
> CorrelatePlan is never instantiated outside tests, it seems to have been 
> superseded by the other join plans.
> Remove it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Reopened] (PHOENIX-6422) Remove CorrelatePlan

2021-05-14 Thread Viraj Jasani (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani reopened PHOENIX-6422:
---

Reopening until 4.16.1 RC is created.

> Remove CorrelatePlan
> 
>
> Key: PHOENIX-6422
> URL: https://issues.apache.org/jira/browse/PHOENIX-6422
> Project: Phoenix
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.1.0, 4.16.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Minor
> Fix For: 4.16.1, 4.17.0, 5.2.0, 5.1.2
>
>
> CorrelatePlan is never instantiated outside tests, it seems to have been 
> superseded by the other join plans.
> Remove it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Reopened] (PHOENIX-6357) Change all command line tools to use the fixed commons-cli constructor

2021-05-14 Thread Viraj Jasani (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani reopened PHOENIX-6357:
---

Reopening until 4.16.1 RC is created.

> Change all command line tools to use the fixed commons-cli constructor
> --
>
> Key: PHOENIX-6357
> URL: https://issues.apache.org/jira/browse/PHOENIX-6357
> Project: Phoenix
>  Issue Type: Improvement
>  Components: core
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 4.16.1, 4.17.0, 5.2.0, 5.1.2
>
>
> Creating DefaultParser with the new DefaultParser(true, false) or 
> DefaultParser(false, false) 
> constructors will not mangle the double quotes for our tools.
> Change all tools to use that.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (PHOENIX-6447) Add support for SYSTEM.CHILD_LINK table in systemcatalogwalentryfilter

2021-05-14 Thread Viraj Jasani (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani updated PHOENIX-6447:
--
Fix Version/s: (was: 4.16.1)
   4.16.2

> Add support for SYSTEM.CHILD_LINK table in systemcatalogwalentryfilter
> --
>
> Key: PHOENIX-6447
> URL: https://issues.apache.org/jira/browse/PHOENIX-6447
> Project: Phoenix
>  Issue Type: Bug
>  Components: core
>Reporter: Sandeep Pal
>Assignee: Sandeep Pal
>Priority: Major
> Fix For: 4.17.0, 5.2.0, 4.16.2
>
>
> In order to replicate system tables, we have a special filter for system 
> catalog table to just replicate tenant owner data in order NOT to mess up the 
> system catalog at the sink cluster. In 4.16, there is a new table getting 
> added (SYSTEM.CHILD_LINK) which will not be replicated completely from our 
> existing filter. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)