[jira] [Resolved] (PHOENIX-6518) Implement SHOW CREATE TABLE SQL command

[Jira]

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

Richárd Antal resolved PHOENIX-6518.

Fix Version/s: 5.1.3
   5.2.0
   4.17.0
   Resolution: Fixed

I'll do the backport to 4.16 branch once PHOENIX-5543 landed there, will update 
the Fix version.

> Implement SHOW CREATE TABLE SQL command
> ---
>
> Key: PHOENIX-6518
> URL: https://issues.apache.org/jira/browse/PHOENIX-6518
> Project: Phoenix
>  Issue Type: Task
>  Components: core
>Reporter: Richárd Antal
>Assignee: Richárd Antal
>Priority: Major
> Fix For: 4.17.0, 5.2.0, 5.1.3
>
>
> With PHOENIX-5946 and PHOENIX-6454 it is possible to generate effective DDL 
> for a table/view/index using the SchemaTool and an hbase command.
>  Implement SHOW CREATE TABLE sql command to further utilize this 
> functionality.



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

[jira] [Resolved] (PHOENIX-6519) Make SchemaTool work with lower case table and column names

[Jira]

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

Richárd Antal resolved PHOENIX-6519.

Fix Version/s: 5.1.3
   5.2.0
   4.17.0
   Resolution: Fixed

I'll do the backport to 4.16 branch once PHOENIX-5543 landed there, will update 
the Fix version.

> Make SchemaTool work with lower case table and column names
> ---
>
> Key: PHOENIX-6519
> URL: https://issues.apache.org/jira/browse/PHOENIX-6519
> Project: Phoenix
>  Issue Type: Task
>  Components: core
>Reporter: Richárd Antal
>Assignee: Richárd Antal
>Priority: Major
> Fix For: 4.17.0, 5.2.0, 5.1.3
>
>
> I wrote this test as part of a PR for PHOENIX-6518 and it fails.
> {code:java}
> @Test
> public void testCreateTableStatementLowerCase() throws Exception {
> String tableName = "lowecasetbl1";
> String schemaName = "lowecaseschemaname1";
> String pTableFullName = SchemaUtil.getEscapedTableName(schemaName, 
> tableName);
> String createTableStmt = "CREATE TABLE "+ pTableFullName + 
> "(\"smallK\" VARCHAR NOT NULL PRIMARY KEY, "
> + "V1 VARCHAR, V2 VARCHAR) TTL=2592000, IMMUTABLE_ROWS=TRUE, 
> DISABLE_WAL=TRUE";
> List queries = new ArrayList(){};
> queries.add(createTableStmt);
> String result = runSchemaExtractionTool("\"" + schemaName + "\"", 
> "\"" + tableName + "\"", null, queries);
> Assert.assertEquals(createTableStmt, result.toUpperCase());
> }{code}
> Expected:
> {code:java}
> CREATE TABLE "lowecaseschemaname1"."lowecasetbl1"("smallK" VARCHAR NOT NULL 
> PRIMARY KEY, V1 VARCHAR, V2 VARCHAR) TTL=2592000, IMMUTABLE_ROWS=TRUE, 
> DISABLE_WAL=TRUE{code}
> Actual result:
> {code:java}
> CREATE TABLE LOWECASESCHEMANAME1.LOWECASETBL1(SMALLK VARCHAR NOT NULL PRIMARY 
> KEY, V1 VARCHAR, V2 VARCHAR) TTL=2592000, IMMUTABLE_ROWS=TRUE, 
> DISABLE_WAL=TRUE{code}



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

?????? [VOTE] Release of Apache Phoenix Query Server 6.0.0 RC5

[&]

Resolved. thanks.It should be recorded in the documents.




----
??: 
   "dev"

https://github.com/apache/phoenix-queryserver/tree/6.0.0RC5
 gt 

[jira] [Updated] (PHOENIX-6522) Unique Id generation support queryId

[Kiran Kumar Maturi (Jira)]

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

Kiran Kumar Maturi updated PHOENIX-6522:

Summary: Unique Id generation support queryId  (was: unique Id generation 
support queryId)

> Unique Id generation support queryId
> 
>
> Key: PHOENIX-6522
> URL: https://issues.apache.org/jira/browse/PHOENIX-6522
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Kiran Kumar Maturi
>Assignee: Kiran Kumar Maturi
>Priority: Major
>
> Sometimes user might want a queryId be generated for the query rather than 
> adding it. This feature will be config based if enabled it will generate 
> queryId for all the queries



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

[jira] [Created] (PHOENIX-6522) unique Id generation support queryId

[Kiran Kumar Maturi (Jira)]

Kiran Kumar Maturi created PHOENIX-6522:
---

 Summary: unique Id generation support queryId
 Key: PHOENIX-6522
 URL: https://issues.apache.org/jira/browse/PHOENIX-6522
 Project: Phoenix
  Issue Type: Sub-task
Reporter: Kiran Kumar Maturi
Assignee: Kiran Kumar Maturi


Sometimes user might want a queryId be generated for the query rather than 
adding it. This feature will be config based if enabled it will generate 
queryId for all the queries



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

[jira] [Updated] (PHOENIX-6521) QueryId support in Phoenix Coprocessor

[Kiran Kumar Maturi (Jira)]

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

Kiran Kumar Maturi updated PHOENIX-6521:

Description: To have better analysis for put (with indexes ) and scans, 
propagating query id at phoenix coprocessor would be necessary  (was: To have 
better analysis for put (with indexes ) and scans propagating query id at 
phoenix coprocessor would be necessary)

> QueryId support in Phoenix Coprocessor 
> ---
>
> Key: PHOENIX-6521
> URL: https://issues.apache.org/jira/browse/PHOENIX-6521
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Kiran Kumar Maturi
>Assignee: Kiran Kumar Maturi
>Priority: Major
>
> To have better analysis for put (with indexes ) and scans, propagating query 
> id at phoenix coprocessor would be necessary



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

[jira] [Updated] (PHOENIX-6521) QueryId support in Phoenix Coprocessor

[Kiran Kumar Maturi (Jira)]

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

Kiran Kumar Maturi updated PHOENIX-6521:

Parent: PHOENIX-5974
Issue Type: Sub-task  (was: New Feature)

> QueryId support in Phoenix Coprocessor 
> ---
>
> Key: PHOENIX-6521
> URL: https://issues.apache.org/jira/browse/PHOENIX-6521
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Kiran Kumar Maturi
>Assignee: Kiran Kumar Maturi
>Priority: Major
>
> To have better analysis for put (with indexes ) and scans propagating query 
> id at phoenix coprocessor would be necessary



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

[jira] [Created] (PHOENIX-6521) QueryId support in Phoenix Coprocessor

[Kiran Kumar Maturi (Jira)]

Kiran Kumar Maturi created PHOENIX-6521:
---

 Summary: QueryId support in Phoenix Coprocessor 
 Key: PHOENIX-6521
 URL: https://issues.apache.org/jira/browse/PHOENIX-6521
 Project: Phoenix
  Issue Type: New Feature
Reporter: Kiran Kumar Maturi
Assignee: Kiran Kumar Maturi


To have better analysis for put (with indexes ) and scans propagating query id 
at phoenix coprocessor would be necessary



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

Re: [VOTE] Release of Apache Phoenix Query Server 6.0.0 RC5

[Istvan Toth]

Hello luoc,
You need to copy the phoenix-client-hbase-2.3.jar from the phoenix
directory to the PQS directory.

On Fri, Jul 30, 2021 at 8:56 AM luoc  wrote:

> Hello guys,
> I have already builded the RC5 on local. but Ican'tstart the
> PQS.
>
>
> The folder structure is that :
> /opt/phoenix-hbase-2.3-5.1.2-bin/
> /opt/phoenix-queryserver-6.0.0/
>
>
> Then, I got the simple error message when run queryserver.py :
>
>
> 1../phoenix-queryserver-6.0.0/bin/queryserver.py start
>  starting Query Server, logging to
> /tmp/phoenix/phoenix-root-queryserver.log
>
>
> 2. The 8765 port is not online.
>
>
> 3.tail -f /tmp/phoenix/phoenix-root-queryserver.out
>  2021-07-30 14:45:20.682400 launching /usr/java/default/bin/java
> -cp
> /opt/phoenix-queryserver-6.0.0/bin/:/etc/hadoop/conf::/opt/phoenix-queryserver-6.0.0/bin/../phoenix-queryserver-6.0.0.jar:
> -Dproc_phoenixserver
> -Dlog4j.configuration=file:/opt/phoenix-queryserver-6.0.0/bin/log4j.properties
> -Dpsql.root.logger=INFO,DRFA -Dpsql.log.dir=/tmp/phoenix
> -Dpsql.log.file=phoenix-root-queryserver.log
> org.apache.phoenix.queryserver.server.QueryServer
> ERROR : Could not find or load main class
> org.apache.phoenix.queryserver.server.QueryServer
>
>
>
> --原始邮件--
> 发件人:
>   "dev"
> <
> st...@apache.org;
> 发送时间:2021年7月30日(星期五) 下午2:24
> 收件人:"dev"
> 主题:Re: [VOTE] Release of Apache Phoenix Query Server 6.0.0 RC5
>
>
>
> Hi!
>
> We have a single +1 from Viraj - Thanks!
> Can I get at least one more vote ?
> I can add the third vote myself.
>
> Istvan
>
> On Mon, Jul 19, 2021 at 7:43 PM Viraj Jasani  wrote:
>
>  +1
> 
>  * Signature: ok
>  * Checksum : ok
>  * Rat check (1.8.0_251): ok
>  - mvn clean apache-rat:check
>  * Built from source (1.8.0_251): ok
>  - mvn clean install -DskipTests
>  * Unit tests pass (1.8.0_251): failed (a couple of expected
> KerberosAuth
>  failures, others look good)
>  - mvn clean verify
> 
> 
>  On 2021/07/16 16:08:28, Istvan TothPlease vote on this Apache phoenix queryserver release candidate,
>   phoenix-queryserver-6.0.0RC5
>  
>   The VOTE will remain open for at least 72 hours.
>  
>   [ ] +1 Release this package as Apache phoenix queryserver 6.0.0
>   [ ] -1 Do not release this package because ...
>  
>   The tag to be voted on is 6.0.0RC5:
>  
>  
> https://github.com/apache/phoenix-queryserver/tree/6.0.0RC5
>  ; 
>   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-queryserver-6.0.0RC5/
> 
> ;
> 
>   Maven artifacts are available in a staging repository at:
>  
>   https://repository.apache.org/#stagingRepositories
>  ;
> (orgapachephoenix-1242)
>  
>   Artifacts were signed with the 0x794433C7 key which can be found
> in:
>  
>  
> https://dist.apache.org/repos/dist/release/phoenix/KEYS
>  ; 
>   To learn more about Apache phoenix queryserver, please see
>  
>   https://phoenix.apache.org/
>  
>   Thanks,
>   Istvan
>  
> 



-- 
*István Tóth* | Staff Software Engineer
st...@cloudera.com 
[image: Cloudera] 
[image: Cloudera on Twitter]  [image:
Cloudera on Facebook]  [image: Cloudera
on LinkedIn] 

--

[jira] [Updated] (PHOENIX-6520) Support for logging QueryId

[Kiran Kumar Maturi (Jira)]

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

Kiran Kumar Maturi updated PHOENIX-6520:

Parent: PHOENIX-5974
Issue Type: Sub-task  (was: New Feature)

> Support for logging QueryId 
> 
>
> Key: PHOENIX-6520
> URL: https://issues.apache.org/jira/browse/PHOENIX-6520
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Kiran Kumar Maturi
>Assignee: Kiran Kumar Maturi
>Priority: Major
>
> For a Heavily loaded cluster phoenix client makes lot of queries. Currently 
> it is very difficult to know which query failed and what happened with the 
> request. Logging a 
> queryId([PHOENIX-5974|https://issues.apache.org/jira/browse/PHOENIX-5974])  
> along with the logs can help us to better debug. This feature will be config 
> based.
> I am planning to use [log4j Thread Context | 
> https://logging.apache.org/log4j/2.x/manual/thread-context.html] to store the 
> queryId and modify the log 
> [pattern|https://github.com/apache/phoenix/blob/master/phoenix-pherf/config/log4j.properties]
>  to show queryId when the feature is enabled



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

[jira] [Created] (PHOENIX-6520) Support for logging QueryId

[Kiran Kumar Maturi (Jira)]

Kiran Kumar Maturi created PHOENIX-6520:
---

 Summary: Support for logging QueryId 
 Key: PHOENIX-6520
 URL: https://issues.apache.org/jira/browse/PHOENIX-6520
 Project: Phoenix
  Issue Type: New Feature
Reporter: Kiran Kumar Maturi
Assignee: Kiran Kumar Maturi


For a Heavily loaded cluster phoenix client makes lot of queries. Currently it 
is very difficult to know which query failed and what happened with the 
request. Logging a 
queryId([PHOENIX-5974|https://issues.apache.org/jira/browse/PHOENIX-5974])  
along with the logs can help us to better debug. This feature will be config 
based.

I am planning to use [log4j Thread Context | 
https://logging.apache.org/log4j/2.x/manual/thread-context.html] to store the 
queryId and modify the log 
[pattern|https://github.com/apache/phoenix/blob/master/phoenix-pherf/config/log4j.properties]
 to show queryId when the feature is enabled



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

[jira] [Updated] (PHOENIX-5974) QueryId for Phoenix Query

[Kiran Kumar Maturi (Jira)]

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

Kiran Kumar Maturi updated PHOENIX-5974:

Description: Add a QueryId corresponding to a Phoenix Query which can be 
used to uniquely identify the query. Propagate this QueryId  further to HBase. 
Hbase supports 
[identifier|https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/OperationWithAttributes.html#getId--]
 for request . Hbase logs the identifier when request timesout or has a slow 
response. This information is very useful in associating client and server side 
information. Phoenix QueryId will help in analyzing client side logs also.  
(was: Add a QueryId corresponding to a Phoenix Query which can be used to 
uniquely identify the query. Propagate this QueryId  further to HBase. Hbase 
supports 
[identifier](https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/OperationWithAttributes.html#getId--)
 for request . Hbase logs the identifier when request timesout or has a slow 
response. This information is very useful in associating client and server side 
information. Phoenix QueryId will help in analyzing client side logs also.)

> QueryId for Phoenix Query
> -
>
> Key: PHOENIX-5974
> URL: https://issues.apache.org/jira/browse/PHOENIX-5974
> Project: Phoenix
>  Issue Type: New Feature
>Reporter: Pranshu Khandelwal
>Assignee: Kiran Kumar Maturi
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add a QueryId corresponding to a Phoenix Query which can be used to uniquely 
> identify the query. Propagate this QueryId  further to HBase. Hbase supports 
> [identifier|https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/OperationWithAttributes.html#getId--]
>  for request . Hbase logs the identifier when request timesout or has a slow 
> response. This information is very useful in associating client and server 
> side information. Phoenix QueryId will help in analyzing client side logs 
> also.



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

[jira] [Resolved] (PHOENIX-6317) Add OWASP dependency check for connectors

[Jira]

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

Richárd Antal resolved PHOENIX-6317.

Fix Version/s: connectors-6.0.0
 Assignee: Richárd Antal  (was: Istvan Toth)
   Resolution: Fixed

> Add OWASP dependency check for connectors
> -
>
> Key: PHOENIX-6317
> URL: https://issues.apache.org/jira/browse/PHOENIX-6317
> Project: Phoenix
>  Issue Type: Task
>  Components: connectors
>Affects Versions: connectors-6.0.0
>Reporter: Istvan Toth
>Assignee: Richárd Antal
>Priority: Major
> Fix For: connectors-6.0.0
>
>
> Splitting this out form PHOENIX-6065



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

[jira] [Updated] (PHOENIX-5974) QueryId for Phoenix Query

[Kiran Kumar Maturi (Jira)]

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

Kiran Kumar Maturi updated PHOENIX-5974:

Description: Add a QueryId corresponding to a Phoenix Query which can be 
used to uniquely identify the query. Propagate this QueryId  further to HBase. 
Hbase supports 
[identifier](https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/OperationWithAttributes.html#getId--)
 for request . Hbase logs the identifier when request timesout or has a slow 
response. This information is very useful in associating client and server side 
information. Phoenix QueryId will help in analyzing client side logs also.  
(was: Add a TraceId corresponding to a Phoenix Query which translates further 
into an HBase mutationId. Using this TraceId one can log information about the 
bottlenecks in the Network and Trace out the flow of the SQL like Phoenix Query 
till it compiles as an Hbase mutation and ultimately into a Message to the RPC 
Layer.)

> QueryId for Phoenix Query
> -
>
> Key: PHOENIX-5974
> URL: https://issues.apache.org/jira/browse/PHOENIX-5974
> Project: Phoenix
>  Issue Type: New Feature
>Reporter: Pranshu Khandelwal
>Assignee: Kiran Kumar Maturi
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add a QueryId corresponding to a Phoenix Query which can be used to uniquely 
> identify the query. Propagate this QueryId  further to HBase. Hbase supports 
> [identifier](https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/OperationWithAttributes.html#getId--)
>  for request . Hbase logs the identifier when request timesout or has a slow 
> response. This information is very useful in associating client and server 
> side information. Phoenix QueryId will help in analyzing client side logs 
> also.



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

[jira] [Updated] (PHOENIX-5974) QueryId for Phoenix Query

[Kiran Kumar Maturi (Jira)]

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

Kiran Kumar Maturi updated PHOENIX-5974:

Summary: QueryId for Phoenix Query  (was: RequestId for Phoenix Query)

> QueryId for Phoenix Query
> -
>
> Key: PHOENIX-5974
> URL: https://issues.apache.org/jira/browse/PHOENIX-5974
> Project: Phoenix
>  Issue Type: New Feature
>Reporter: Pranshu Khandelwal
>Assignee: Kiran Kumar Maturi
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add a TraceId corresponding to a Phoenix Query which translates further into 
> an HBase mutationId. Using this TraceId one can log information about the 
> bottlenecks in the Network and Trace out the flow of the SQL like Phoenix 
> Query till it compiles as an Hbase mutation and ultimately into a Message to 
> the RPC Layer.



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

?????? [VOTE] Release of Apache Phoenix Query Server 6.0.0 RC5

[luoc]

Hello guys,
I have already builded the RC5 on local. but Ican'tstart the PQS.


The folder structure is that :
/opt/phoenix-hbase-2.3-5.1.2-bin/
/opt/phoenix-queryserver-6.0.0/


Then, I got the simple error message when run queryserver.py :


1../phoenix-queryserver-6.0.0/bin/queryserver.py start
 starting Query Server, logging to 
/tmp/phoenix/phoenix-root-queryserver.log


2. The 8765 port is not online.


3.tail -f /tmp/phoenix/phoenix-root-queryserver.out
 2021-07-30 14:45:20.682400 launching /usr/java/default/bin/java -cp 
/opt/phoenix-queryserver-6.0.0/bin/:/etc/hadoop/conf::/opt/phoenix-queryserver-6.0.0/bin/../phoenix-queryserver-6.0.0.jar:
 -Dproc_phoenixserver 
-Dlog4j.configuration=file:/opt/phoenix-queryserver-6.0.0/bin/log4j.properties 
-Dpsql.root.logger=INFO,DRFA -Dpsql.log.dir=/tmp/phoenix 
-Dpsql.log.file=phoenix-root-queryserver.log 
org.apache.phoenix.queryserver.server.QueryServer
ERROR : Could not find or load main class 
org.apache.phoenix.queryserver.server.QueryServer



----
??: 
   "dev"
https://github.com/apache/phoenix-queryserver/tree/6.0.0RC5
 
  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-queryserver-6.0.0RC5/
 
  Maven artifacts are available in a staging repository at:
 
  https://repository.apache.org/#stagingRepositories
 (orgapachephoenix-1242)
 
  Artifacts were signed with the 0x794433C7 key which can be found in:
 
  https://dist.apache.org/repos/dist/release/phoenix/KEYS
 
  To learn more about Apache phoenix queryserver, please see
 
  https://phoenix.apache.org/
 
  Thanks,
  Istvan
 

Re: [VOTE] Release of Apache Phoenix Query Server 6.0.0 RC5

[Istvan Toth]

Hi!

We have a single +1 from Viraj - Thanks!
Can I get at least one more vote ?
I can add the third vote myself.

Istvan

On Mon, Jul 19, 2021 at 7:43 PM Viraj Jasani  wrote:

> +1
>
> * Signature: ok
> * Checksum : ok
> * Rat check (1.8.0_251): ok
>  - mvn clean apache-rat:check
> * Built from source (1.8.0_251): ok
>  - mvn clean install  -DskipTests
> * Unit tests pass (1.8.0_251): failed (a couple of expected KerberosAuth
> failures, others look good)
>  - mvn clean verify
>
>
> On 2021/07/16 16:08:28, Istvan Toth  wrote:
> > Please vote on this Apache phoenix queryserver release candidate,
> > phoenix-queryserver-6.0.0RC5
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache phoenix queryserver 6.0.0
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 6.0.0RC5:
> >
> >   https://github.com/apache/phoenix-queryserver/tree/6.0.0RC5
> >
> > 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-queryserver-6.0.0RC5/
> >
> > Maven artifacts are available in a staging repository at:
> >
> >   https://repository.apache.org/#stagingRepositories
> (orgapachephoenix-1242)
> >
> > Artifacts were signed with the 0x794433C7 key which can be found in:
> >
> >   https://dist.apache.org/repos/dist/release/phoenix/KEYS
> >
> > To learn more about Apache phoenix queryserver, please see
> >
> >   https://phoenix.apache.org/
> >
> > Thanks,
> > Istvan
> >
>