[jira] [Assigned] (PHOENIX-6261) Reorganise project structure to make mvn versions:set work
[ https://issues.apache.org/jira/browse/PHOENIX-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal reassigned PHOENIX-6261: -- Assignee: Richard Antal > Reorganise project structure to make mvn versions:set work > -- > > Key: PHOENIX-6261 > URL: https://issues.apache.org/jira/browse/PHOENIX-6261 > Project: Phoenix > Issue Type: Task > Components: connectors, core >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6261) Reorganise project structure to make mvn versions:set work
Richard Antal created PHOENIX-6261: -- Summary: Reorganise project structure to make mvn versions:set work Key: PHOENIX-6261 URL: https://issues.apache.org/jira/browse/PHOENIX-6261 Project: Phoenix Issue Type: Task Components: connectors, core Reporter: Richard Antal -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OMID-192) fix missing jcommander dependency
[
https://issues.apache.org/jira/browse/OMID-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243966#comment-17243966
]
Richard Antal commented on OMID-192:
Thanks [~stoty] for the fix and for the further details!
> fix missing jcommander dependency
> -
>
> Key: OMID-192
> URL: https://issues.apache.org/jira/browse/OMID-192
> Project: Phoenix Omid
> Issue Type: Bug
>Reporter: Richard Antal
>Assignee: Istvan Toth
>Priority: Major
>
> When I started the the _omid.sh create-hbase-commit-table
> I got the following exception:
> {code:java}
> Error: A JNI error has occurred, please check your installation and try again
> Exception in thread "main" java.lang.NoClassDefFoundError:
> com/beust/jcommander/ParameterException{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OMID-192) fix missing jcommander dependency
[
https://issues.apache.org/jira/browse/OMID-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated OMID-192:
---
Description:
When I started the the _omid.sh create-hbase-commit-table
I got the following exception:
{code:java}
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.NoClassDefFoundError:
com/beust/jcommander/ParameterException{code}
was:
When I started the the **_omid.sh create-hbase-commit-table
_I got the following exception:
{code:java}
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.NoClassDefFoundError:
com/beust/jcommander/ParameterException{code}
> fix missing jcommander dependency
> -
>
> Key: OMID-192
> URL: https://issues.apache.org/jira/browse/OMID-192
> Project: Phoenix Omid
> Issue Type: Bug
>Reporter: Richard Antal
>Assignee: Istvan Toth
>Priority: Major
>
> When I started the the _omid.sh create-hbase-commit-table
> I got the following exception:
> {code:java}
> Error: A JNI error has occurred, please check your installation and try again
> Exception in thread "main" java.lang.NoClassDefFoundError:
> com/beust/jcommander/ParameterException{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OMID-192) fix missing jcommander dependency
[
https://issues.apache.org/jira/browse/OMID-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated OMID-192:
---
Description:
When I started the the **_omid.sh create-hbase-commit-table
_I got the following exception:
{code:java}
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.NoClassDefFoundError:
com/beust/jcommander/ParameterException{code}
was:
When I started the the **_omid.sh create-hbase-commit-table
_I got the following exception:
{{}}
{code:java}
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.NoClassDefFoundError:
com/beust/jcommander/ParameterException{code}
> fix missing jcommander dependency
> -
>
> Key: OMID-192
> URL: https://issues.apache.org/jira/browse/OMID-192
> Project: Phoenix Omid
> Issue Type: Bug
>Reporter: Richard Antal
>Assignee: Istvan Toth
>Priority: Major
>
> When I started the the **_omid.sh create-hbase-commit-table
> _I got the following exception:
> {code:java}
> Error: A JNI error has occurred, please check your installation and try again
> Exception in thread "main" java.lang.NoClassDefFoundError:
> com/beust/jcommander/ParameterException{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OMID-192) fix missing jcommander dependency
[
https://issues.apache.org/jira/browse/OMID-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated OMID-192:
---
Summary: fix missing jcommander dependency (was: fix missing jcommander)
> fix missing jcommander dependency
> -
>
> Key: OMID-192
> URL: https://issues.apache.org/jira/browse/OMID-192
> Project: Phoenix Omid
> Issue Type: Bug
>Reporter: Richard Antal
>Priority: Major
>
> When I started the the **_omid.sh create-hbase-commit-table
> _I got the following exception:
> {{}}
> {code:java}
> Error: A JNI error has occurred, please check your installation and try again
> Exception in thread "main" java.lang.NoClassDefFoundError:
> com/beust/jcommander/ParameterException{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (OMID-192) fix missing jcommander
Richard Antal created OMID-192:
--
Summary: fix missing jcommander
Key: OMID-192
URL: https://issues.apache.org/jira/browse/OMID-192
Project: Phoenix Omid
Issue Type: Bug
Reporter: Richard Antal
When I started the the **_omid.sh create-hbase-commit-table
_I got the following exception:
{{}}
{code:java}
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.NoClassDefFoundError:
com/beust/jcommander/ParameterException{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (TEPHRA-316) Fix missing executable permission because of MASSEMBLY-941
[ https://issues.apache.org/jira/browse/TEPHRA-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal closed TEPHRA-316. Resolution: Not A Problem > Fix missing executable permission because of MASSEMBLY-941 > -- > > Key: TEPHRA-316 > URL: https://issues.apache.org/jira/browse/TEPHRA-316 > Project: Phoenix Tephra > Issue Type: Bug >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (TEPHRA-316) Fix missing executable permission because of MASSEMBLY-941
Richard Antal created TEPHRA-316: Summary: Fix missing executable permission because of MASSEMBLY-941 Key: TEPHRA-316 URL: https://issues.apache.org/jira/browse/TEPHRA-316 Project: Phoenix Tephra Issue Type: Bug Reporter: Richard Antal Assignee: Poorna Chandra -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6238) Fix missing executable permission because of MASSEMBLY-941
[ https://issues.apache.org/jira/browse/PHOENIX-6238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal reassigned PHOENIX-6238: -- Assignee: Richard Antal > Fix missing executable permission because of MASSEMBLY-941 > -- > > Key: PHOENIX-6238 > URL: https://issues.apache.org/jira/browse/PHOENIX-6238 > Project: Phoenix > Issue Type: Bug > Components: connectors, queryserver >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6238) Fix missing executable permission because of MASSEMBLY-941
Richard Antal created PHOENIX-6238: -- Summary: Fix missing executable permission because of MASSEMBLY-941 Key: PHOENIX-6238 URL: https://issues.apache.org/jira/browse/PHOENIX-6238 Project: Phoenix Issue Type: Bug Components: connectors, queryserver Reporter: Richard Antal -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OMID-191) Fix missing executable permission because of MASSEMBLY-941
Richard Antal created OMID-191: -- Summary: Fix missing executable permission because of MASSEMBLY-941 Key: OMID-191 URL: https://issues.apache.org/jira/browse/OMID-191 Project: Phoenix Omid Issue Type: Bug Reporter: Richard Antal -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6233) QueryTimeoutIT fails sometimes.
[
https://issues.apache.org/jira/browse/PHOENIX-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated PHOENIX-6233:
---
Attachment: PHOENIX-6233.4.x.v1.patch
> QueryTimeoutIT fails sometimes.
> ---
>
> Key: PHOENIX-6233
> URL: https://issues.apache.org/jira/browse/PHOENIX-6233
> Project: Phoenix
> Issue Type: Task
>Reporter: Richard Antal
>Assignee: Richard Antal
>Priority: Minor
> Attachments: PHOENIX-6233.4.x.v1.patch, PHOENIX-6233.master.v1.patch
>
>
> On a faster computers QueryTimeoutIT does not take 1000 ms.
> Sometimes on my computer it runs well below it. I suggest increasing nRows
> to make it stable for some year.
> One of my failing run (MacBook Pro 16 9th-gen i7):
> {code:java}
> QueryTimeoutIT.testQueryTimeout:134 Total time of query was 852 ms, but
> expected to be greater than 1000{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-6233) QueryTimeoutIT fails sometimes.
[
https://issues.apache.org/jira/browse/PHOENIX-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated PHOENIX-6233:
---
Description:
On a faster computers QueryTimeoutIT does not take 1000 ms.
Sometimes on my computer it runs well below it. I suggest increasing nRows to
make it stable for some year.
One of my failing run (MacBook Pro 16 9th-gen i7):
{code:java}
QueryTimeoutIT.testQueryTimeout:134 Total time of query was 852 ms, but
expected to be greater than 1000{code}
was:
On a faster computers QueryTimeoutIT does not take 1000 ms.
Sometimes on my computer it runs well below it. I suggest increasing nRows to
make it stable for some year.
One of my failing run:
{code:java}
QueryTimeoutIT.testQueryTimeout:134 Total time of query was 852 ms, but
expected to be greater than 1000{code}
> QueryTimeoutIT fails sometimes.
> ---
>
> Key: PHOENIX-6233
> URL: https://issues.apache.org/jira/browse/PHOENIX-6233
> Project: Phoenix
> Issue Type: Task
>Reporter: Richard Antal
>Assignee: Richard Antal
>Priority: Minor
>
> On a faster computers QueryTimeoutIT does not take 1000 ms.
> Sometimes on my computer it runs well below it. I suggest increasing nRows
> to make it stable for some year.
> One of my failing run (MacBook Pro 16 9th-gen i7):
> {code:java}
> QueryTimeoutIT.testQueryTimeout:134 Total time of query was 852 ms, but
> expected to be greater than 1000{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (PHOENIX-6233) QueryTimeoutIT fails sometimes.
Richard Antal created PHOENIX-6233:
--
Summary: QueryTimeoutIT fails sometimes.
Key: PHOENIX-6233
URL: https://issues.apache.org/jira/browse/PHOENIX-6233
Project: Phoenix
Issue Type: Task
Reporter: Richard Antal
Assignee: Richard Antal
On a faster computers QueryTimeoutIT does not take 1000 ms.
Sometimes on my computer it runs well below it. I suggest increasing nRows to
make it stable for some year.
One of my failing run:
{code:java}
QueryTimeoutIT.testQueryTimeout:134 Total time of query was 852 ms, but
expected to be greater than 1000{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5066) The TimeZone is incorrectly used during writing or reading data
[
https://issues.apache.org/jira/browse/PHOENIX-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal reassigned PHOENIX-5066:
--
Assignee: (was: Richard Antal)
> The TimeZone is incorrectly used during writing or reading data
> ---
>
> Key: PHOENIX-5066
> URL: https://issues.apache.org/jira/browse/PHOENIX-5066
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 5.0.0, 4.14.1
>Reporter: Jaanai Zhang
>Priority: Critical
> Fix For: 5.1.1, 4.16.1, 4.17.0
>
> Attachments: DateTest.java, PHOENIX-5066.4x.v1.patch,
> PHOENIX-5066.4x.v2.patch, PHOENIX-5066.4x.v3.patch,
> PHOENIX-5066.master.v1.patch, PHOENIX-5066.master.v2.patch,
> PHOENIX-5066.master.v3.patch, PHOENIX-5066.master.v4.patch,
> PHOENIX-5066.master.v5.patch, PHOENIX-5066.master.v6.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We have two methods to write data when uses JDBC API.
> #1. Uses _the exceuteUpdate_ method to execute a string that is an upsert SQL.
> #2. Uses the _prepareStatement_ method to set some objects and execute.
> The _string_ data needs to convert to a new object by the schema information
> of tables. we'll use some date formatters to convert string data to object
> for Date/Time/Timestamp types when writes data and the formatters are used
> when reads data as well.
>
> *Uses default timezone test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 2 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 3 | 2018-12-10 | 15:45:07 | 2018-12-10 15:45:07.66
> {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 2 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 3 | 2018-12-10 07:45:07.660 | 2018-12-10 07:45:07.660 | 2018-12-10
> 07:45:07.660
> {code}
> *Uses GMT+8 test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:40:47 | 2018-12-10 23:40:47.0
> 2 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.0
> 3 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.106 {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 23:40:47.000 | 2018-12-10 23:40:47.000 | 2018-12-10
> 23:40:47.000
> 2 | 2018-12-10 15:40:47.000 | 2018-12-10 15:40:47.000 | 2018-12-10
> 15:40:47.000
> 3 | 2018-12-10 15:40:47.106 | 2018-12-10 15:40:47.106 | 2018-12-10
> 15:40:47.106
> {code}
>
> _We_ have a historical problem, we'll parse the string to
> Date/Time/Timestamp objects with timezone in #1, which means the actual data
> is going to be changed when stored in HBase table。
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6083) View index creation does a checkAndPut on an incorrect row key
[ https://issues.apache.org/jira/browse/PHOENIX-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal resolved PHOENIX-6083. Resolution: Resolved > View index creation does a checkAndPut on an incorrect row key > -- > > Key: PHOENIX-6083 > URL: https://issues.apache.org/jira/browse/PHOENIX-6083 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.15.0 >Reporter: Chinmay Kulkarni >Assignee: Richard Antal >Priority: Critical > Labels: phoenix-hardening, quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: image-2020-08-18-11-09-35-080.png, > image-2020-08-18-11-09-53-816.png > > > When creating a view index, we "lock" on the indexed and included columns by > doing a checkAndPut on the cell: > (, , the indexed/included column>) > This is done to prevent another client from concurrently dropping any of the > indexed/included columns. This however, is not working as expected since the > indexed column naming convention is different (:) > rather than just . > Thus, concurrent dropping of the column is not prevented and this leads to > failure in view index creation with either an NPE or IllegalArgumentException. > !image-2020-08-18-11-09-35-080.png! > !image-2020-08-18-11-09-53-816.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6091) Calling MetaDataProtocol.getVersion() on a 4.16 timestamp gives version as 4.15.x
[ https://issues.apache.org/jira/browse/PHOENIX-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-6091: --- Attachment: PHOENIX-6091.4.x.v2.patch > Calling MetaDataProtocol.getVersion() on a 4.16 timestamp gives version as > 4.15.x > - > > Key: PHOENIX-6091 > URL: https://issues.apache.org/jira/browse/PHOENIX-6091 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Chinmay Kulkarni >Priority: Minor > Fix For: 4.16.0 > > Attachments: PHOENIX-6091.4.x.v1.patch, PHOENIX-6091.4.x.v2.patch > > > This is probably because we haven't added an entry for 4.16 in the > MetaDataProtocol.TIMESTAMP_VERSION_MAP -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6197) AggregateIT and StoreNullsIT hangs
[ https://issues.apache.org/jira/browse/PHOENIX-6197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal reassigned PHOENIX-6197: -- Assignee: Richard Antal > AggregateIT and StoreNullsIT hangs > -- > > Key: PHOENIX-6197 > URL: https://issues.apache.org/jira/browse/PHOENIX-6197 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.1.0, 4.16.0 >Reporter: Istvan Toth >Assignee: Richard Antal >Priority: Blocker > > Recent 4.x builds don't finish. > The maven output shows that AggregateIT and StoreNullsIT are started, but > never complete. > All 4.x CI builds seem to be affected. > I can see the same hang on some master builds (on HBase 2.3, though that may > be a coincidence) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6083) View index creation does a checkAndPut on an incorrect row key
[ https://issues.apache.org/jira/browse/PHOENIX-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal reassigned PHOENIX-6083: -- Assignee: Richard Antal > View index creation does a checkAndPut on an incorrect row key > -- > > Key: PHOENIX-6083 > URL: https://issues.apache.org/jira/browse/PHOENIX-6083 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.15.0 >Reporter: Chinmay Kulkarni >Assignee: Richard Antal >Priority: Critical > Labels: phoenix-hardening, quality-improvement > Fix For: 5.1.0, 4.16.0 > > Attachments: image-2020-08-18-11-09-35-080.png, > image-2020-08-18-11-09-53-816.png > > > When creating a view index, we "lock" on the indexed and included columns by > doing a checkAndPut on the cell: > (, , the indexed/included column>) > This is done to prevent another client from concurrently dropping any of the > indexed/included columns. This however, is not working as expected since the > indexed column naming convention is different (:) > rather than just . > Thus, concurrent dropping of the column is not prevented and this leads to > failure in view index creation with either an NPE or IllegalArgumentException. > !image-2020-08-18-11-09-35-080.png! > !image-2020-08-18-11-09-53-816.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6085) Remove duplicate calls to getSysMutexPhysicalTableNameBytes() during the upgrade path
[ https://issues.apache.org/jira/browse/PHOENIX-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-6085: --- Comment: was deleted (was: You have already done the rebasing, thanks.) > 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: Richard Antal >Priority: Minor > Labels: phoenix-hardening, quality-improvement > Fix For: 5.1.0, 4.16.0 > > 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] [Assigned] (PHOENIX-6085) Remove duplicate calls to getSysMutexPhysicalTableNameBytes() during the upgrade path
[ https://issues.apache.org/jira/browse/PHOENIX-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal reassigned PHOENIX-6085: -- Assignee: Richard Antal > 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: Richard Antal >Priority: Minor > Labels: phoenix-hardening, quality-improvement > Fix For: 5.1.0, 4.16.0 > > 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] [Created] (PHOENIX-6180) Investigate flaky tests in Phoenix Connectors
Richard Antal created PHOENIX-6180: -- Summary: Investigate flaky tests in Phoenix Connectors Key: PHOENIX-6180 URL: https://issues.apache.org/jira/browse/PHOENIX-6180 Project: Phoenix Issue Type: Task Components: connectors Affects Versions: connectors-6.0.0 Reporter: Richard Antal Assignee: Richard Antal Fix For: connectors-6.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6166) Make Tephra support optional for phoenix 5 connectors
[ https://issues.apache.org/jira/browse/PHOENIX-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal reassigned PHOENIX-6166: -- Assignee: Richard Antal (was: Istvan Toth) > Make Tephra support optional for phoenix 5 connectors > - > > Key: PHOENIX-6166 > URL: https://issues.apache.org/jira/browse/PHOENIX-6166 > Project: Phoenix > Issue Type: Improvement > Components: connectors >Affects Versions: connectors-6.0.0 >Reporter: Istvan Toth >Assignee: Richard Antal >Priority: Major > > We should add an option to trigger the same optional exclusion that > PHOENIX-6064 added for the core components. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-5784) Phoenix-connectors doesn't work with phoenix master branch
[ https://issues.apache.org/jira/browse/PHOENIX-5784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal resolved PHOENIX-5784. Resolution: Resolved > Phoenix-connectors doesn't work with phoenix master branch > -- > > Key: PHOENIX-5784 > URL: https://issues.apache.org/jira/browse/PHOENIX-5784 > Project: Phoenix > Issue Type: Bug > Components: connectors >Affects Versions: connectors-6.0.0 >Reporter: Istvan Toth >Assignee: Richard Antal >Priority: Major > > phoenix-connectors cannot even be built against the master branch: > mvn clean package -Dphoenix.version=5.1.0-SNAPSHOT -Dhadoop-two.version=3.0.0 > -Dhbase.version=2.2.1 -fn > fails for about half of the modules. > Most of these problems are simple API changes, have some kind of solution in > the pre-split master branch, the question is how to make them coexist in a > repo/branch. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6165) Add Phoenix-Connectors assembly to create tarball of jar artifacts
Richard Antal created PHOENIX-6165: -- Summary: Add Phoenix-Connectors assembly to create tarball of jar artifacts Key: PHOENIX-6165 URL: https://issues.apache.org/jira/browse/PHOENIX-6165 Project: Phoenix Issue Type: Task Reporter: Richard Antal Assignee: Richard Antal -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6164) Rename phoenix4-compat and phoenix5-compat maven artifacts
[ https://issues.apache.org/jira/browse/PHOENIX-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal reassigned PHOENIX-6164: -- Assignee: Richard Antal > Rename phoenix4-compat and phoenix5-compat maven artifacts > -- > > Key: PHOENIX-6164 > URL: https://issues.apache.org/jira/browse/PHOENIX-6164 > Project: Phoenix > Issue Type: Improvement > Components: connectors >Affects Versions: connectors-6.0.0 >Reporter: Istvan Toth >Assignee: Richard Antal >Priority: Minor > > The new connectors build uses compatibility modules. > These have the coordinates org.apache.phoenix:phoenix4-compat and > org.apache.phoenix:phoenix5-compat > These artifacts are connectors-specific, yet this is not apparent from their > names. > Rename them so that the relation is immediately apparent, to something like > phoenix-connectors-phoenix4-compat . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6161) Update the building part of documentation for Phoenix Connectors
Richard Antal created PHOENIX-6161: -- Summary: Update the building part of documentation for Phoenix Connectors Key: PHOENIX-6161 URL: https://issues.apache.org/jira/browse/PHOENIX-6161 Project: Phoenix Issue Type: Task Reporter: Richard Antal Assignee: Richard Antal -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6128) Remove unused getAdmin() call inside CQSI.init()
[ https://issues.apache.org/jira/browse/PHOENIX-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal reassigned PHOENIX-6128: -- Attachment: PHOENIX-6128.4.x.v1.patch PHOENIX-6128.master.v1.patch Assignee: Richard Antal > Remove unused getAdmin() call inside CQSI.init() > > > Key: PHOENIX-6128 > URL: https://issues.apache.org/jira/browse/PHOENIX-6128 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0, 5.0.0 >Reporter: Chinmay Kulkarni >Assignee: Richard Antal >Priority: Minor > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-6128.4.x.v1.patch, PHOENIX-6128.master.v1.patch > > > A new HBase Admin object is created inside CQSI.init() > [here|https://github.com/apache/phoenix/blob/e3c7b4bdce2524eb4fd1e7eb0ccd3454fcca81ce/phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java#L3150], > however this is unused. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6152) Add phoenix-shaded-protobuf to phoenix-thirdparty.
[ https://issues.apache.org/jira/browse/PHOENIX-6152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-6152: --- Summary: Add phoenix-shaded-protobuf to phoenix-thirdparty. (was: Add phoenix-shaded-protobuf to phoenix-thirdpart.) > Add phoenix-shaded-protobuf to phoenix-thirdparty. > -- > > Key: PHOENIX-6152 > URL: https://issues.apache.org/jira/browse/PHOENIX-6152 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-6152.master.v1.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6152) Add phoenix-shaded-protobuf to phoenix-thirdpart.
Richard Antal created PHOENIX-6152: -- Summary: Add phoenix-shaded-protobuf to phoenix-thirdpart. Key: PHOENIX-6152 URL: https://issues.apache.org/jira/browse/PHOENIX-6152 Project: Phoenix Issue Type: Task Reporter: Richard Antal Assignee: Richard Antal -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OMID-162) Remove org.mortbay.log.Log and add junit dependency
[ https://issues.apache.org/jira/browse/OMID-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17196117#comment-17196117 ] Richard Antal commented on OMID-162: Hi, [~stoty], [~chrajeshbab...@gmail.com] Could you review this change please? > Remove org.mortbay.log.Log and add junit dependency > --- > > Key: OMID-162 > URL: https://issues.apache.org/jira/browse/OMID-162 > Project: Phoenix Omid > Issue Type: Task >Reporter: Richard Antal >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OMID-162) Remove org.mortbay.log.Log and add junit dependency
Richard Antal created OMID-162: -- Summary: Remove org.mortbay.log.Log and add junit dependency Key: OMID-162 URL: https://issues.apache.org/jira/browse/OMID-162 Project: Phoenix Omid Issue Type: Task Reporter: Richard Antal -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6113) Update website for building Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-6113: --- Attachment: HOENIX-6113.docs.v1.patch > Update website for building Phoenix > --- > > Key: PHOENIX-6113 > URL: https://issues.apache.org/jira/browse/PHOENIX-6113 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: HOENIX-6113.docs.v1.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6113) Update website for building Phoenix
Richard Antal created PHOENIX-6113: -- Summary: Update website for building Phoenix Key: PHOENIX-6113 URL: https://issues.apache.org/jira/browse/PHOENIX-6113 Project: Phoenix Issue Type: Task Reporter: Richard Antal Assignee: Richard Antal -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6103) Replace apache.commons.logging in Phoenix-Connectors
Richard Antal created PHOENIX-6103: -- Summary: Replace apache.commons.logging in Phoenix-Connectors Key: PHOENIX-6103 URL: https://issues.apache.org/jira/browse/PHOENIX-6103 Project: Phoenix Issue Type: Task Reporter: Richard Antal In the main Phoenix repo apache commons logging have been replaced with SLF4J some time ago. Try to do it in the connectors repo as well, if possible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6091) Calling MetaDataProtocol.getVersion() on a 4.16 timestamp gives version as 4.15.x
[ https://issues.apache.org/jira/browse/PHOENIX-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-6091: --- Attachment: PHOENIX-6091.4.x.v1.patch > Calling MetaDataProtocol.getVersion() on a 4.16 timestamp gives version as > 4.15.x > - > > Key: PHOENIX-6091 > URL: https://issues.apache.org/jira/browse/PHOENIX-6091 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Chinmay Kulkarni >Priority: Minor > Fix For: 4.16.0 > > Attachments: PHOENIX-6091.4.x.v1.patch > > > This is probably because we haven't added an entry for 4.16 in the > MetaDataProtocol.TIMESTAMP_VERSION_MAP -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6100) Update HBase-two version in phoenix connectors according to PHOENIX-6028
Richard Antal created PHOENIX-6100: -- Summary: Update HBase-two version in phoenix connectors according to PHOENIX-6028 Key: PHOENIX-6100 URL: https://issues.apache.org/jira/browse/PHOENIX-6100 Project: Phoenix Issue Type: Task Reporter: Richard Antal Assignee: Richard Antal -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6076) Refactor Phoenix Hive Connectors introduced by PHOENIX-6057
[ https://issues.apache.org/jira/browse/PHOENIX-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-6076: --- Description: Refactor Phoenix Hive connectors in a way we decrease code duplication by creating common source for multiple Hive connectors. We should add Hive 2 support as well in this change. was:Refactor Phoenix Hive connectors in a way we decrease code duplication by creating common source for multiple Hive connectors. > Refactor Phoenix Hive Connectors introduced by PHOENIX-6057 > --- > > Key: PHOENIX-6076 > URL: https://issues.apache.org/jira/browse/PHOENIX-6076 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > > Refactor Phoenix Hive connectors in a way we decrease code duplication by > creating common source for multiple Hive connectors. > We should add Hive 2 support as well in this change. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6076) Refactor Phoenix Hive Connectors introduced by PHOENIX-6057
[ https://issues.apache.org/jira/browse/PHOENIX-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-6076: --- Comment: was deleted (was: This refactor should add Hive 2 support as well.) > Refactor Phoenix Hive Connectors introduced by PHOENIX-6057 > --- > > Key: PHOENIX-6076 > URL: https://issues.apache.org/jira/browse/PHOENIX-6076 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > > Refactor Phoenix Hive connectors in a way we decrease code duplication by > creating common source for multiple Hive connectors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6076) Refactor Phoenix Hive Connectors introduced by PHOENIX-6057
[ https://issues.apache.org/jira/browse/PHOENIX-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-6076: --- Description: Refactor Phoenix Hive connectors in a way we decrease code duplication by creating common source for multiple Hive connectors. > Refactor Phoenix Hive Connectors introduced by PHOENIX-6057 > --- > > Key: PHOENIX-6076 > URL: https://issues.apache.org/jira/browse/PHOENIX-6076 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > > Refactor Phoenix Hive connectors in a way we decrease code duplication by > creating common source for multiple Hive connectors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6076) Refactor Phoenix Hive Connectors introduced by PHOENIX-6057
Richard Antal created PHOENIX-6076: -- Summary: Refactor Phoenix Hive Connectors introduced by PHOENIX-6057 Key: PHOENIX-6076 URL: https://issues.apache.org/jira/browse/PHOENIX-6076 Project: Phoenix Issue Type: Task Reporter: Richard Antal Assignee: Richard Antal -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6054) Phoenix-spark connector doesn't work with phoenix master branch
[ https://issues.apache.org/jira/browse/PHOENIX-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal resolved PHOENIX-6054. Resolution: Duplicate I am handling phoenix-spark connector as part of the PHOENIX-6057 > Phoenix-spark connector doesn't work with phoenix master branch > --- > > Key: PHOENIX-6054 > URL: https://issues.apache.org/jira/browse/PHOENIX-6054 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > > Provide a working connector for phoenix 5.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6057) Create phoenix-connector for spark, kafka, pig, flume that works with Phoenix5
Richard Antal created PHOENIX-6057: -- Summary: Create phoenix-connector for spark, kafka, pig, flume that works with Phoenix5 Key: PHOENIX-6057 URL: https://issues.apache.org/jira/browse/PHOENIX-6057 Project: Phoenix Issue Type: Task Reporter: Richard Antal Assignee: Richard Antal Spark, kafka, pig, flume did not have to many differences in the presplit master and 4.x. We should be able to to create working connectors without duplicating the whole code. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6054) Phoenix-spark connector doesn't work with phoenix master branch
[ https://issues.apache.org/jira/browse/PHOENIX-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal reassigned PHOENIX-6054: -- Assignee: Richard Antal > Phoenix-spark connector doesn't work with phoenix master branch > --- > > Key: PHOENIX-6054 > URL: https://issues.apache.org/jira/browse/PHOENIX-6054 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > > Provide a working connector for phoenix 5.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6054) Phoenix-spark connector doesn't work with phoenix master branch
Richard Antal created PHOENIX-6054: -- Summary: Phoenix-spark connector doesn't work with phoenix master branch Key: PHOENIX-6054 URL: https://issues.apache.org/jira/browse/PHOENIX-6054 Project: Phoenix Issue Type: Task Reporter: Richard Antal Provide a working connector for phoenix 5.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5422) Use Java8 DateTime APIs instead of joda-time APIs
[ https://issues.apache.org/jira/browse/PHOENIX-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5422: --- Attachment: PHOENIX-5422.master.v4.patch > Use Java8 DateTime APIs instead of joda-time APIs > - > > Key: PHOENIX-5422 > URL: https://issues.apache.org/jira/browse/PHOENIX-5422 > Project: Phoenix > Issue Type: Task >Affects Versions: 4.8.0 >Reporter: Naveen Gangam >Assignee: Richard Antal >Priority: Minor > Attachments: PHOENIX-5422.master.v1.patch, > PHOENIX-5422.master.v2.patch, PHOENIX-5422.master.v3.patch, > PHOENIX-5422.master.v4.patch > > > currently, phoenix-hive.jar bundles an old version of joda-time library. > Java8 has new DateTime APIs are similar in to the joda-time APIs in features. > It would make sense to eliminate a dependency on external library that may or > may not be > a) Actively developed > b) not guaranteed to be backward compatible with older APIs and could involve > code changes as well. > Its is better to move using JDK8 APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5422) Use Java8 DateTime APIs instead of joda-time APIs
[ https://issues.apache.org/jira/browse/PHOENIX-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5422: --- Attachment: PHOENIX-5422.master.v3.patch > Use Java8 DateTime APIs instead of joda-time APIs > - > > Key: PHOENIX-5422 > URL: https://issues.apache.org/jira/browse/PHOENIX-5422 > Project: Phoenix > Issue Type: Task >Affects Versions: 4.8.0 >Reporter: Naveen Gangam >Assignee: Richard Antal >Priority: Minor > Attachments: PHOENIX-5422.master.v1.patch, > PHOENIX-5422.master.v2.patch, PHOENIX-5422.master.v3.patch > > > currently, phoenix-hive.jar bundles an old version of joda-time library. > Java8 has new DateTime APIs are similar in to the joda-time APIs in features. > It would make sense to eliminate a dependency on external library that may or > may not be > a) Actively developed > b) not guaranteed to be backward compatible with older APIs and could involve > code changes as well. > Its is better to move using JDK8 APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5422) Use Java8 DateTime APIs instead of joda-time APIs
[ https://issues.apache.org/jira/browse/PHOENIX-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5422: --- Attachment: PHOENIX-5422.master.v2.patch > Use Java8 DateTime APIs instead of joda-time APIs > - > > Key: PHOENIX-5422 > URL: https://issues.apache.org/jira/browse/PHOENIX-5422 > Project: Phoenix > Issue Type: Task >Affects Versions: 4.8.0 >Reporter: Naveen Gangam >Assignee: Richard Antal >Priority: Minor > Attachments: PHOENIX-5422.master.v1.patch, > PHOENIX-5422.master.v2.patch > > > currently, phoenix-hive.jar bundles an old version of joda-time library. > Java8 has new DateTime APIs are similar in to the joda-time APIs in features. > It would make sense to eliminate a dependency on external library that may or > may not be > a) Actively developed > b) not guaranteed to be backward compatible with older APIs and could involve > code changes as well. > Its is better to move using JDK8 APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6029) Merge InListIT tests to reduce runtime
[ https://issues.apache.org/jira/browse/PHOENIX-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal resolved PHOENIX-6029. Resolution: Duplicate > Merge InListIT tests to reduce runtime > -- > > Key: PHOENIX-6029 > URL: https://issues.apache.org/jira/browse/PHOENIX-6029 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-6029.master.v1.patch > > > InListIT is one of the slowest tests. > In my opinion we could reduce the time it takes to run it if we merge > multiple similar tests, because we create lot of connection, and do the same > initialisation in every test. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6029) Merge InListIT tests to reduce runtime
[ https://issues.apache.org/jira/browse/PHOENIX-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-6029: --- Attachment: PHOENIX-6029.master.v1.patch > Merge InListIT tests to reduce runtime > -- > > Key: PHOENIX-6029 > URL: https://issues.apache.org/jira/browse/PHOENIX-6029 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-6029.master.v1.patch > > > InListIT is one of the slowest tests. > In my opinion we could reduce the time it takes to run it if we merge > multiple similar tests, because we create lot of connection, and do the same > initialisation in every test. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6029) Merge InListIT tests to reduce runtime
[ https://issues.apache.org/jira/browse/PHOENIX-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-6029: --- Attachment: PHOENIX-6029.master.v1.patch > Merge InListIT tests to reduce runtime > -- > > Key: PHOENIX-6029 > URL: https://issues.apache.org/jira/browse/PHOENIX-6029 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Priority: Major > > InListIT is one of the slowest tests. > In my opinion we could reduce the time it takes to run it if we merge > multiple similar tests, because we create lot of connection, and do the same > initialisation in every test. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6029) Merge InListIT tests to reduce runtime
[ https://issues.apache.org/jira/browse/PHOENIX-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-6029: --- Attachment: (was: PHOENIX-6029.master.v1.patch) > Merge InListIT tests to reduce runtime > -- > > Key: PHOENIX-6029 > URL: https://issues.apache.org/jira/browse/PHOENIX-6029 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > > InListIT is one of the slowest tests. > In my opinion we could reduce the time it takes to run it if we merge > multiple similar tests, because we create lot of connection, and do the same > initialisation in every test. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6029) Merge InListIT tests to reduce runtime
[ https://issues.apache.org/jira/browse/PHOENIX-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal reassigned PHOENIX-6029: -- Assignee: Richard Antal > Merge InListIT tests to reduce runtime > -- > > Key: PHOENIX-6029 > URL: https://issues.apache.org/jira/browse/PHOENIX-6029 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > > InListIT is one of the slowest tests. > In my opinion we could reduce the time it takes to run it if we merge > multiple similar tests, because we create lot of connection, and do the same > initialisation in every test. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6029) Merge InListIT tests to reduce runtime
Richard Antal created PHOENIX-6029: -- Summary: Merge InListIT tests to reduce runtime Key: PHOENIX-6029 URL: https://issues.apache.org/jira/browse/PHOENIX-6029 Project: Phoenix Issue Type: Task Reporter: Richard Antal InListIT is one of the slowest tests. In my opinion we could reduce the time it takes to run it if we merge multiple similar tests, because we create lot of connection, and do the same initialisation in every test. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5786) Update phoenix-hive to support current hive versions
[ https://issues.apache.org/jira/browse/PHOENIX-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal reassigned PHOENIX-5786: -- Assignee: Richard Antal > Update phoenix-hive to support current hive versions > > > Key: PHOENIX-5786 > URL: https://issues.apache.org/jira/browse/PHOENIX-5786 > Project: Phoenix > Issue Type: Task > Components: connectors, hive-connector >Affects Versions: connectors-1.0.0 >Reporter: Istvan Toth >Assignee: Richard Antal >Priority: Major > > phoenix-hive is built against hive 1.2.1 > It doesn't even compile with 3.1 or 2.3 > Provide a working connector for 3.1 (phoenix 5.x), and preferably for 2.3 > (phoenix 4.x) as well -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6004) Metadata operations cannot filter on case-sensitive names
[
https://issues.apache.org/jira/browse/PHOENIX-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal reassigned PHOENIX-6004:
--
Assignee: Richard Antal
> Metadata operations cannot filter on case-sensitive names
> -
>
> Key: PHOENIX-6004
> URL: https://issues.apache.org/jira/browse/PHOENIX-6004
> Project: Phoenix
> Issue Type: Bug
> Components: core
>Affects Versions: 5.1.0, 4.16.0
>Reporter: Istvan Toth
>Assignee: Richard Antal
>Priority: Major
>
> The MetaData operations cannot filter on case-sensitive table, schema,
> column, or catalog names.
> Looks like at least QueryUtil.getTablesStmt() misses the logic to detect and
> handle the case-sensitive names
> expected behaviour:
> {code:java}
> meta.getTables(null, null, "\"CamelCase\"", null){code}
> should find the table "CamelCase", instead of "CAMELCASE"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5784) Phoenix-connectors doesn't work with phoenix master branch
[ https://issues.apache.org/jira/browse/PHOENIX-5784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal reassigned PHOENIX-5784: -- Assignee: Richard Antal > Phoenix-connectors doesn't work with phoenix master branch > -- > > Key: PHOENIX-5784 > URL: https://issues.apache.org/jira/browse/PHOENIX-5784 > Project: Phoenix > Issue Type: Bug > Components: connectors >Affects Versions: connectors-1.0.0 >Reporter: Istvan Toth >Assignee: Richard Antal >Priority: Major > > phoenix-connectors cannot even be built against the master branch: > mvn clean package -Dphoenix.version=5.1.0-SNAPSHOT -Dhadoop-two.version=3.0.0 > -Dhbase.version=2.2.1 -fn > fails for about half of the modules. > Most of these problems are simple API changes, have some kind of solution in > the pre-split master branch, the question is how to make them coexist in a > repo/branch. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5779) SplitSystemCatalogIT tests fail with Multiple Regions error
[ https://issues.apache.org/jira/browse/PHOENIX-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5779: --- Attachment: PHOENIX-5779.addendum.master.v4.patch > SplitSystemCatalogIT tests fail with Multiple Regions error > --- > > Key: PHOENIX-5779 > URL: https://issues.apache.org/jira/browse/PHOENIX-5779 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.1.0 >Reporter: Sandeep Guggilam >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5779-addendum.master.v1.patch, > PHOENIX-5779-addendum.master.v2.patch, PHOENIX-5779.addendum.master.v3.patch, > PHOENIX-5779.addendum.master.v4.patch, PHOENIX-5779.master.v1.patch > > > I see the SplitSystemCatalogIT tests failing on master branch complaining > with the error " Multiple regions on server" when it tries to split the > system catalog. > > Sample builds where it failed: > [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3560//testReport/] > [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3571//testReport/] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5937) Order by on nullable column sometimes filters rows
[ https://issues.apache.org/jira/browse/PHOENIX-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5937: --- Attachment: PHOENIX-5937.master.v4.patch > Order by on nullable column sometimes filters rows > -- > > Key: PHOENIX-5937 > URL: https://issues.apache.org/jira/browse/PHOENIX-5937 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 4.x, master >Reporter: Istvan Toth >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5937.master.v1.patch, > PHOENIX-5937.master.v2.patch, PHOENIX-5937.master.v3.patch, > PHOENIX-5937.master.v4.patch > > > When selecting using order by on a nullable column, the rows where the order > column is null are sometimes not returned. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5779) SplitSystemCatalogIT tests fail with Multiple Regions error
[ https://issues.apache.org/jira/browse/PHOENIX-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal reassigned PHOENIX-5779: -- Attachment: PHOENIX-5779.master.v1.patch Assignee: Richard Antal > SplitSystemCatalogIT tests fail with Multiple Regions error > --- > > Key: PHOENIX-5779 > URL: https://issues.apache.org/jira/browse/PHOENIX-5779 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.1.0 >Reporter: Sandeep Guggilam >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5779.master.v1.patch > > > I see the SplitSystemCatalogIT tests failing on master branch complaining > with the error " Multiple regions on server" when it tries to split the > system catalog. > > Sample builds where it failed: > [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3560//testReport/] > [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3571//testReport/] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5779) SplitSystemCatalogIT tests fail with Multiple Regions error
[ https://issues.apache.org/jira/browse/PHOENIX-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5779: --- Summary: SplitSystemCatalogIT tests fail with Multiple Regions error (was: SpliitSystemCatalogIT tests fail with Multiple Regions error) > SplitSystemCatalogIT tests fail with Multiple Regions error > --- > > Key: PHOENIX-5779 > URL: https://issues.apache.org/jira/browse/PHOENIX-5779 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.1.0 >Reporter: Sandeep Guggilam >Priority: Major > > I see the SplitSystemCatalogIT tests failing on master branch complaining > with the error " Multiple regions on server" when it tries to split the > system catalog. > > Sample builds where it failed: > [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3560//testReport/] > [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3571//testReport/] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5962) Stabilize builds
[ https://issues.apache.org/jira/browse/PHOENIX-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5962: --- Attachment: PHOENIX-5962.master.v6.patch > Stabilize builds > > > Key: PHOENIX-5962 > URL: https://issues.apache.org/jira/browse/PHOENIX-5962 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5962.4.x.v1.patch, PHOENIX-5962.master.v1.patch, > PHOENIX-5962.master.v2.patch, PHOENIX-5962.master.v3.patch, > PHOENIX-5962.master.v4.patch, PHOENIX-5962.master.v5.patch, > PHOENIX-5962.master.v6.patch > > > Last 2 build was aborted because Build timed out (after 360 minutes). > Search the possible cause of the problem and try to fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5962) Stabilize builds
[ https://issues.apache.org/jira/browse/PHOENIX-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5962: --- Attachment: PHOENIX-5962.4.x.v1.patch > Stabilize builds > > > Key: PHOENIX-5962 > URL: https://issues.apache.org/jira/browse/PHOENIX-5962 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5962.4.x.v1.patch, PHOENIX-5962.master.v1.patch, > PHOENIX-5962.master.v2.patch, PHOENIX-5962.master.v3.patch, > PHOENIX-5962.master.v4.patch, PHOENIX-5962.master.v5.patch > > > Last 2 build was aborted because Build timed out (after 360 minutes). > Search the possible cause of the problem and try to fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5962) Stabilize builds
[ https://issues.apache.org/jira/browse/PHOENIX-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5962: --- Attachment: PHOENIX-5962.master.v5.patch > Stabilize builds > > > Key: PHOENIX-5962 > URL: https://issues.apache.org/jira/browse/PHOENIX-5962 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5962.master.v1.patch, > PHOENIX-5962.master.v2.patch, PHOENIX-5962.master.v3.patch, > PHOENIX-5962.master.v4.patch, PHOENIX-5962.master.v5.patch > > > Last 2 build was aborted because Build timed out (after 360 minutes). > Search the possible cause of the problem and try to fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5962) Stabilize builds
[ https://issues.apache.org/jira/browse/PHOENIX-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5962: --- Attachment: PHOENIX-5962.master.v4.patch > Stabilize builds > > > Key: PHOENIX-5962 > URL: https://issues.apache.org/jira/browse/PHOENIX-5962 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5962.master.v1.patch, > PHOENIX-5962.master.v2.patch, PHOENIX-5962.master.v3.patch, > PHOENIX-5962.master.v4.patch > > > Last 2 build was aborted because Build timed out (after 360 minutes). > Search the possible cause of the problem and try to fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5962) Stabilize builds
[ https://issues.apache.org/jira/browse/PHOENIX-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5962: --- Attachment: PHOENIX-5962.master.v3.patch > Stabilize builds > > > Key: PHOENIX-5962 > URL: https://issues.apache.org/jira/browse/PHOENIX-5962 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5962.master.v1.patch, > PHOENIX-5962.master.v2.patch, PHOENIX-5962.master.v3.patch > > > Last 2 build was aborted because Build timed out (after 360 minutes). > Search the possible cause of the problem and try to fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5962) Stabilize builds
[ https://issues.apache.org/jira/browse/PHOENIX-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5962: --- Attachment: PHOENIX-5962.master.v2.patch > Stabilize builds > > > Key: PHOENIX-5962 > URL: https://issues.apache.org/jira/browse/PHOENIX-5962 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Priority: Major > Attachments: PHOENIX-5962.master.v1.patch, > PHOENIX-5962.master.v2.patch > > > Last 2 build was aborted because Build timed out (after 360 minutes). > Search the possible cause of the problem and try to fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5962) Stabilize builds
[ https://issues.apache.org/jira/browse/PHOENIX-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5962: --- Attachment: PHOENIX-5962.master.v1.patch > Stabilize builds > > > Key: PHOENIX-5962 > URL: https://issues.apache.org/jira/browse/PHOENIX-5962 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Priority: Major > > Last 2 build was aborted because Build timed out (after 360 minutes). > Search the possible cause of the problem and try to fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5962) Stabilize builds
[ https://issues.apache.org/jira/browse/PHOENIX-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5962: --- Attachment: (was: PHOENIX-5962.master.v1.patch) > Stabilize builds > > > Key: PHOENIX-5962 > URL: https://issues.apache.org/jira/browse/PHOENIX-5962 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Priority: Major > > Last 2 build was aborted because Build timed out (after 360 minutes). > Search the possible cause of the problem and try to fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5962) Stabilize builds
Richard Antal created PHOENIX-5962: -- Summary: Stabilize builds Key: PHOENIX-5962 URL: https://issues.apache.org/jira/browse/PHOENIX-5962 Project: Phoenix Issue Type: Task Reporter: Richard Antal Last 2 build was aborted because Build timed out (after 360 minutes). Search the possible cause of the problem and try to fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5937) Order by on nullable column sometimes filters rows
[ https://issues.apache.org/jira/browse/PHOENIX-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5937: --- Attachment: PHOENIX-5937.master.v3.patch > Order by on nullable column sometimes filters rows > -- > > Key: PHOENIX-5937 > URL: https://issues.apache.org/jira/browse/PHOENIX-5937 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 4.x, master >Reporter: Istvan Toth >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5937.master.v1.patch, > PHOENIX-5937.master.v2.patch, PHOENIX-5937.master.v3.patch > > > When selecting using order by on a nullable column, the rows where the order > column is null are sometimes not returned. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5937) Order by on nullable column sometimes filters rows
[ https://issues.apache.org/jira/browse/PHOENIX-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5937: --- Attachment: PHOENIX-5937.master.v2.patch > Order by on nullable column sometimes filters rows > -- > > Key: PHOENIX-5937 > URL: https://issues.apache.org/jira/browse/PHOENIX-5937 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 4.x, master >Reporter: Istvan Toth >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5937.master.v1.patch, > PHOENIX-5937.master.v2.patch > > > When selecting using order by on a nullable column, the rows where the order > column is null are sometimes not returned. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5937) Order by on nullable column sometimes filters rows
[ https://issues.apache.org/jira/browse/PHOENIX-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal reassigned PHOENIX-5937: -- Assignee: Richard Antal > Order by on nullable column sometimes filters rows > -- > > Key: PHOENIX-5937 > URL: https://issues.apache.org/jira/browse/PHOENIX-5937 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 4.x, master >Reporter: Istvan Toth >Assignee: Richard Antal >Priority: Major > > When selecting using order by on a nullable column, the rows where the order > column is null are sometimes not returned. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5764) Update website to reflect the new 4.x branch
[ https://issues.apache.org/jira/browse/PHOENIX-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5764: --- Attachment: PHOENIX-5764.docs.v1.patch > Update website to reflect the new 4.x branch > > > Key: PHOENIX-5764 > URL: https://issues.apache.org/jira/browse/PHOENIX-5764 > Project: Phoenix > Issue Type: Task >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Attachments: PHOENIX-5764.docs.v1.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5764) Update website to reflect the new 4.x branch
[ https://issues.apache.org/jira/browse/PHOENIX-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal reassigned PHOENIX-5764: -- Assignee: Richard Antal (was: Istvan Toth) > Update website to reflect the new 4.x branch > > > Key: PHOENIX-5764 > URL: https://issues.apache.org/jira/browse/PHOENIX-5764 > Project: Phoenix > Issue Type: Task >Reporter: Istvan Toth >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5764.docs.v1.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5066) The TimeZone is incorrectly used during writing or reading data
[
https://issues.apache.org/jira/browse/PHOENIX-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated PHOENIX-5066:
---
Attachment: PHOENIX-5066.master.v6.patch
> The TimeZone is incorrectly used during writing or reading data
> ---
>
> Key: PHOENIX-5066
> URL: https://issues.apache.org/jira/browse/PHOENIX-5066
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 5.0.0, 4.14.1
>Reporter: Jaanai Zhang
>Assignee: Richard Antal
>Priority: Critical
> Fix For: 4.15.1, 5.1.1, 4.16.0
>
> Attachments: DateTest.java, PHOENIX-5066.4x.v1.patch,
> PHOENIX-5066.4x.v2.patch, PHOENIX-5066.4x.v3.patch,
> PHOENIX-5066.master.v1.patch, PHOENIX-5066.master.v2.patch,
> PHOENIX-5066.master.v3.patch, PHOENIX-5066.master.v4.patch,
> PHOENIX-5066.master.v5.patch, PHOENIX-5066.master.v6.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We have two methods to write data when uses JDBC API.
> #1. Uses _the exceuteUpdate_ method to execute a string that is an upsert SQL.
> #2. Uses the _prepareStatement_ method to set some objects and execute.
> The _string_ data needs to convert to a new object by the schema information
> of tables. we'll use some date formatters to convert string data to object
> for Date/Time/Timestamp types when writes data and the formatters are used
> when reads data as well.
>
> *Uses default timezone test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 2 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 3 | 2018-12-10 | 15:45:07 | 2018-12-10 15:45:07.66
> {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 2 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 3 | 2018-12-10 07:45:07.660 | 2018-12-10 07:45:07.660 | 2018-12-10
> 07:45:07.660
> {code}
> *Uses GMT+8 test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:40:47 | 2018-12-10 23:40:47.0
> 2 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.0
> 3 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.106 {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 23:40:47.000 | 2018-12-10 23:40:47.000 | 2018-12-10
> 23:40:47.000
> 2 | 2018-12-10 15:40:47.000 | 2018-12-10 15:40:47.000 | 2018-12-10
> 15:40:47.000
> 3 | 2018-12-10 15:40:47.106 | 2018-12-10 15:40:47.106 | 2018-12-10
> 15:40:47.106
> {code}
>
> _We_ have a historical problem, we'll parse the string to
> Date/Time/Timestamp objects with timezone in #1, which means the actual data
> is going to be changed when stored in HBase table。
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5831) Make Phoenix queryserver scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5831: --- Attachment: PHOENIX-5831.master.v6.patch > Make Phoenix queryserver scripts work with Python 3 > --- > > Key: PHOENIX-5831 > URL: https://issues.apache.org/jira/browse/PHOENIX-5831 > Project: Phoenix > Issue Type: Bug > Components: queryserver >Affects Versions: queryserver-1.0.0 >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Critical > Fix For: queryserver-1.0.0 > > Attachments: PHOENIX-5831.master.v1.patch, > PHOENIX-5831.master.v2.patch, PHOENIX-5831.master.v3.patch, > PHOENIX-5831.master.v4.patch, PHOENIX-5831.master.v5.patch, > PHOENIX-5831.master.v6.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix queryserver scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5656) Make Phoenix scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5656: --- Attachment: PHOENIX-5656.master.v5.patch > Make Phoenix scripts work with Python 3 > --- > > Key: PHOENIX-5656 > URL: https://issues.apache.org/jira/browse/PHOENIX-5656 > Project: Phoenix > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Richard Antal >Priority: Critical > Fix For: 5.1.0, 4.16.0 > > Attachments: 5656-4.x-HBase-1.5-untested.txt, > 5656-4.x-HBase-1.5-v3.txt, 5656-4.x-HBase-1.5-v4.txt, > PHOENIX-5656.4.x.v1.patch, PHOENIX-5656.4.x.v2.patch, > PHOENIX-5656.4.x.v3.patch, PHOENIX-5656.4.x.v4.patch, > PHOENIX-5656.4.x.v5.patch, PHOENIX-5656.master.v1.patch, > PHOENIX-5656.master.v2.patch, PHOENIX-5656.master.v3.patch, > PHOENIX-5656.master.v4.patch, PHOENIX-5656.master.v5.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5656) Make Phoenix scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5656: --- Attachment: PHOENIX-5656.4.x.v5.patch > Make Phoenix scripts work with Python 3 > --- > > Key: PHOENIX-5656 > URL: https://issues.apache.org/jira/browse/PHOENIX-5656 > Project: Phoenix > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Richard Antal >Priority: Critical > Fix For: 5.1.0, 4.16.0 > > Attachments: 5656-4.x-HBase-1.5-untested.txt, > 5656-4.x-HBase-1.5-v3.txt, 5656-4.x-HBase-1.5-v4.txt, > PHOENIX-5656.4.x.v1.patch, PHOENIX-5656.4.x.v2.patch, > PHOENIX-5656.4.x.v3.patch, PHOENIX-5656.4.x.v4.patch, > PHOENIX-5656.4.x.v5.patch, PHOENIX-5656.master.v1.patch, > PHOENIX-5656.master.v2.patch, PHOENIX-5656.master.v3.patch, > PHOENIX-5656.master.v4.patch, PHOENIX-5656.master.v5.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5831) Make Phoenix queryserver scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5831: --- Attachment: PHOENIX-5831.master.v5.patch > Make Phoenix queryserver scripts work with Python 3 > --- > > Key: PHOENIX-5831 > URL: https://issues.apache.org/jira/browse/PHOENIX-5831 > Project: Phoenix > Issue Type: Bug > Components: queryserver >Affects Versions: queryserver-1.0.0 >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Critical > Fix For: queryserver-1.0.0 > > Attachments: PHOENIX-5831.master.v1.patch, > PHOENIX-5831.master.v2.patch, PHOENIX-5831.master.v3.patch, > PHOENIX-5831.master.v4.patch, PHOENIX-5831.master.v5.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix queryserver scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5656) Make Phoenix scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5656: --- Attachment: PHOENIX-5656.4.x.v4.patch > Make Phoenix scripts work with Python 3 > --- > > Key: PHOENIX-5656 > URL: https://issues.apache.org/jira/browse/PHOENIX-5656 > Project: Phoenix > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Richard Antal >Priority: Critical > Fix For: 5.1.0, 4.16.0 > > Attachments: 5656-4.x-HBase-1.5-untested.txt, > 5656-4.x-HBase-1.5-v3.txt, 5656-4.x-HBase-1.5-v4.txt, > PHOENIX-5656.4.x.v1.patch, PHOENIX-5656.4.x.v2.patch, > PHOENIX-5656.4.x.v3.patch, PHOENIX-5656.4.x.v4.patch, > PHOENIX-5656.master.v1.patch, PHOENIX-5656.master.v2.patch, > PHOENIX-5656.master.v3.patch, PHOENIX-5656.master.v4.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5656) Make Phoenix scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5656: --- Attachment: PHOENIX-5656.master.v4.patch > Make Phoenix scripts work with Python 3 > --- > > Key: PHOENIX-5656 > URL: https://issues.apache.org/jira/browse/PHOENIX-5656 > Project: Phoenix > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Richard Antal >Priority: Critical > Fix For: 5.1.0, 4.16.0 > > Attachments: 5656-4.x-HBase-1.5-untested.txt, > 5656-4.x-HBase-1.5-v3.txt, 5656-4.x-HBase-1.5-v4.txt, > PHOENIX-5656.4.x.v1.patch, PHOENIX-5656.4.x.v2.patch, > PHOENIX-5656.4.x.v3.patch, PHOENIX-5656.master.v1.patch, > PHOENIX-5656.master.v2.patch, PHOENIX-5656.master.v3.patch, > PHOENIX-5656.master.v4.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5831) Make Phoenix queryserver scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5831: --- Attachment: PHOENIX-5831.master.v4.patch > Make Phoenix queryserver scripts work with Python 3 > --- > > Key: PHOENIX-5831 > URL: https://issues.apache.org/jira/browse/PHOENIX-5831 > Project: Phoenix > Issue Type: Bug > Components: queryserver >Affects Versions: queryserver-1.0.0 >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Critical > Fix For: queryserver-1.0.0 > > Attachments: PHOENIX-5831.master.v1.patch, > PHOENIX-5831.master.v2.patch, PHOENIX-5831.master.v3.patch, > PHOENIX-5831.master.v4.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix queryserver scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5656) Make Phoenix scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5656: --- Attachment: (was: PHOENIX-5831.master.v4.patch) > Make Phoenix scripts work with Python 3 > --- > > Key: PHOENIX-5656 > URL: https://issues.apache.org/jira/browse/PHOENIX-5656 > Project: Phoenix > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Richard Antal >Priority: Critical > Fix For: 5.1.0, 4.16.0 > > Attachments: 5656-4.x-HBase-1.5-untested.txt, > 5656-4.x-HBase-1.5-v3.txt, 5656-4.x-HBase-1.5-v4.txt, > PHOENIX-5656.4.x.v1.patch, PHOENIX-5656.4.x.v2.patch, > PHOENIX-5656.4.x.v3.patch, PHOENIX-5656.master.v1.patch, > PHOENIX-5656.master.v2.patch, PHOENIX-5656.master.v3.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5656) Make Phoenix scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5656: --- Attachment: PHOENIX-5831.master.v4.patch > Make Phoenix scripts work with Python 3 > --- > > Key: PHOENIX-5656 > URL: https://issues.apache.org/jira/browse/PHOENIX-5656 > Project: Phoenix > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Richard Antal >Priority: Critical > Fix For: 5.1.0, 4.16.0 > > Attachments: 5656-4.x-HBase-1.5-untested.txt, > 5656-4.x-HBase-1.5-v3.txt, 5656-4.x-HBase-1.5-v4.txt, > PHOENIX-5656.4.x.v1.patch, PHOENIX-5656.4.x.v2.patch, > PHOENIX-5656.4.x.v3.patch, PHOENIX-5656.master.v1.patch, > PHOENIX-5656.master.v2.patch, PHOENIX-5656.master.v3.patch, > PHOENIX-5831.master.v4.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5656) Make Phoenix scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5656: --- Attachment: PHOENIX-5656.master.v3.patch > Make Phoenix scripts work with Python 3 > --- > > Key: PHOENIX-5656 > URL: https://issues.apache.org/jira/browse/PHOENIX-5656 > Project: Phoenix > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Richard Antal >Priority: Critical > Fix For: 5.1.0, 4.16.0 > > Attachments: 5656-4.x-HBase-1.5-untested.txt, > 5656-4.x-HBase-1.5-v3.txt, 5656-4.x-HBase-1.5-v4.txt, > PHOENIX-5656.4.x.v1.patch, PHOENIX-5656.4.x.v2.patch, > PHOENIX-5656.4.x.v3.patch, PHOENIX-5656.master.v1.patch, > PHOENIX-5656.master.v2.patch, PHOENIX-5656.master.v3.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5656) Make Phoenix scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5656: --- Attachment: PHOENIX-5656.4.x.v3.patch > Make Phoenix scripts work with Python 3 > --- > > Key: PHOENIX-5656 > URL: https://issues.apache.org/jira/browse/PHOENIX-5656 > Project: Phoenix > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Richard Antal >Priority: Critical > Fix For: 5.1.0, 4.16.0 > > Attachments: 5656-4.x-HBase-1.5-untested.txt, > 5656-4.x-HBase-1.5-v3.txt, 5656-4.x-HBase-1.5-v4.txt, > PHOENIX-5656.4.x.v1.patch, PHOENIX-5656.4.x.v2.patch, > PHOENIX-5656.4.x.v3.patch, PHOENIX-5656.master.v1.patch, > PHOENIX-5656.master.v2.patch, PHOENIX-5656.master.v3.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5831) Make Phoenix queryserver scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5831: --- Attachment: PHOENIX-5831.master.v3.patch > Make Phoenix queryserver scripts work with Python 3 > --- > > Key: PHOENIX-5831 > URL: https://issues.apache.org/jira/browse/PHOENIX-5831 > Project: Phoenix > Issue Type: Bug > Components: queryserver >Affects Versions: queryserver-1.0.0 >Reporter: Richard Antal >Priority: Critical > Fix For: queryserver-1.0.0 > > Attachments: PHOENIX-5831.master.v1.patch, > PHOENIX-5831.master.v2.patch, PHOENIX-5831.master.v3.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix queryserver scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5831) Make Phoenix queryserver scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5831: --- Attachment: PHOENIX-5831.master.v2.patch > Make Phoenix queryserver scripts work with Python 3 > --- > > Key: PHOENIX-5831 > URL: https://issues.apache.org/jira/browse/PHOENIX-5831 > Project: Phoenix > Issue Type: Bug > Components: queryserver >Affects Versions: queryserver-1.0.0 >Reporter: Richard Antal >Priority: Critical > Fix For: queryserver-1.0.0 > > Attachments: PHOENIX-5831.master.v1.patch, > PHOENIX-5831.master.v2.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix queryserver scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5656) Make Phoenix scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5656: --- Attachment: PHOENIX-5656.master.v2.patch PHOENIX-5656.4.x.v2.patch > Make Phoenix scripts work with Python 3 > --- > > Key: PHOENIX-5656 > URL: https://issues.apache.org/jira/browse/PHOENIX-5656 > Project: Phoenix > Issue Type: Bug >Reporter: Lars Hofhansl >Priority: Critical > Fix For: 5.1.0, 4.16.0 > > Attachments: 5656-4.x-HBase-1.5-untested.txt, > 5656-4.x-HBase-1.5-v3.txt, 5656-4.x-HBase-1.5-v4.txt, > PHOENIX-5656.4.x.v1.patch, PHOENIX-5656.4.x.v2.patch, > PHOENIX-5656.master.v1.patch, PHOENIX-5656.master.v2.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5066) The TimeZone is incorrectly used during writing or reading data
[
https://issues.apache.org/jira/browse/PHOENIX-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated PHOENIX-5066:
---
Attachment: PHOENIX-5066.master.v4.patch
> The TimeZone is incorrectly used during writing or reading data
> ---
>
> Key: PHOENIX-5066
> URL: https://issues.apache.org/jira/browse/PHOENIX-5066
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 5.0.0, 4.14.1
>Reporter: Jaanai Zhang
>Assignee: Richard Antal
>Priority: Critical
> Fix For: 4.15.1, 5.1.1
>
> Attachments: DateTest.java, PHOENIX-5066.4x.v1.patch,
> PHOENIX-5066.4x.v2.patch, PHOENIX-5066.4x.v3.patch,
> PHOENIX-5066.master.v1.patch, PHOENIX-5066.master.v2.patch,
> PHOENIX-5066.master.v3.patch, PHOENIX-5066.master.v4.patch
>
>
> We have two methods to write data when uses JDBC API.
> #1. Uses _the exceuteUpdate_ method to execute a string that is an upsert SQL.
> #2. Uses the _prepareStatement_ method to set some objects and execute.
> The _string_ data needs to convert to a new object by the schema information
> of tables. we'll use some date formatters to convert string data to object
> for Date/Time/Timestamp types when writes data and the formatters are used
> when reads data as well.
>
> *Uses default timezone test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 2 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 3 | 2018-12-10 | 15:45:07 | 2018-12-10 15:45:07.66
> {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 2 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 3 | 2018-12-10 07:45:07.660 | 2018-12-10 07:45:07.660 | 2018-12-10
> 07:45:07.660
> {code}
> *Uses GMT+8 test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:40:47 | 2018-12-10 23:40:47.0
> 2 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.0
> 3 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.106 {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 23:40:47.000 | 2018-12-10 23:40:47.000 | 2018-12-10
> 23:40:47.000
> 2 | 2018-12-10 15:40:47.000 | 2018-12-10 15:40:47.000 | 2018-12-10
> 15:40:47.000
> 3 | 2018-12-10 15:40:47.106 | 2018-12-10 15:40:47.106 | 2018-12-10
> 15:40:47.106
> {code}
>
> _We_ have a historical problem, we'll parse the string to
> Date/Time/Timestamp objects with timezone in #1, which means the actual data
> is going to be changed when stored in HBase table。
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5066) The TimeZone is incorrectly used during writing or reading data
[
https://issues.apache.org/jira/browse/PHOENIX-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated PHOENIX-5066:
---
Attachment: PHOENIX-5066.master.v3.patch
> The TimeZone is incorrectly used during writing or reading data
> ---
>
> Key: PHOENIX-5066
> URL: https://issues.apache.org/jira/browse/PHOENIX-5066
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 5.0.0, 4.14.1
>Reporter: Jaanai Zhang
>Assignee: Richard Antal
>Priority: Critical
> Fix For: 4.15.1, 5.1.1
>
> Attachments: DateTest.java, PHOENIX-5066.4x.v1.patch,
> PHOENIX-5066.4x.v2.patch, PHOENIX-5066.4x.v3.patch,
> PHOENIX-5066.master.v1.patch, PHOENIX-5066.master.v2.patch,
> PHOENIX-5066.master.v3.patch
>
>
> We have two methods to write data when uses JDBC API.
> #1. Uses _the exceuteUpdate_ method to execute a string that is an upsert SQL.
> #2. Uses the _prepareStatement_ method to set some objects and execute.
> The _string_ data needs to convert to a new object by the schema information
> of tables. we'll use some date formatters to convert string data to object
> for Date/Time/Timestamp types when writes data and the formatters are used
> when reads data as well.
>
> *Uses default timezone test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 2 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 3 | 2018-12-10 | 15:45:07 | 2018-12-10 15:45:07.66
> {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 2 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 3 | 2018-12-10 07:45:07.660 | 2018-12-10 07:45:07.660 | 2018-12-10
> 07:45:07.660
> {code}
> *Uses GMT+8 test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:40:47 | 2018-12-10 23:40:47.0
> 2 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.0
> 3 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.106 {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 23:40:47.000 | 2018-12-10 23:40:47.000 | 2018-12-10
> 23:40:47.000
> 2 | 2018-12-10 15:40:47.000 | 2018-12-10 15:40:47.000 | 2018-12-10
> 15:40:47.000
> 3 | 2018-12-10 15:40:47.106 | 2018-12-10 15:40:47.106 | 2018-12-10
> 15:40:47.106
> {code}
>
> _We_ have a historical problem, we'll parse the string to
> Date/Time/Timestamp objects with timezone in #1, which means the actual data
> is going to be changed when stored in HBase table。
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5066) The TimeZone is incorrectly used during writing or reading data
[
https://issues.apache.org/jira/browse/PHOENIX-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated PHOENIX-5066:
---
Attachment: PHOENIX-5066.4x.v3.patch
> The TimeZone is incorrectly used during writing or reading data
> ---
>
> Key: PHOENIX-5066
> URL: https://issues.apache.org/jira/browse/PHOENIX-5066
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 5.0.0, 4.14.1
>Reporter: Jaanai Zhang
>Assignee: Richard Antal
>Priority: Critical
> Fix For: 4.15.1, 5.1.1
>
> Attachments: DateTest.java, PHOENIX-5066.4x.v1.patch,
> PHOENIX-5066.4x.v2.patch, PHOENIX-5066.4x.v3.patch,
> PHOENIX-5066.master.v1.patch, PHOENIX-5066.master.v2.patch
>
>
> We have two methods to write data when uses JDBC API.
> #1. Uses _the exceuteUpdate_ method to execute a string that is an upsert SQL.
> #2. Uses the _prepareStatement_ method to set some objects and execute.
> The _string_ data needs to convert to a new object by the schema information
> of tables. we'll use some date formatters to convert string data to object
> for Date/Time/Timestamp types when writes data and the formatters are used
> when reads data as well.
>
> *Uses default timezone test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 2 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 3 | 2018-12-10 | 15:45:07 | 2018-12-10 15:45:07.66
> {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 2 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 3 | 2018-12-10 07:45:07.660 | 2018-12-10 07:45:07.660 | 2018-12-10
> 07:45:07.660
> {code}
> *Uses GMT+8 test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:40:47 | 2018-12-10 23:40:47.0
> 2 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.0
> 3 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.106 {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 23:40:47.000 | 2018-12-10 23:40:47.000 | 2018-12-10
> 23:40:47.000
> 2 | 2018-12-10 15:40:47.000 | 2018-12-10 15:40:47.000 | 2018-12-10
> 15:40:47.000
> 3 | 2018-12-10 15:40:47.106 | 2018-12-10 15:40:47.106 | 2018-12-10
> 15:40:47.106
> {code}
>
> _We_ have a historical problem, we'll parse the string to
> Date/Time/Timestamp objects with timezone in #1, which means the actual data
> is going to be changed when stored in HBase table。
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5066) The TimeZone is incorrectly used during writing or reading data
[
https://issues.apache.org/jira/browse/PHOENIX-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated PHOENIX-5066:
---
Attachment: PHOENIX-5066.4x.v2.patch
> The TimeZone is incorrectly used during writing or reading data
> ---
>
> Key: PHOENIX-5066
> URL: https://issues.apache.org/jira/browse/PHOENIX-5066
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 5.0.0, 4.14.1
>Reporter: Jaanai Zhang
>Assignee: Richard Antal
>Priority: Critical
> Fix For: 4.15.1, 5.1.1
>
> Attachments: DateTest.java, PHOENIX-5066.4x.v1.patch,
> PHOENIX-5066.4x.v2.patch, PHOENIX-5066.master.v1.patch,
> PHOENIX-5066.master.v2.patch
>
>
> We have two methods to write data when uses JDBC API.
> #1. Uses _the exceuteUpdate_ method to execute a string that is an upsert SQL.
> #2. Uses the _prepareStatement_ method to set some objects and execute.
> The _string_ data needs to convert to a new object by the schema information
> of tables. we'll use some date formatters to convert string data to object
> for Date/Time/Timestamp types when writes data and the formatters are used
> when reads data as well.
>
> *Uses default timezone test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 2 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 3 | 2018-12-10 | 15:45:07 | 2018-12-10 15:45:07.66
> {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 2 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 3 | 2018-12-10 07:45:07.660 | 2018-12-10 07:45:07.660 | 2018-12-10
> 07:45:07.660
> {code}
> *Uses GMT+8 test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:40:47 | 2018-12-10 23:40:47.0
> 2 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.0
> 3 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.106 {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 23:40:47.000 | 2018-12-10 23:40:47.000 | 2018-12-10
> 23:40:47.000
> 2 | 2018-12-10 15:40:47.000 | 2018-12-10 15:40:47.000 | 2018-12-10
> 15:40:47.000
> 3 | 2018-12-10 15:40:47.106 | 2018-12-10 15:40:47.106 | 2018-12-10
> 15:40:47.106
> {code}
>
> _We_ have a historical problem, we'll parse the string to
> Date/Time/Timestamp objects with timezone in #1, which means the actual data
> is going to be changed when stored in HBase table。
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5066) The TimeZone is incorrectly used during writing or reading data
[
https://issues.apache.org/jira/browse/PHOENIX-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated PHOENIX-5066:
---
Attachment: PHOENIX-5066.master.v2.patch
> The TimeZone is incorrectly used during writing or reading data
> ---
>
> Key: PHOENIX-5066
> URL: https://issues.apache.org/jira/browse/PHOENIX-5066
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 5.0.0, 4.14.1
>Reporter: Jaanai Zhang
>Assignee: Richard Antal
>Priority: Critical
> Fix For: 4.15.1, 5.1.1
>
> Attachments: DateTest.java, PHOENIX-5066.4x.v1.patch,
> PHOENIX-5066.master.v1.patch, PHOENIX-5066.master.v2.patch
>
>
> We have two methods to write data when uses JDBC API.
> #1. Uses _the exceuteUpdate_ method to execute a string that is an upsert SQL.
> #2. Uses the _prepareStatement_ method to set some objects and execute.
> The _string_ data needs to convert to a new object by the schema information
> of tables. we'll use some date formatters to convert string data to object
> for Date/Time/Timestamp types when writes data and the formatters are used
> when reads data as well.
>
> *Uses default timezone test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 2 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 3 | 2018-12-10 | 15:45:07 | 2018-12-10 15:45:07.66
> {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 2 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 3 | 2018-12-10 07:45:07.660 | 2018-12-10 07:45:07.660 | 2018-12-10
> 07:45:07.660
> {code}
> *Uses GMT+8 test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:40:47 | 2018-12-10 23:40:47.0
> 2 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.0
> 3 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.106 {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 23:40:47.000 | 2018-12-10 23:40:47.000 | 2018-12-10
> 23:40:47.000
> 2 | 2018-12-10 15:40:47.000 | 2018-12-10 15:40:47.000 | 2018-12-10
> 15:40:47.000
> 3 | 2018-12-10 15:40:47.106 | 2018-12-10 15:40:47.106 | 2018-12-10
> 15:40:47.106
> {code}
>
> _We_ have a historical problem, we'll parse the string to
> Date/Time/Timestamp objects with timezone in #1, which means the actual data
> is going to be changed when stored in HBase table。
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5066) The TimeZone is incorrectly used during writing or reading data
[
https://issues.apache.org/jira/browse/PHOENIX-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated PHOENIX-5066:
---
Attachment: PHOENIX-5066.4x.v1.patch
> The TimeZone is incorrectly used during writing or reading data
> ---
>
> Key: PHOENIX-5066
> URL: https://issues.apache.org/jira/browse/PHOENIX-5066
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 5.0.0, 4.14.1
>Reporter: Jaanai Zhang
>Assignee: Richard Antal
>Priority: Critical
> Fix For: 4.15.1, 5.1.1
>
> Attachments: DateTest.java, PHOENIX-5066.4x.v1.patch,
> PHOENIX-5066.master.v1.patch
>
>
> We have two methods to write data when uses JDBC API.
> #1. Uses _the exceuteUpdate_ method to execute a string that is an upsert SQL.
> #2. Uses the _prepareStatement_ method to set some objects and execute.
> The _string_ data needs to convert to a new object by the schema information
> of tables. we'll use some date formatters to convert string data to object
> for Date/Time/Timestamp types when writes data and the formatters are used
> when reads data as well.
>
> *Uses default timezone test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 2 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 3 | 2018-12-10 | 15:45:07 | 2018-12-10 15:45:07.66
> {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 2 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 3 | 2018-12-10 07:45:07.660 | 2018-12-10 07:45:07.660 | 2018-12-10
> 07:45:07.660
> {code}
> *Uses GMT+8 test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:40:47 | 2018-12-10 23:40:47.0
> 2 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.0
> 3 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.106 {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 23:40:47.000 | 2018-12-10 23:40:47.000 | 2018-12-10
> 23:40:47.000
> 2 | 2018-12-10 15:40:47.000 | 2018-12-10 15:40:47.000 | 2018-12-10
> 15:40:47.000
> 3 | 2018-12-10 15:40:47.106 | 2018-12-10 15:40:47.106 | 2018-12-10
> 15:40:47.106
> {code}
>
> _We_ have a historical problem, we'll parse the string to
> Date/Time/Timestamp objects with timezone in #1, which means the actual data
> is going to be changed when stored in HBase table。
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5066) The TimeZone is incorrectly used during writing or reading data
[
https://issues.apache.org/jira/browse/PHOENIX-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal reassigned PHOENIX-5066:
--
Attachment: PHOENIX-5066.master.v1.patch
Assignee: Richard Antal (was: Jaanai Zhang)
> The TimeZone is incorrectly used during writing or reading data
> ---
>
> Key: PHOENIX-5066
> URL: https://issues.apache.org/jira/browse/PHOENIX-5066
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.14.1, 5.0.0
>Reporter: Jaanai Zhang
>Assignee: Richard Antal
>Priority: Critical
> Fix For: 4.15.1, 5.1.1
>
> Attachments: DateTest.java, PHOENIX-5066.master.v1.patch
>
>
> We have two methods to write data when uses JDBC API.
> #1. Uses _the exceuteUpdate_ method to execute a string that is an upsert SQL.
> #2. Uses the _prepareStatement_ method to set some objects and execute.
> The _string_ data needs to convert to a new object by the schema information
> of tables. we'll use some date formatters to convert string data to object
> for Date/Time/Timestamp types when writes data and the formatters are used
> when reads data as well.
>
> *Uses default timezone test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 2 | 2018-12-10 | 23:45:07 | 2018-12-10 23:45:07.0
> 3 | 2018-12-10 | 15:45:07 | 2018-12-10 15:45:07.66
> {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 2 | 2018-12-10 15:45:07.000 | 2018-12-10 15:45:07.000 | 2018-12-10
> 15:45:07.000
> 3 | 2018-12-10 07:45:07.660 | 2018-12-10 07:45:07.660 | 2018-12-10
> 07:45:07.660
> {code}
> *Uses GMT+8 test*
> Writing 3 records by the different ways.
> {code:java}
> UPSERT INTO date_test VALUES (1,'2018-12-10 15:40:47','2018-12-10
> 15:40:47','2018-12-10 15:40:47')
> UPSERT INTO date_test VALUES (2,to_date('2018-12-10
> 15:40:47'),to_time('2018-12-10 15:40:47'),to_timestamp('2018-12-10 15:40:47'))
> stmt.setInt(1, 3);stmt.setDate(2, date);stmt.setTime(3,
> time);stmt.setTimestamp(4, ts);
> {code}
> Reading the table by the getObject(getDate/getTime/getTimestamp) methods.
> {code:java}
> 1 | 2018-12-10 | 23:40:47 | 2018-12-10 23:40:47.0
> 2 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.0
> 3 | 2018-12-10 | 15:40:47 | 2018-12-10 15:40:47.106 {code}
> Reading the table by the getString methods
> {code:java}
> 1 | 2018-12-10 23:40:47.000 | 2018-12-10 23:40:47.000 | 2018-12-10
> 23:40:47.000
> 2 | 2018-12-10 15:40:47.000 | 2018-12-10 15:40:47.000 | 2018-12-10
> 15:40:47.000
> 3 | 2018-12-10 15:40:47.106 | 2018-12-10 15:40:47.106 | 2018-12-10
> 15:40:47.106
> {code}
>
> _We_ have a historical problem, we'll parse the string to
> Date/Time/Timestamp objects with timezone in #1, which means the actual data
> is going to be changed when stored in HBase table。
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5789) try to standardize on a JSON library
[ https://issues.apache.org/jira/browse/PHOENIX-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5789: --- Attachment: PHOENIX-5789.master.addendum.v3.patch > try to standardize on a JSON library > > > Key: PHOENIX-5789 > URL: https://issues.apache.org/jira/browse/PHOENIX-5789 > Project: Phoenix > Issue Type: Improvement > Components: core >Reporter: Istvan Toth >Assignee: Richard Antal >Priority: Minor > Attachments: PHOENIX-5789.4.x.v1.patch, PHOENIX-5789.4.x.v3.patch, > PHOENIX-5789.4.x.v4.patch, PHOENIX-5789.4.x.v5.patch, > PHOENIX-5789.4.x.v6.patch, PHOENIX-5789.4.x.v7.patch, > PHOENIX-5789.master.addendum.patch, PHOENIX-5789.master.addendum.v2.patch, > PHOENIX-5789.master.addendum.v3.patch, PHOENIX-5789.master.v1.patch, > PHOENIX-5789.master.v2.patch, PHOENIX-5789.master.v3.patch, > PHOENIX-5789.master.v4.patch > > > Phoenix uses at least the following JSON libraries: > * gson > * jackson > * jettison > Of these, only the jackson usage is performance critical, as it is used > during bulk loading. > Try to standardize on a single one to reduce dependency hell. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5789) try to standardize on a JSON library
[ https://issues.apache.org/jira/browse/PHOENIX-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5789: --- Attachment: PHOENIX-5789.master.addendum.v2.patch > try to standardize on a JSON library > > > Key: PHOENIX-5789 > URL: https://issues.apache.org/jira/browse/PHOENIX-5789 > Project: Phoenix > Issue Type: Improvement > Components: core >Reporter: Istvan Toth >Assignee: Richard Antal >Priority: Minor > Attachments: PHOENIX-5789.4.x.v1.patch, PHOENIX-5789.4.x.v3.patch, > PHOENIX-5789.4.x.v4.patch, PHOENIX-5789.4.x.v5.patch, > PHOENIX-5789.4.x.v6.patch, PHOENIX-5789.4.x.v7.patch, > PHOENIX-5789.master.addendum.patch, PHOENIX-5789.master.addendum.v2.patch, > PHOENIX-5789.master.v1.patch, PHOENIX-5789.master.v2.patch, > PHOENIX-5789.master.v3.patch, PHOENIX-5789.master.v4.patch > > > Phoenix uses at least the following JSON libraries: > * gson > * jackson > * jettison > Of these, only the jackson usage is performance critical, as it is used > during bulk loading. > Try to standardize on a single one to reduce dependency hell. -- This message was sent by Atlassian Jira (v8.3.4#803005)
