[jira] [Updated] (PHOENIX-4822) The configuration "phoenix.query.dateFormatTimeZone" does't work on the client
[ https://issues.apache.org/jira/browse/PHOENIX-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai Zhang updated PHOENIX-4822: -- Attachment: PHOENIX-4822_v3.patch > The configuration "phoenix.query.dateFormatTimeZone" does't work on the client > -- > > Key: PHOENIX-4822 > URL: https://issues.apache.org/jira/browse/PHOENIX-4822 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.12.0, 4.13.0, 4.14.0, 5.0.0 >Reporter: Jaanai Zhang >Assignee: Jaanai Zhang >Priority: Major > Fix For: 4.15.0, 5.1.0 > > Attachments: PHOENIX-4822.patch, PHOENIX-4822_v2.patch, > PHOENIX-4822_v3.patch > > > when add configuration "phoenix.query.dateFormatTimeZone" into hbase-site.xml > or Properites of Connection, it can not work still uses time zone with GTM -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-4181) Drop tenant views columns when base view column is dropped
[ https://issues.apache.org/jira/browse/PHOENIX-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4181: Labels: SFDC (was: ) > Drop tenant views columns when base view column is dropped > -- > > Key: PHOENIX-4181 > URL: https://issues.apache.org/jira/browse/PHOENIX-4181 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.12.0 >Reporter: Vincent Poon >Priority: Major > Labels: SFDC > Attachments: PHOENIX-4181_test.master.patch > > > If you create a base table, a base view on the base table, and then a tenant > view on the base view, when a base view column is dropped, it should get > dropped from the tenant views as well. > This is currently not happening. See the attached test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] phoenix issue #308: Client-side hash aggregation
Github user geraldss commented on the issue: https://github.com/apache/phoenix/pull/308 Hi @JamesRTaylor, I pushed another change and replied with some comments. Please review, thanks. ---
[GitHub] phoenix pull request #313: PHOENIX-4799 Write cells using checkAndMutate to ...
Github user ankitsinghal commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/313#discussion_r205594858
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java ---
@@ -3604,6 +3675,17 @@ public MutationState addColumn(PTable table,
List origColumnDefs,
}
} finally {
connection.setAutoCommit(wasAutoCommit);
+if (!columns.isEmpty()) {
+for (PColumn pColumn : columns) {
+PName physicalName = table.getPhysicalName();
+String physicalSchemaName =
+
SchemaUtil.getSchemaNameFromFullName(physicalName.getString());
+String physicalTableName =
+
SchemaUtil.getTableNameFromFullName(physicalName.getString());
+deleteCell(null, physicalSchemaName, physicalTableName,
--- End diff --
@twdsilva , shouldn't you check whether you have acquired a lock(or
inserted the cell in Mutex) before deleting the lock cell, because here you
might be deleting the locks acquired by some other threads. And, You may need
to do this per column I think.
---
[GitHub] phoenix pull request #313: PHOENIX-4799 Write cells using checkAndMutate to ...
Github user ankitsinghal commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/313#discussion_r205595041
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java ---
@@ -3034,6 +3088,11 @@ MutationState dropTable(String schemaName, String
tableName, String parentTableN
return new MutationState(0, 0, connection);
} finally {
connection.setAutoCommit(wasAutoCommit);
+// acquire a mutex on the table to prevent creating views
while concurrently
+// dropping the base table
+if (tableType == PTableType.TABLE) {
+deleteCell(null, schemaName, tableName, null);
+}
--- End diff --
nit: Please update the comment here that you are releasing a mutex.
---
[jira] [Assigned] (PHOENIX-4798) Update encoded col qualifiers on the base table correctly
[ https://issues.apache.org/jira/browse/PHOENIX-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva reassigned PHOENIX-4798: --- Assignee: Thomas D'Silva > Update encoded col qualifiers on the base table correctly > - > > Key: PHOENIX-4798 > URL: https://issues.apache.org/jira/browse/PHOENIX-4798 > Project: Phoenix > Issue Type: Sub-task >Reporter: Thomas D'Silva >Assignee: Thomas D'Silva >Priority: Major > > For tables that use column qualifier encoding, when a column is added or view > created we update the encoded column qualifier on the base table and > increment its sequence number. > Add a check to see if the base table is at the expected sequence number and > fail if it is not with a CONCURRENT_TABLE_MUTATION -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [DISCUSS] reduce notifications to phoenix-dev list
Josh, Only apache members or pmc chairs can create a new mailing list ( https://selfserve.apache.org/mail.html). Can you create iss...@phoenix.apache.org? Thanks, Thomas On Wed, Jul 25, 2018 at 9:20 AM, Josh Elser wrote: > I think this would be a nice thing to do. > > > On 7/24/18 8:17 PM, Thomas D'Silva wrote: > >> Do folks think we need an issues mailing list similar to HBase that will >> receive notifications about comments? >> >> On Tue, Jul 24, 2018 at 5:10 PM, Thomas D'Silva >> wrote: >> >> Thanks Josh, I filed an INFRA Jira and updated the notification scheme. >>> dev@phoenix.apache.org will no longer receive notifications when an >>> issue >>> is commented on or a comment is edited/deleted. >>> >>> On Thu, Jul 12, 2018 at 1:41 PM, Josh Elser >>> wrote: >>> >>> I think INFRA keeps these locked down. Just requires an INFRA JIRA issue, I'd guess asking them to change it. On 7/12/18 1:53 PM, Thomas D'Silva wrote: Josh, > > Do you know how to edit the notification scheme here > https://issues.apache.org/jira/plugins/servlet/project-confi > g/PHOENIX/notifications > ? > I don't see an edit button. > > Thanks, > Thomas > > On Thu, Jul 12, 2018 at 7:09 AM, James Taylor > wrote: > > +1 > >> >> On Thu, Jul 12, 2018 at 5:51 AM Josh Elser >> wrote: >> >> Fine by me. >> >>> >>> On 7/11/18 9:50 PM, Thomas D'Silva wrote: >>> >>> I think we should reduce the number of notifications that are sent to the >>> >> >> phoenix-dev list. >>> The notification scheme we use is located here : https://issues.apache.org/ >>> >>> jira/plugins/servlet/project-config/PHOENIX/notifications Maybe we don't need to notify the dev list when an issue is updated, or a >>> >> >> comment is created/edited/deleted. People watching a particular issue >>> would >>> >>> still see all the changes. This would be similar to how other projects like HBase and Calcite operate. >>> >>> Thanks, Thomas >>> >> > >>> >>
[jira] [Updated] (PHOENIX-4799) Write cells using checkAndMutate to prevent conflicting changes
[ https://issues.apache.org/jira/browse/PHOENIX-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4799: Attachment: (was: PHOENIX-4799.patch) > Write cells using checkAndMutate to prevent conflicting changes > --- > > Key: PHOENIX-4799 > URL: https://issues.apache.org/jira/browse/PHOENIX-4799 > Project: Phoenix > Issue Type: Sub-task >Affects Versions: 4.15.0, 5.1.0 >Reporter: Thomas D'Silva >Assignee: Thomas D'Silva >Priority: Major > Attachments: PHOENIX-4799-v2.patch > > > In order to prevent race conditions when multiple client try to mutate the > same column before sending the request to mutate the column to the server do > a checkAndMutate with the column name being added/dropped. Also: > 1. When a view is created do a checkAndMutate with the columns in the view > where clause. > 2. When an index on a view is created do a checkAndMutate with the indexed > columns. > > To prevent a race condition in the DROP TABLE CASCADE case, when a table is > dropped do a checkAndMutate with the rowkey of the base table name. If a view > is created it also does a checkAndMutate with the same rowkey. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-4822) The configuration "phoenix.query.dateFormatTimeZone" does't work on the client
[ https://issues.apache.org/jira/browse/PHOENIX-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-4822: Fix Version/s: 5.1.0 4.15.0 > The configuration "phoenix.query.dateFormatTimeZone" does't work on the client > -- > > Key: PHOENIX-4822 > URL: https://issues.apache.org/jira/browse/PHOENIX-4822 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.12.0, 4.13.0, 4.14.0, 5.0.0 >Reporter: Jaanai Zhang >Assignee: Jaanai Zhang >Priority: Major > Fix For: 4.15.0, 5.1.0 > > Attachments: PHOENIX-4822.patch, PHOENIX-4822_v2.patch > > > when add configuration "phoenix.query.dateFormatTimeZone" into hbase-site.xml > or Properites of Connection, it can not work still uses time zone with GTM -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (PHOENIX-4822) The configuration "phoenix.query.dateFormatTimeZone" does't work on the client
[ https://issues.apache.org/jira/browse/PHOENIX-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser reassigned PHOENIX-4822: --- Assignee: Jaanai Zhang > The configuration "phoenix.query.dateFormatTimeZone" does't work on the client > -- > > Key: PHOENIX-4822 > URL: https://issues.apache.org/jira/browse/PHOENIX-4822 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.12.0, 4.13.0, 4.14.0, 5.0.0 >Reporter: Jaanai Zhang >Assignee: Jaanai Zhang >Priority: Major > Fix For: 4.15.0, 5.1.0 > > Attachments: PHOENIX-4822.patch, PHOENIX-4822_v2.patch > > > when add configuration "phoenix.query.dateFormatTimeZone" into hbase-site.xml > or Properites of Connection, it can not work still uses time zone with GTM -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-4823) Issue with Maven Dependencies
[
https://issues.apache.org/jira/browse/PHOENIX-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine updated PHOENIX-4823:
-
Description:
There is a runtime error using phoenix 5.0.0-HBase-2.0 with java and maven. The
exception is when the following method is called:
DriverManager.getConnection("jdbc:phoenix:localhost");
The problem is from hadoop-auth which is included twice in 2 different versions
in the dependency tree. The fix is to do the following:
org.apache.phoenix
phoenix-core
5.0.0-HBase-2.0
org.apache.hadoop
hadoop-auth
org.apache.hadoop
hadoop-auth
3.0.0
was:
There is a runtime error using phoenix 5.0.0-HBase-2.0 with java and maven. The
exception is when the following method is called:
DriverManager.getConnection("jdbc:phoenix:localhost");
The problem is from hadoop-auth which is included twice in 2 different versions
in the dependency tree. The fix is to do the followingL
org.apache.phoenix
phoenix-core
5.0.0-HBase-2.0
org.apache.hadoop
hadoop-auth
org.apache.hadoop
hadoop-auth
3.0.0
> Issue with Maven Dependencies
> -
>
> Key: PHOENIX-4823
> URL: https://issues.apache.org/jira/browse/PHOENIX-4823
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 5.0.0
>Reporter: Antoine
>Priority: Major
> Fix For: 5.0.0
>
>
> There is a runtime error using phoenix 5.0.0-HBase-2.0 with java and maven.
> The exception is when the following method is called:
> DriverManager.getConnection("jdbc:phoenix:localhost");
>
> The problem is from hadoop-auth which is included twice in 2 different
> versions in the dependency tree. The fix is to do the following:
>
>
>
> org.apache.phoenix
> phoenix-core
> 5.0.0-HBase-2.0
>
>
> org.apache.hadoop
> hadoop-auth
>
>
>
>
> org.apache.hadoop
> hadoop-auth
> 3.0.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (PHOENIX-4823) Issue with Maven Dependencies
Antoine created PHOENIX-4823:
Summary: Issue with Maven Dependencies
Key: PHOENIX-4823
URL: https://issues.apache.org/jira/browse/PHOENIX-4823
Project: Phoenix
Issue Type: Bug
Affects Versions: 5.0.0
Reporter: Antoine
Fix For: 5.0.0
There is a runtime error using phoenix 5.0.0-HBase-2.0 with java and maven. The
exception is when the following method is called:
DriverManager.getConnection("jdbc:phoenix:localhost");
The problem is from hadoop-auth which is included twice in 2 different versions
in the dependency tree. The fix is to do the followingL
org.apache.phoenix
phoenix-core
5.0.0-HBase-2.0
org.apache.hadoop
hadoop-auth
org.apache.hadoop
hadoop-auth
3.0.0
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] phoenix issue #311: PHOENIX-4817 Fixed Phoenix Tracing Web Application
Github user mygood commented on the issue: https://github.com/apache/phoenix/pull/311 trace on not data into trace table I use apache-phoenix-4.13.1-HBase-1.1-bin and hbase-1.1.6 and hadoop-2.7.1 cp $PHOENIX_HOME/phoenix-4.13.1-HBase-1.1-server.jar $HBASE_HOME/lib cp $PHOENIX_HOME/bin/hadoop-metrics2-hbase.properties $HBASE_HOME/conf cp $PHOENIX_HOME/bin/hadoop-metrics2-phoenix.properties $HBASE_HOME/conf add hbase-sit.xml phoenix.trace.frequency always phoenix.trace.statsTableName SYSTEM.TRACING_STATS phoenix.trace.frequency true run sqlline.py create SYSTEM.TRACING_STATS CREATE TABLE SYSTEM.TRACING_STATS ( trace_id BIGINT NOT NULL, parent_id BIGINT NOT NULL, span_id BIGINT NOT NULL, description VARCHAR, start_time BIGINT, end_time BIGINT, hostname VARCHAR, tags.count SMALLINT, annotations.count SMALLINT, CONSTRAINT pk PRIMARY KEY (trace_id, parent_id, span_id) ) 0: jdbc:phoenix:localhost:2181:/hbase> trace on; --- trace_id --- -7450651397611882467 --- 1 row selected (0.001 seconds) 0: jdbc:phoenix:localhost:2181:/hbase> create table t(a bigint not null PRIMARY key,b bigint); No rows affected (2.523 seconds) 0: jdbc:phoenix:localhost:2181:/hbase> !ta + TABLE_CAT TABLE_SCHEM TABLE_NAME TABLE_TYPE REMARKS TYPE_NAME SELF_REFERENCING_COL_NAME REF_GENERATIO + SYSTEM CATALOG SYSTEM TABLE SYSTEM FUNCTIONSYSTEM TABLE SYSTEM SEQUENCESYSTEM TABLE SYSTEM STATS SYSTEM TABLE SYSTEM TRACING_STATS SYSTEM TABLE T TABLE + 0: jdbc:phoenix:localhost:2181:/hbase> upsert into t(a,b) values(1,1); 1 row affected (0.046 seconds) 0: jdbc:phoenix:localhost:2181:/hbase> select * from SYSTEM.TRACING_STATS where trace_id=-7450651397611882467; -- TRACE_IDPARENT_ID SPAN_ID DESCRIPTION START_TIME END_TIME HOSTNAMECOUNT COUNT -- -- No rows selected (0.09 seconds) 0: jdbc:phoenix:localhost:2181:/hbase> select * from SYSTEM.TRACING_STATS; -- TRACE_IDPARENT_ID SPAN_ID DESCRIPTION START_TIME END_TIME HOSTNAMECOUNT COUNT -- -- No rows selected (0.09 seconds) @MrSandmanRUS @joshelser ---
[jira] [Updated] (PHOENIX-4815) support alter table modify column
[
https://issues.apache.org/jira/browse/PHOENIX-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaanai Zhang updated PHOENIX-4815:
--
Affects Version/s: 4.12.0
> support alter table modify column
> --
>
> Key: PHOENIX-4815
> URL: https://issues.apache.org/jira/browse/PHOENIX-4815
> Project: Phoenix
> Issue Type: Improvement
>Affects Versions: 4.12.0
>Reporter: Jaanai Zhang
>Priority: Major
> Attachments: PHOENIX-4815.patch
>
>
> if we want to change max length or scale of fields of variable length type(
> example for :varchar, char and decimal type etc), we can not drop column to
> recreate new column when the table has massive data, which may affects
> online service，meanwhile, it is also very expensive. so sometimes this
> function is very useful.
> Taking ORACLE dialect as an reference
> {code:java}
> alter table
>table_name
> modify
>column_name datatype;
> {code}
> reference link:
> https://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_3001.htm#i2103956
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (PHOENIX-4822) The configuration "phoenix.query.dateFormatTimeZone" does't work on the client
[ https://issues.apache.org/jira/browse/PHOENIX-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai Zhang updated PHOENIX-4822: -- Affects Version/s: (was: 4.11.0) > The configuration "phoenix.query.dateFormatTimeZone" does't work on the client > -- > > Key: PHOENIX-4822 > URL: https://issues.apache.org/jira/browse/PHOENIX-4822 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.12.0, 4.13.0, 4.14.0, 5.0.0 >Reporter: Jaanai Zhang >Priority: Major > Attachments: PHOENIX-4822.patch, PHOENIX-4822_v2.patch > > > when add configuration "phoenix.query.dateFormatTimeZone" into hbase-site.xml > or Properites of Connection, it can not work still uses time zone with GTM -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-4822) The configuration "phoenix.query.dateFormatTimeZone" does't work on the client
[ https://issues.apache.org/jira/browse/PHOENIX-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai Zhang updated PHOENIX-4822: -- Affects Version/s: 4.13.0 > The configuration "phoenix.query.dateFormatTimeZone" does't work on the client > -- > > Key: PHOENIX-4822 > URL: https://issues.apache.org/jira/browse/PHOENIX-4822 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.12.0, 4.13.0, 4.14.0, 5.0.0 >Reporter: Jaanai Zhang >Priority: Major > Attachments: PHOENIX-4822.patch, PHOENIX-4822_v2.patch > > > when add configuration "phoenix.query.dateFormatTimeZone" into hbase-site.xml > or Properites of Connection, it can not work still uses time zone with GTM -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-4822) The configuration "phoenix.query.dateFormatTimeZone" does't work on the client
[ https://issues.apache.org/jira/browse/PHOENIX-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai Zhang updated PHOENIX-4822: -- Attachment: PHOENIX-4822_v2.patch > The configuration "phoenix.query.dateFormatTimeZone" does't work on the client > -- > > Key: PHOENIX-4822 > URL: https://issues.apache.org/jira/browse/PHOENIX-4822 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.11.0, 4.12.0, 4.14.0, 5.0.0 >Reporter: Jaanai Zhang >Priority: Major > Attachments: PHOENIX-4822.patch, PHOENIX-4822_v2.patch > > > when add configuration "phoenix.query.dateFormatTimeZone" into hbase-site.xml > or Properites of Connection, it can not work still uses time zone with GTM -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-4822) The configuration "phoenix.query.dateFormatTimeZone" does't work on the client
[ https://issues.apache.org/jira/browse/PHOENIX-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai Zhang updated PHOENIX-4822: -- Affects Version/s: 4.14.0 5.0.0 > The configuration "phoenix.query.dateFormatTimeZone" does't work on the client > -- > > Key: PHOENIX-4822 > URL: https://issues.apache.org/jira/browse/PHOENIX-4822 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.11.0, 4.12.0, 4.14.0, 5.0.0 >Reporter: Jaanai Zhang >Priority: Major > Attachments: PHOENIX-4822.patch, PHOENIX-4822_v2.patch > > > when add configuration "phoenix.query.dateFormatTimeZone" into hbase-site.xml > or Properites of Connection, it can not work still uses time zone with GTM -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-4822) The configuration "phoenix.query.dateFormatTimeZone" does't work on the client
[ https://issues.apache.org/jira/browse/PHOENIX-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai Zhang updated PHOENIX-4822: -- Attachment: (was: PHOENIX-4822.patch_v2) > The configuration "phoenix.query.dateFormatTimeZone" does't work on the client > -- > > Key: PHOENIX-4822 > URL: https://issues.apache.org/jira/browse/PHOENIX-4822 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.11.0, 4.12.0 >Reporter: Jaanai Zhang >Priority: Major > Attachments: PHOENIX-4822.patch > > > when add configuration "phoenix.query.dateFormatTimeZone" into hbase-site.xml > or Properites of Connection, it can not work still uses time zone with GTM -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-4822) The configuration "phoenix.query.dateFormatTimeZone" does't work on the client
[ https://issues.apache.org/jira/browse/PHOENIX-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai Zhang updated PHOENIX-4822: -- Attachment: (was: PHOENIX-4822.patch_v2) > The configuration "phoenix.query.dateFormatTimeZone" does't work on the client > -- > > Key: PHOENIX-4822 > URL: https://issues.apache.org/jira/browse/PHOENIX-4822 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.11.0, 4.12.0 >Reporter: Jaanai Zhang >Priority: Major > Attachments: PHOENIX-4822.patch, PHOENIX-4822.patch_v2 > > > when add configuration "phoenix.query.dateFormatTimeZone" into hbase-site.xml > or Properites of Connection, it can not work still uses time zone with GTM -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-4822) The configuration "phoenix.query.dateFormatTimeZone" does't work on the client
[ https://issues.apache.org/jira/browse/PHOENIX-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai Zhang updated PHOENIX-4822: -- Attachment: PHOENIX-4822.patch_v2 > The configuration "phoenix.query.dateFormatTimeZone" does't work on the client > -- > > Key: PHOENIX-4822 > URL: https://issues.apache.org/jira/browse/PHOENIX-4822 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.11.0, 4.12.0 >Reporter: Jaanai Zhang >Priority: Major > Attachments: PHOENIX-4822.patch, PHOENIX-4822.patch_v2 > > > when add configuration "phoenix.query.dateFormatTimeZone" into hbase-site.xml > or Properites of Connection, it can not work still uses time zone with GTM -- This message was sent by Atlassian JIRA (v7.6.3#76005)
