[jira] [Created] (PHOENIX-7150) PHOENIX-6523 has broken HBase 2.1 and 2.2 support

[Istvan Toth (Jira)]

Istvan Toth created PHOENIX-7150:


 Summary: PHOENIX-6523 has broken HBase 2.1 and 2.2 support
 Key: PHOENIX-7150
 URL: https://issues.apache.org/jira/browse/PHOENIX-7150
 Project: Phoenix
  Issue Type: Bug
  Components: core
Affects Versions: 5.1.4
Reporter: Istvan Toth
Assignee: Istvan Toth


We set the ZK Registry name, but that doesn't exist pre 2.3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[VOTE] Release of Apache Phoenix Thirdparty 2.1.0 RC0

[rajeshb...@apache.org]

Please vote on this Apache phoenix thirdparty release candidate,
phoenix-thirdparty-2.1.0RC0

The VOTE will remain open for at least 72 hours.

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

The tag to be voted on is 2.1.0RC0:

  https://github.com/apache/phoenix-thirdparty/tree/2.1.0RC0

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-thirdparty-2.1.0RC0/

Maven artifacts are available in a staging repository at:

  https://repository.apache.org/content/repositories//

Artifacts were signed with the 0x2CC0FD99 key which can be found in:

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

To learn more about Apache phoenix thirdparty, please see

  https://phoenix.apache.org/

Thanks,
Rajeshbabu Chintaguntla

Re: [DISCUSS] Client-Server Code Separation (PHOENIX-6053) has been Merged and Next Steps

[Viraj Jasani]

One more question: do generated jars (phoenix-client and phoenix-server)
follow the same naming conventions after this change? Perhaps this is
already answered somewhere, I hope I can take a thorough look at the Jira
discussions and the change soon :)


Thanks,
Viraj


On Tue, Dec 12, 2023 at 8:59 PM Viraj Jasani  wrote:

> Thank you for starting this thread Istvan!
>
> This is really nice change and I can see how porting to 5.1 could be
> beneficial as well as disastrous for a maintenance release. One question:
> how confident are we from backward compatibility viewpoint? specifically
> 5.1 client against current master branch based server.
>
> IMHO, we should keep this for major/minor release only. It would also
> enforce us to create 2 PRs going forward (one for master/5.2 and another
> for 5.1) but this is still better in case something gets broken in the
> future. Fixing it on maintenance release would also be nightmare.
>
> This is really good improvement. I also wonder what should be our path
> forward beyond 5.1. Shall we still stick to 5.2.0 or move to 6.0.0?
>
> master branch is becoming extremely heavy day by day with many features
> still being lined up for merging very soon. Json support is almost ready I
> believe. We have data integrity issues and many behavioural changes that
> are non-compatible (but necessary to implement heavy feature like ViewTTL)
> in the queue. Many committed features like Partial Index, Uncovered Index,
> MasterRegistry compatible JDBC connection etc are ready for rollout as soon
> as we cut release branch from master. It does seem quite a massive list for
> a minor release, but this is just my opinion. I am not against 5.2.0
> release, would be open for more opinions.
>
> Thanks,
> Viraj
>
>
> On Mon, Dec 11, 2023 at 11:31 PM Istvan Toth  wrote:
>
>> Hi!
>>
>> First of all, a heads up that I have merged the Client-Server code
>> separation (PHOENIX-6053) patch a few minutes ago.
>>
>> A huge thanks to Aron for turning my two years old POC patch into a
>> merge-ready patch, and handling all the change requests and numerous
>> rebases.
>>
>> The patch has been discussed on the ticket
>> 
>> and in the 2021
>>  and
>> the
>> recent
>> <
>> https://lists.apache.org/list?dev@phoenix.apache.org:2023-10:PHOENIX-6053
>> >
>> email threads.
>>
>>
>> *A very quick recap:*
>> *phoenix-core* has been split into two modules* phoenix-core-client* and
>> *phoenix-core-server*.
>> *Phoenix-core-server* depends on* phoenix-core-client*, as we more or less
>> need the full client code on the server side.
>> phoenix-core includes all the code needed the JDBC driver, but does not
>> include anything that is used exclusively on the server side
>> (coprocessors,
>> split policies, etc)
>>
>> *phoenix-core* is still around, it retains all the tests (as the majority
>> of them ), and it also acts as a compatibility dependency, which
>> transitively depends on both client and server.
>>
>>
>> *Backporting to 5.1:*
>> We need to make a decision on whether to backport this change into 5.1 or
>> not.
>>
>> Against:
>>
>>- It is a huge patch by file count
>>- maven module structure changes
>>
>> For:
>>
>>- Backports to 5.1 will be a *nightmare* if we don't backport this
>> change
>>- The actual code changes are minimal, and the behavioural changes
>>should be non-existent.
>>- Dependency compatibility should be handled by the phoenix-core
>> package
>>- Users get the advantages without having to wait for 5.2.
>>
>> We have three options:
>>
>>- Backport to 5.1.4
>>- Backport post 5.1.4
>>- Do not backport
>>
>>
>> *I really need to hear your take on this.*
>>
>> *Next steps:*
>> This change in itself does little apart from cleaning up the code, but it
>> enables a number of important new features (these were originally planned
>> to be included in PHOENIX-6053, but I decided to split them to separate
>> tickets to keep the scope manageable):
>>
>>
>>- PHOENIX-7137 
>>Create *phoenix-client-lite* shaded JAR without server-side
>> dependencies
>>   - This adds a new shaded client variant, *phoenix-client-lite
>> *(names
>>   are up for discussion), which omits the server-side code and its
>>   dependencies. It is ~20 MB smaller, and pollutes the classpath less.
>>- PHOENIX-7139 
>>Create *phoenix-mapreduce-byo-shaded-hbase* artifact for use by
>>connectors
>>   - This allows using the hbase-shaded-client and phoenix on the same
>>   classpath. Up until now, you had to do that by using the
>> phoenix-core
>>   dependency from Maven, or by using the HBase libraries shaded into
>>   phoenix-client.
>>   The current phoenix-client will fail hard with any other Hbase
>>   libraries on 

Re: [DISCUSS] Client-Server Code Separation (PHOENIX-6053) has been Merged and Next Steps

[Viraj Jasani]

Thank you for starting this thread Istvan!

This is really nice change and I can see how porting to 5.1 could be
beneficial as well as disastrous for a maintenance release. One question:
how confident are we from backward compatibility viewpoint? specifically
5.1 client against current master branch based server.

IMHO, we should keep this for major/minor release only. It would also
enforce us to create 2 PRs going forward (one for master/5.2 and another
for 5.1) but this is still better in case something gets broken in the
future. Fixing it on maintenance release would also be nightmare.

This is really good improvement. I also wonder what should be our path
forward beyond 5.1. Shall we still stick to 5.2.0 or move to 6.0.0?

master branch is becoming extremely heavy day by day with many features
still being lined up for merging very soon. Json support is almost ready I
believe. We have data integrity issues and many behavioural changes that
are non-compatible (but necessary to implement heavy feature like ViewTTL)
in the queue. Many committed features like Partial Index, Uncovered Index,
MasterRegistry compatible JDBC connection etc are ready for rollout as soon
as we cut release branch from master. It does seem quite a massive list for
a minor release, but this is just my opinion. I am not against 5.2.0
release, would be open for more opinions.

Thanks,
Viraj


On Mon, Dec 11, 2023 at 11:31 PM Istvan Toth  wrote:

> Hi!
>
> First of all, a heads up that I have merged the Client-Server code
> separation (PHOENIX-6053) patch a few minutes ago.
>
> A huge thanks to Aron for turning my two years old POC patch into a
> merge-ready patch, and handling all the change requests and numerous
> rebases.
>
> The patch has been discussed on the ticket
> 
> and in the 2021
>  and the
> recent
>  >
> email threads.
>
>
> *A very quick recap:*
> *phoenix-core* has been split into two modules* phoenix-core-client* and
> *phoenix-core-server*.
> *Phoenix-core-server* depends on* phoenix-core-client*, as we more or less
> need the full client code on the server side.
> phoenix-core includes all the code needed the JDBC driver, but does not
> include anything that is used exclusively on the server side (coprocessors,
> split policies, etc)
>
> *phoenix-core* is still around, it retains all the tests (as the majority
> of them ), and it also acts as a compatibility dependency, which
> transitively depends on both client and server.
>
>
> *Backporting to 5.1:*
> We need to make a decision on whether to backport this change into 5.1 or
> not.
>
> Against:
>
>- It is a huge patch by file count
>- maven module structure changes
>
> For:
>
>- Backports to 5.1 will be a *nightmare* if we don't backport this
> change
>- The actual code changes are minimal, and the behavioural changes
>should be non-existent.
>- Dependency compatibility should be handled by the phoenix-core package
>- Users get the advantages without having to wait for 5.2.
>
> We have three options:
>
>- Backport to 5.1.4
>- Backport post 5.1.4
>- Do not backport
>
>
> *I really need to hear your take on this.*
>
> *Next steps:*
> This change in itself does little apart from cleaning up the code, but it
> enables a number of important new features (these were originally planned
> to be included in PHOENIX-6053, but I decided to split them to separate
> tickets to keep the scope manageable):
>
>
>- PHOENIX-7137 
>Create *phoenix-client-lite* shaded JAR without server-side dependencies
>   - This adds a new shaded client variant, *phoenix-client-lite *(names
>   are up for discussion), which omits the server-side code and its
>   dependencies. It is ~20 MB smaller, and pollutes the classpath less.
>- PHOENIX-7139 
>Create *phoenix-mapreduce-byo-shaded-hbase* artifact for use by
>connectors
>   - This allows using the hbase-shaded-client and phoenix on the same
>   classpath. Up until now, you had to do that by using the phoenix-core
>   dependency from Maven, or by using the HBase libraries shaded into
>   phoenix-client.
>   The current phoenix-client will fail hard with any other Hbase
>   libraries on the classpath due to relocation conflicts.
>   - Allows updating the hbase client code without rebuilding Phoenix
>   - Solves the protobuf 2.5.0 woes, which make it impossible to use
>   code/libraries using unshaded protobuf 3.0 together with
> Phoenix. This was,
>   and remains the original driver behind PHOENIX-6053.
>   - Allows using Hadoop extensions with Phoenix. Being able to use the
>   various cloud connectors like AWS S3a without shading 

[jira] [Created] (PHOENIX-7149) Use Statement#closeOnCompletion for PhoenixDataBaseMetaData queries

[Istvan Toth (Jira)]

Istvan Toth created PHOENIX-7149:


 Summary: Use Statement#closeOnCompletion for 
PhoenixDataBaseMetaData queries
 Key: PHOENIX-7149
 URL: https://issues.apache.org/jira/browse/PHOENIX-7149
 Project: Phoenix
  Issue Type: Improvement
  Components: core
Reporter: Istvan Toth


We already do this for the ResultSet metadata.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (PHOENIX-7076) MetaDataRegionObserver#postOpen hook improvements

[Viraj Jasani (Jira)]

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

Viraj Jasani resolved PHOENIX-7076.
---
Resolution: Fixed

> MetaDataRegionObserver#postOpen hook improvements
> -
>
> Key: PHOENIX-7076
> URL: https://issues.apache.org/jira/browse/PHOENIX-7076
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 5.1.3
>Reporter: Viraj Jasani
>Assignee: Divneet Kaur
>Priority: Major
> Fix For: 5.2.0, 5.1.4
>
>
> For older versions upgrading to 4.7+, we perform deletion of all rows on 
> SYSTEM.STATS table one time. This is done only if column "UPGRADE_TO_4_7" 
> does not exist on SYSTEM.CATALOG.
> Since this task is performed in a daemon thread as part of region#postOpen 
> coproc hook, it might get stuck accessing SYSTEM.CATALOG table if the region 
> open gets delayed for some reason.
> Similar to BuildIndexScheduleTask that gets scheduled with 10s of initial 
> delay (by default), we should perform truncate stats as a delayed task, even 
> though it does not require any repetition.
>  
> {code:java}
> 2023-10-11 22:51:09,728 DEBUG [Thread-60] client.RpcRetryingCallerImpl - 
> n$ClientServiceBlockingInterfaceWrapper.doCall(ServerConnectionUtils.java:163)
>  
>     at 
> org.apache.hadoop.hbase.client.ServerConnectionUtils$ShortCircuitingClusterConnection$ClientServiceBlockingInterfaceWrapper.get(ServerConnectionUtils.java:131)
>  
>     at 
> org.apache.hadoop.hbase.client.ClientServiceCallable.doGet(ClientServiceCallable.java:51)
>  
>     at org.apache.hadoop.hbase.client.HTable$1.rpcCall(HTable.java:364) 
>     at org.apache.hadoop.hbase.client.HTable$1.rpcCall(HTable.java:359) 
>     at 
> org.apache.hadoop.hbase.client.RegionServerCallable.call(RegionServerCallable.java:124)
>  
>     at 
> org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:104)
>  
>     at org.apache.hadoop.hbase.client.HTable.get(HTable.java:370) 
>     at org.apache.hadoop.hbase.client.HTable.get(HTable.java:343) 
>     at 
> org.apache.phoenix.util.UpgradeUtil.truncateStats(UpgradeUtil.java:2057) 
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1$1.run(MetaDataRegionObserver.java:182)
>  
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1$1.run(MetaDataRegionObserver.java:179)
>  
>     at java.security.AccessController.doPrivileged(Native Method) 
>     at javax.security.auth.Subject.doAs(Subject.java:422) 
>     at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1962)
>  
>     at 
> org.apache.hadoop.security.SecurityUtil.doAsUser(SecurityUtil.java:514) 
>     at 
> org.apache.hadoop.security.SecurityUtil.doAsLoginUser(SecurityUtil.java:495) 
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  
>     at java.lang.reflect.Method.invoke(Method.java:498) 
>     at org.apache.hadoop.hbase.util.Methods.call(Methods.java:39) 
>     at org.apache.hadoop.hbase.security.User.runAsLoginUser(User.java:178) 
>     at 
> org.apache.phoenix.coprocessor.MetaDataRegionObserver$1.run(MetaDataRegionObserver.java:179)
>  
>     at java.lang.Thread.run(Thread.java:750) {code}
>  
> Improvements:
>  # Schedule truncate stats task with 10s delay (configurable) rather than 
> starting the thread immediately.
>  # Only if {{phoenix.stats.collection.enabled}} is enabled, create daemon 
> thread for truncate stats task.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (PHOENIX-7148) Use getColumnLabel Instead of getColumnName in QueryServerBasicsIT

[Istvan Toth (Jira)]

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

Istvan Toth resolved PHOENIX-7148.
--
Fix Version/s: queryserver-6.0.1
   Resolution: Fixed

Committed to master.
Thanks for the review [~vjasani] and [~rajeshbabu].

> Use getColumnLabel Instead of getColumnName in QueryServerBasicsIT
> --
>
> Key: PHOENIX-7148
> URL: https://issues.apache.org/jira/browse/PHOENIX-7148
> Project: Phoenix
>  Issue Type: Bug
>  Components: queryserver
>Affects Versions: queryserver-6.0.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>  Labels: test
> Fix For: queryserver-6.0.1
>
>
> Otherwise tests are going to fail with 5.1.4 and 5.2.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (PHOENIX-7148) Use getColumnLabel Instead of getColumnName in QueryServerBasicsIT

[Istvan Toth (Jira)]

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

Istvan Toth reassigned PHOENIX-7148:


Assignee: Istvan Toth

> Use getColumnLabel Instead of getColumnName in QueryServerBasicsIT
> --
>
> Key: PHOENIX-7148
> URL: https://issues.apache.org/jira/browse/PHOENIX-7148
> Project: Phoenix
>  Issue Type: Bug
>  Components: queryserver
>Affects Versions: queryserver-6.0.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>
> Otherwise tests are going to fail with 5.1.4 and 5.2.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7148) Use getColumnLabel Instead of getColumnName in QueryServerBasicsIT

[Istvan Toth (Jira)]

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

Istvan Toth updated PHOENIX-7148:
-
Labels: test  (was: )

> Use getColumnLabel Instead of getColumnName in QueryServerBasicsIT
> --
>
> Key: PHOENIX-7148
> URL: https://issues.apache.org/jira/browse/PHOENIX-7148
> Project: Phoenix
>  Issue Type: Bug
>  Components: queryserver
>Affects Versions: queryserver-6.0.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>  Labels: test
>
> Otherwise tests are going to fail with 5.1.4 and 5.2.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (PHOENIX-7111) Metrics for server-side metadata cache

[Rushabh Shah (Jira)]

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

Rushabh Shah resolved PHOENIX-7111.
---
Resolution: Fixed

> Metrics for server-side metadata cache
> --
>
> Key: PHOENIX-7111
> URL: https://issues.apache.org/jira/browse/PHOENIX-7111
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Palash Chauhan
>Assignee: Palash Chauhan
>Priority: Major
>
> Add metrics for monitoring the new metadata caching design. 
>  # Time taken to invalidate cache on all region servers during a DDL operation
>  # Number of failed DDL operations due to failure in cache invalidation
>  # Number of validateLastDDLTimestamp requests per region-server
>  # Cache hits/misses per region-server when validating timestamps



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (PHOENIX-7148) Use getColumnLabel Instead of getColumnName in QueryServerBasicsIT

[Istvan Toth (Jira)]

Istvan Toth created PHOENIX-7148:


 Summary: Use getColumnLabel Instead of getColumnName in 
QueryServerBasicsIT
 Key: PHOENIX-7148
 URL: https://issues.apache.org/jira/browse/PHOENIX-7148
 Project: Phoenix
  Issue Type: Bug
  Components: queryserver
Affects Versions: queryserver-6.0.0
Reporter: Istvan Toth


Otherwise tests are going to fail with 5.1.4 and 5.2.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (PHOENIX-7147) conn.getMetaData().getCatalogs() returns incorrect column name

[Istvan Toth (Jira)]

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

Istvan Toth resolved PHOENIX-7147.
--
Resolution: Not A Problem

> conn.getMetaData().getCatalogs() returns incorrect column name
> --
>
> Key: PHOENIX-7147
> URL: https://issues.apache.org/jira/browse/PHOENIX-7147
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>
> -It should return- It used to return a single column named "TABLE_CAT", but 
> it returns a column named TENANT_ID.
> This is a recent regression, this works in 5.1.3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7147) conn.getMetaData().getCatalogs() returns incorrect column name

[Istvan Toth (Jira)]

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

Istvan Toth updated PHOENIX-7147:
-
Description: 
-It should return- It used to return a single column named "TABLE_CAT", but it 
returns a column named TENANT_ID.
This is a recent regression, this works in 5.1.3.

  was:
It should return a single column named "TABLE_CAT", but it returns a column 
named TENANT_ID.
This is a recent regression, this works in 5.1.3.


> conn.getMetaData().getCatalogs() returns incorrect column name
> --
>
> Key: PHOENIX-7147
> URL: https://issues.apache.org/jira/browse/PHOENIX-7147
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>
> -It should return- It used to return a single column named "TABLE_CAT", but 
> it returns a column named TENANT_ID.
> This is a recent regression, this works in 5.1.3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (PHOENIX-7147) conn.getMetaData().getCatalogs() returns incorrect column name

[Istvan Toth (Jira)]

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

Istvan Toth reassigned PHOENIX-7147:


Assignee: Istvan Toth

> conn.getMetaData().getCatalogs() returns incorrect column name
> --
>
> Key: PHOENIX-7147
> URL: https://issues.apache.org/jira/browse/PHOENIX-7147
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>
> It should return a single column named "TABLE_CAT", but it returns a column 
> named TENANT_ID.
> This is a recent regression, this works in 5.1.3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (PHOENIX-7147) conn.getMetaData().getCatalogs() returns incorrect column name

[Istvan Toth (Jira)]

Istvan Toth created PHOENIX-7147:


 Summary: conn.getMetaData().getCatalogs() returns incorrect column 
name
 Key: PHOENIX-7147
 URL: https://issues.apache.org/jira/browse/PHOENIX-7147
 Project: Phoenix
  Issue Type: Bug
Reporter: Istvan Toth


It should return a single column named "TABLE_CAT", but it returns a column 
named TENANT_ID.
This is a recent regression, this works in 5.1.3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7098) Document JSON functionality on the Phoenix Site

[Ranganath Govardhanagiri (Jira)]

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

Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: (was: Adding_JSON_Support_documentation_.patch)

> Document JSON functionality on the Phoenix Site
> ---
>
> Key: PHOENIX-7098
> URL: https://issues.apache.org/jira/browse/PHOENIX-7098
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Ranganath Govardhanagiri
>Assignee: Ranganath Govardhanagiri
>Priority: Major
> Attachments: Adding_JSON_Support_documentation.patch, JSON Support in 
> Features dropdown menu.png, Json Datatype info.png, Json Datatype.png, Json 
> Functions Index.png, Json Functions description.png, Json Support 
> Documentation.png, Json Support at the bottom.png, JsonSupport.pdf, 
> image-2023-12-08-11-12-07-766.png
>
>
> Adding documentation for the JSON Support feature



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7098) Document JSON functionality on the Phoenix Site

[Ranganath Govardhanagiri (Jira)]

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

Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: Adding_JSON_Support_documentation.patch

> Document JSON functionality on the Phoenix Site
> ---
>
> Key: PHOENIX-7098
> URL: https://issues.apache.org/jira/browse/PHOENIX-7098
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Ranganath Govardhanagiri
>Assignee: Ranganath Govardhanagiri
>Priority: Major
> Attachments: Adding_JSON_Support_documentation.patch, JSON Support in 
> Features dropdown menu.png, Json Datatype info.png, Json Datatype.png, Json 
> Functions Index.png, Json Functions description.png, Json Support 
> Documentation.png, Json Support at the bottom.png, JsonSupport.pdf, 
> image-2023-12-08-11-12-07-766.png
>
>
> Adding documentation for the JSON Support feature



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7098) Document JSON functionality on the Phoenix Site

[Ranganath Govardhanagiri (Jira)]

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

Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: Json Support Documentation.png

> Document JSON functionality on the Phoenix Site
> ---
>
> Key: PHOENIX-7098
> URL: https://issues.apache.org/jira/browse/PHOENIX-7098
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Ranganath Govardhanagiri
>Assignee: Ranganath Govardhanagiri
>Priority: Major
> Attachments: JSON Support in Features dropdown menu.png, Json 
> Datatype info.png, Json Datatype.png, Json Functions Index.png, Json 
> Functions description.png, Json Support Documentation.png, Json Support at 
> the bottom.png, JsonSupport.pdf, image-2023-12-08-11-12-07-766.png
>
>
> Adding documentation for the JSON Support feature



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7098) Document JSON functionality on the Phoenix Site

[Ranganath Govardhanagiri (Jira)]

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

Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: Adding_JSON_Support_documentation_.patch

> Document JSON functionality on the Phoenix Site
> ---
>
> Key: PHOENIX-7098
> URL: https://issues.apache.org/jira/browse/PHOENIX-7098
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Ranganath Govardhanagiri
>Assignee: Ranganath Govardhanagiri
>Priority: Major
> Attachments: Adding_JSON_Support_documentation_.patch, JSON Support 
> in Features dropdown menu.png, Json Datatype info.png, Json Datatype.png, 
> Json Functions Index.png, Json Functions description.png, Json Support 
> Documentation.png, Json Support at the bottom.png, JsonSupport.pdf, 
> image-2023-12-08-11-12-07-766.png
>
>
> Adding documentation for the JSON Support feature



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7098) Document JSON functionality on the Phoenix Site

[Ranganath Govardhanagiri (Jira)]

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

Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: (was: Json Support Documentation.png)

> Document JSON functionality on the Phoenix Site
> ---
>
> Key: PHOENIX-7098
> URL: https://issues.apache.org/jira/browse/PHOENIX-7098
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Ranganath Govardhanagiri
>Assignee: Ranganath Govardhanagiri
>Priority: Major
> Attachments: JSON Support in Features dropdown menu.png, Json 
> Datatype info.png, Json Datatype.png, Json Functions Index.png, Json 
> Functions description.png, Json Support Documentation.png, Json Support at 
> the bottom.png, JsonSupport.pdf, image-2023-12-08-11-12-07-766.png
>
>
> Adding documentation for the JSON Support feature



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7098) Document JSON functionality on the Phoenix Site

[Ranganath Govardhanagiri (Jira)]

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

Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: (was: Adding_JSON_Support_documentation.patch)

> Document JSON functionality on the Phoenix Site
> ---
>
> Key: PHOENIX-7098
> URL: https://issues.apache.org/jira/browse/PHOENIX-7098
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Ranganath Govardhanagiri
>Assignee: Ranganath Govardhanagiri
>Priority: Major
> Attachments: JSON Support in Features dropdown menu.png, Json 
> Datatype info.png, Json Datatype.png, Json Functions Index.png, Json 
> Functions description.png, Json Support Documentation.png, Json Support at 
> the bottom.png, JsonSupport.pdf, image-2023-12-08-11-12-07-766.png
>
>
> Adding documentation for the JSON Support feature



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7098) Document JSON functionality on the Phoenix Site

[Ranganath Govardhanagiri (Jira)]

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

Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: (was: Adding_JSON_Support_documentation_.patch)

> Document JSON functionality on the Phoenix Site
> ---
>
> Key: PHOENIX-7098
> URL: https://issues.apache.org/jira/browse/PHOENIX-7098
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Ranganath Govardhanagiri
>Assignee: Ranganath Govardhanagiri
>Priority: Major
> Attachments: Adding_JSON_Support_documentation.patch, JSON Support in 
> Features dropdown menu.png, Json Datatype info.png, Json Datatype.png, Json 
> Functions Index.png, Json Functions description.png, Json Support 
> Documentation.png, Json Support at the bottom.png, JsonSupport.pdf, 
> image-2023-12-08-11-12-07-766.png
>
>
> Adding documentation for the JSON Support feature



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7098) Document JSON functionality on the Phoenix Site

[Ranganath Govardhanagiri (Jira)]

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

Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: Adding_JSON_Support_documentation.patch

> Document JSON functionality on the Phoenix Site
> ---
>
> Key: PHOENIX-7098
> URL: https://issues.apache.org/jira/browse/PHOENIX-7098
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Ranganath Govardhanagiri
>Assignee: Ranganath Govardhanagiri
>Priority: Major
> Attachments: Adding_JSON_Support_documentation.patch, JSON Support in 
> Features dropdown menu.png, Json Datatype info.png, Json Datatype.png, Json 
> Functions Index.png, Json Functions description.png, Json Support 
> Documentation.png, Json Support at the bottom.png, JsonSupport.pdf, 
> image-2023-12-08-11-12-07-766.png
>
>
> Adding documentation for the JSON Support feature



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7098) Document JSON functionality on the Phoenix Site

[Ranganath Govardhanagiri (Jira)]

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

Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: Json Support Documentation.png

> Document JSON functionality on the Phoenix Site
> ---
>
> Key: PHOENIX-7098
> URL: https://issues.apache.org/jira/browse/PHOENIX-7098
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Ranganath Govardhanagiri
>Assignee: Ranganath Govardhanagiri
>Priority: Major
> Attachments: Adding_JSON_Support_documentation_.patch, JSON Support 
> in Features dropdown menu.png, Json Datatype info.png, Json Datatype.png, 
> Json Functions Index.png, Json Functions description.png, Json Support 
> Documentation.png, Json Support at the bottom.png, JsonSupport.pdf, 
> image-2023-12-08-11-12-07-766.png
>
>
> Adding documentation for the JSON Support feature



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7098) Document JSON functionality on the Phoenix Site

[Ranganath Govardhanagiri (Jira)]

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

Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: (was: Json Support Documentation.png)

> Document JSON functionality on the Phoenix Site
> ---
>
> Key: PHOENIX-7098
> URL: https://issues.apache.org/jira/browse/PHOENIX-7098
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Ranganath Govardhanagiri
>Assignee: Ranganath Govardhanagiri
>Priority: Major
> Attachments: Adding_JSON_Support_documentation_.patch, JSON Support 
> in Features dropdown menu.png, Json Datatype info.png, Json Datatype.png, 
> Json Functions Index.png, Json Functions description.png, Json Support at the 
> bottom.png, JsonSupport.pdf, image-2023-12-08-11-12-07-766.png
>
>
> Adding documentation for the JSON Support feature



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (PHOENIX-7146) Use the embedded client when packaging phoenix-client into the PQS assembly

[Istvan Toth (Jira)]

Istvan Toth created PHOENIX-7146:


 Summary: Use the embedded client when packaging phoenix-client 
into the PQS assembly
 Key: PHOENIX-7146
 URL: https://issues.apache.org/jira/browse/PHOENIX-7146
 Project: Phoenix
  Issue Type: Bug
  Components: queryserver
Reporter: Istvan Toth


We are packing phoenix-client into the assmbly, which may cause issues with 
logging.
Use the -embedded client by default.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (PHOENIX-7145) Use embedded client in PQS startup script

[Istvan Toth (Jira)]

Istvan Toth created PHOENIX-7145:


 Summary: Use embedded client in PQS startup script
 Key: PHOENIX-7145
 URL: https://issues.apache.org/jira/browse/PHOENIX-7145
 Project: Phoenix
  Issue Type: Bug
  Components: queryserver
Reporter: Istvan Toth


We have made logging configurable in the queryserver.py script, and we add the 
required JARs to to the classpath.

However, the user may supply the old non-embedded jar (or both variants)

Try to find the embedded client JAR first, and log a warning if we only find 
the non-embedded variant (by file name pattern).




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-6992) Upgrade Guava to 32.1.1

[Rajeshbabu Chintaguntla (Jira)]

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

Rajeshbabu Chintaguntla updated PHOENIX-6992:
-
Fix Version/s: thirdparty-2.1.0
   (was: thirdparty-2.0.1)

> Upgrade Guava to 32.1.1
> ---
>
> Key: PHOENIX-6992
> URL: https://issues.apache.org/jira/browse/PHOENIX-6992
> Project: Phoenix
>  Issue Type: Task
>  Components: thirdparty
>Reporter: Richárd Antal
>Assignee: Richárd Antal
>Priority: Major
> Fix For: thirdparty-2.1.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7080) Switch phoenix-thirdparty to guava-jre from guava-android

[Rajeshbabu Chintaguntla (Jira)]

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

Rajeshbabu Chintaguntla updated PHOENIX-7080:
-
Fix Version/s: thirdparty-2.1.0
   (was: thirdparty-2.0.1)

> Switch phoenix-thirdparty to guava-jre from guava-android
> -
>
> Key: PHOENIX-7080
> URL: https://issues.apache.org/jira/browse/PHOENIX-7080
> Project: Phoenix
>  Issue Type: Improvement
>  Components: thirdparty
>Affects Versions: thirdparty-2.0.0
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
> Fix For: thirdparty-2.1.0
>
>
> As discussed in mail thread, here, we want to switch to guava-jre from 
> guava-android for phoenix thirdparty
> Some more context on why we want to do this (Copied from PHOENIX-6817) is as 
> below:
> {quote}We chose to include the -android variant of Guava, to ensure 
> compatibiity with Java 7, which was required by the 4.x branch.
> Now that the 4.x branch is EOL, we can switch to the more standard -jre 
> version.
> {quote}
> CC: [~stoty] [~rajeshbabu] [~vjasani] 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7142) Bump phoenix-thirdparty version to 2.1

[Rajeshbabu Chintaguntla (Jira)]

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

Rajeshbabu Chintaguntla updated PHOENIX-7142:
-
Fix Version/s: thirdparty-2.1.0
   (was: 2.1.0)

> Bump phoenix-thirdparty version to 2.1
> --
>
> Key: PHOENIX-7142
> URL: https://issues.apache.org/jira/browse/PHOENIX-7142
> Project: Phoenix
>  Issue Type: Task
>  Components: thirdparty
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
> Fix For: thirdparty-2.1.0
>
>
> Changing the Guava variant is a relatively big change.
> Bump the minor version to 2.1



--
This message was sent by Atlassian Jira
(v8.20.10#820010)