[jira] [Resolved] (PHOENIX-4093) org.apache.phoenix.exception.PhoenixIOException: java.net.SocketTimeoutException: callTimeout=60000, callDuration=60304:

2018-09-11 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai resolved PHOENIX-4093. - Resolution: Not A Bug > org.apache.phoenix.exception.PhoenixIOException: >

[jira] [Created] (PHOENIX-4901) support insert grammar for spark-phoenix module

2018-09-12 Thread Jaanai (JIRA)
Jaanai created PHOENIX-4901: --- Summary: support insert grammar for spark-phoenix module Key: PHOENIX-4901 URL: https://issues.apache.org/jira/browse/PHOENIX-4901 Project: Phoenix Issue Type: New

[jira] [Resolved] (PHOENIX-4364) java.sql.SQLException: ERROR 2008 (INT10): Unable to find cached index metadata.

2018-09-11 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai resolved PHOENIX-4364. - Resolution: Not A Problem > java.sql.SQLException: ERROR 2008 (INT10): Unable to find cached index >

[jira] [Created] (PHOENIX-4970) Test throws NPE when compiles query in LocalIndexIT->testLocalIndexSelfJoin

2018-10-14 Thread Jaanai (JIRA)
Jaanai created PHOENIX-4970: --- Summary: Test throws NPE when compiles query in LocalIndexIT->testLocalIndexSelfJoin Key: PHOENIX-4970 URL: https://issues.apache.org/jira/browse/PHOENIX-4970 Project:

[jira] [Updated] (PHOENIX-4970) Integration test throws NPE in LocalIndexIT->testLocalIndexSelfJoin

2018-10-14 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4970: Summary: Integration test throws NPE in LocalIndexIT->testLocalIndexSelfJoin (was: Test throws NPE

[jira] [Updated] (PHOENIX-4971) Drop index will execute successfully using Incorrect name of parent tables

2018-10-14 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4971: Priority: Critical (was: Major) > Drop index will execute successfully using Incorrect name of parent

[jira] [Created] (PHOENIX-4971) Checking table name whether legal when executes drop table

2018-10-14 Thread Jaanai (JIRA)
Jaanai created PHOENIX-4971: --- Summary: Checking table name whether legal when executes drop table Key: PHOENIX-4971 URL: https://issues.apache.org/jira/browse/PHOENIX-4971 Project: Phoenix Issue

[jira] [Updated] (PHOENIX-4971) Drop index will execute successfully using Incorrect name of parent tables

2018-10-14 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4971: Summary: Drop index will execute successfully using Incorrect name of parent tables (was: Checking

[jira] [Updated] (PHOENIX-4971) Drop index will execute successfully using Incorrect name of parent tables

2018-10-15 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4971: Attachment: PHOENIX-4971-master.patch > Drop index will execute successfully using Incorrect name of

[jira] [Updated] (PHOENIX-4971) Drop index will execute successfully using Incorrect name of parent tables

2018-10-18 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4971: Attachment: PHOENIX-4971-master-v2.patch > Drop index will execute successfully using Incorrect name of

[jira] [Updated] (PHOENIX-4971) Drop index will execute successfully using Incorrect name of parent tables

2018-10-18 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4971: Attachment: PHOENIX-4971-master-v3.patch > Drop index will execute successfully using Incorrect name of

[jira] [Updated] (PHOENIX-4974) Gets all regions uses get requests is extremely slows for big table

2018-10-16 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4974: Attachment: performance.png > Gets all regions uses get requests is extremely slows for big table >

[jira] [Assigned] (PHOENIX-4974) Gets all regions uses get requests is extremely slows for big table

2018-10-16 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai reassigned PHOENIX-4974: --- Assignee: Jaanai > Gets all regions uses get requests is extremely slows for big table >

[jira] [Updated] (PHOENIX-4974) Gets all regions uses get requests is extremely slows for big table

2018-10-16 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4974: Summary: Gets all regions uses get requests is extremely slows for big table (was: Gets all regions

[jira] [Updated] (PHOENIX-4974) Gets all regions uses get requests is extremely slows for big table

2018-10-16 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4974: Attachment: (was: Screen Shot 2018-10-16 at 19.53.48.png) > Gets all regions uses get requests is

[jira] [Updated] (PHOENIX-4974) Gets all regions uses get requests is extremely slows for big table

2018-10-16 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4974: Attachment: performance.png > Gets all regions uses get requests is extremely slows for big table >

[jira] [Updated] (PHOENIX-4974) Gets all regions uses get requests is extremely slows for big table

2018-10-16 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4974: Attachment: performance.png > Gets all regions uses get requests is extremely slows for big table >

[jira] [Updated] (PHOENIX-4974) Gets all regions uses get requests is extremely slows for big table

2018-10-16 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4974: Priority: Blocker (was: Major) > Gets all regions uses get requests is extremely slows for big table >

[jira] [Created] (PHOENIX-4974) Gets all regions uses get requests serially is extremely slows for table has lots of regions

2018-10-16 Thread Jaanai (JIRA)
Jaanai created PHOENIX-4974: --- Summary: Gets all regions uses get requests serially is extremely slows for table has lots of regions Key: PHOENIX-4974 URL: https://issues.apache.org/jira/browse/PHOENIX-4974

[jira] [Updated] (PHOENIX-4974) Gets all regions uses get requests is extremely slows for big table

2018-10-16 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4974: Attachment: Screen Shot 2018-10-16 at 19.53.48.png > Gets all regions uses get requests is extremely

[jira] [Updated] (PHOENIX-4974) Gets all regions uses get requests is extremely slows for big table

2018-10-16 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4974: Attachment: PHOENIX-4974-master.patch > Gets all regions uses get requests is extremely slows for big

[jira] [Updated] (PHOENIX-4974) Gets all regions uses get requests is extremely slows for big table

2018-10-16 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4974: Attachment: (was: performance.png) > Gets all regions uses get requests is extremely slows for big

[jira] [Updated] (PHOENIX-4974) Gets all regions uses get requests is extremely slows for big table

2018-10-16 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4974: Attachment: (was: performance.png) > Gets all regions uses get requests is extremely slows for big

[jira] [Updated] (PHOENIX-4971) Drop index will execute successfully using Incorrect name of parent tables

2018-10-28 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4971: Attachment: (was: PHOENIX-4971-master-v4.patch) > Drop index will execute successfully using

[jira] [Updated] (PHOENIX-4971) Drop index will execute successfully using Incorrect name of parent tables

2018-10-28 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4971: Attachment: PHOENIX-4971-master-v4.patch > Drop index will execute successfully using Incorrect name of

[jira] [Updated] (PHOENIX-4971) Drop index will execute successfully using Incorrect name of parent tables

2018-10-28 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4971: Attachment: PHOENIX-4971-master-v4.patch > Drop index will execute successfully using Incorrect name of

[jira] [Updated] (PHOENIX-4971) Drop index will execute successfully using Incorrect name of parent tables

2018-11-01 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4971: Attachment: PHOENIX-4971-master-v5-it-fixed.patch > Drop index will execute successfully using Incorrect

[jira] [Updated] (PHOENIX-4815) support alter table modify column

2018-09-29 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4815: Attachment: PHOENIX-4815-master-v2.patch > support alter table modify column >

[jira] [Updated] (PHOENIX-4815) support alter table modify column

2018-09-21 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4815: Affects Version/s: 4.13.0 4.14.0 > support alter table modify column >

[jira] [Created] (PHOENIX-4915) The client gets stuck when multi threads concurrently writing data table(has global index) with same rows

2018-09-21 Thread Jaanai (JIRA)
Jaanai created PHOENIX-4915: --- Summary: The client gets stuck when multi threads concurrently writing data table(has global index) with same rows Key: PHOENIX-4915 URL:

[jira] [Updated] (PHOENIX-4915) The client gets stuck when using same rows concurrently writing data table

2018-09-21 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4915: Summary: The client gets stuck when using same rows concurrently writing data table (was: The client

[jira] [Updated] (PHOENIX-4915) The client gets stuck when using same rows concurrently writing data table

2018-09-21 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4915: Attachment: (was: Screen Shot 2018-09-21 at 19.19.28.png) > The client gets stuck when using same

[jira] [Updated] (PHOENIX-4904) NPE exception when use non-existing fields in function

2018-09-21 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4904: Summary: NPE exception when use non-existing fields in function (was: NPE exception when use

[jira] [Updated] (PHOENIX-4915) The client gets stuck when using same rows concurrently writing data table

2018-09-21 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4915: Attachment: Screen Shot 2018-09-21 at 19.19.28.png > The client gets stuck when using same rows

[jira] [Updated] (PHOENIX-4915) The client gets stuck when using same rows concurrently writing data table

2018-09-21 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4915: Attachment: test.sql test.java > The client gets stuck when using same rows concurrently

[jira] [Updated] (PHOENIX-4915) The client gets stuck when using same rows concurrently writing data table

2018-09-21 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4915: Attachment: image-2018-09-21-19-21-41-898.png > The client gets stuck when using same rows concurrently

[jira] [Updated] (PHOENIX-4915) The client gets stuck when using same rows concurrently writing data table

2018-09-21 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4915: Attachment: (was: image-2018-09-21-19-21-41-898.png) > The client gets stuck when using same rows

[jira] [Updated] (PHOENIX-4915) The client gets stuck when using same rows concurrently writing data table

2018-09-21 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4915: Attachment: image-2018-09-21-19-30-12-989.png > The client gets stuck when using same rows concurrently

[jira] [Updated] (PHOENIX-4915) The client gets stuck when using same rows concurrently writing data table

2018-09-21 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4915: Description: The client has got stuck when using the multi-thread writes the same rows data into a data

[jira] [Updated] (PHOENIX-4904) NPE exception when use non-existing fields in function

2018-09-21 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4904: Attachment: PHOENIX-4904-master.patch > NPE exception when use non-existing fields in function >

[jira] [Updated] (PHOENIX-4901) support insert grammar for spark-phoenix module

2018-09-25 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4901: Attachment: PHOENIX-4901-master.patch > support insert grammar for spark-phoenix module >

[jira] [Updated] (PHOENIX-4901) support insert grammar for spark-phoenix module

2018-09-25 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4901: Attachment: (was: PHOENIX-4901.patch) > support insert grammar for spark-phoenix module >

[jira] [Resolved] (PHOENIX-4915) The client gets stuck when using same rows concurrently writing data table

2019-01-02 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai resolved PHOENIX-4915. - Resolution: Not A Problem > The client gets stuck when using same rows concurrently writing data table

[jira] [Updated] (PHOENIX-5055) Split mutations batches probably affects correctness of index data

2018-12-10 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-5055: Attachment: PHOENIX-5055-4.x-HBase-1.4-v4.patch > Split mutations batches probably affects correctness

[jira] [Updated] (PHOENIX-5055) Split mutations batches probably affects correctness of index data

2018-12-04 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-5055: Description: In order to get more performance, we split the list of mutations into multiple batches in

[jira] [Updated] (PHOENIX-5055) Split mutations batches probably affects correctness of index data

2018-12-04 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-5055: Description: In order to get more performance, we split the list of mutations into multiple batches in

[jira] [Updated] (PHOENIX-5055) Split mutations batches probably affects correctness of index data

2018-12-07 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-5055: Attachment: PHOENIX-5055-4.x-HBase-1.4-v3.patch > Split mutations batches probably affects correctness

[jira] [Updated] (PHOENIX-5055) Split mutations batches probably affects correctness of index data

2018-12-03 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-5055: Summary: Split mutations batches probably affects correctness of index data (was: Split mutations into

[jira] [Updated] (PHOENIX-5055) Split mutations into multiple batches probably affects correctness of index data

2018-12-03 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-5055: Summary: Split mutations into multiple batches probably affects correctness of index data (was: Split

[jira] [Updated] (PHOENIX-5055) Split mutations batches probably affects correctness of index data

2018-12-03 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-5055: Attachment: PHOENIX-5055-v4.x-HBase-1.4.patch > Split mutations batches probably affects correctness of

[jira] [Created] (PHOENIX-5055) Split the list of mutations into multiple batches probably cause correctness of index data

2018-12-03 Thread Jaanai (JIRA)
Jaanai created PHOENIX-5055: --- Summary: Split the list of mutations into multiple batches probably cause correctness of index data Key: PHOENIX-5055 URL: https://issues.apache.org/jira/browse/PHOENIX-5055

[jira] [Assigned] (PHOENIX-300) Support TRUNCATE TABLE

2018-12-03 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai reassigned PHOENIX-300: -- Assignee: Jaanai > Support TRUNCATE TABLE > -- > > Key:

[jira] [Updated] (PHOENIX-5055) Split mutations batches probably affects correctness of index data

2018-12-03 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-5055: Description: In order to get more performance, we split the list of mutations into multiple batches in

[jira] [Updated] (PHOENIX-5055) Split mutations batches probably affects correctness of index data

2018-12-03 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-5055: Attachment: ConcurrentTest.java > Split mutations batches probably affects correctness of index data >

[jira] [Updated] (PHOENIX-5055) Split mutations batches probably affects correctness of index data

2018-12-06 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-5055: Attachment: PHOENIX-5055-4.x-HBase-1.4-v2.patch > Split mutations batches probably affects correctness

[jira] [Created] (PHOENIX-5066) The TimeZone is incorrectly used during writing or reading data

2018-12-10 Thread Jaanai (JIRA)
Jaanai created PHOENIX-5066: --- Summary: The TimeZone is incorrectly used during writing or reading data Key: PHOENIX-5066 URL: https://issues.apache.org/jira/browse/PHOENIX-5066 Project: Phoenix

[jira] [Updated] (PHOENIX-5066) The TimeZone is incorrectly used during writing or reading data

2018-12-10 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-5066: Description: We have two methods to write data when uses JDBC API. #1. Uses _the exceuteUpdate_ method

[jira] [Updated] (PHOENIX-5066) The TimeZone is incorrectly used during writing or reading data

2018-12-10 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-5066: Attachment: DateTest.java > The TimeZone is incorrectly used during writing or reading data >

[jira] [Updated] (PHOENIX-5066) The TimeZone is incorrectly used during writing or reading data

2018-12-10 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-5066: Description: We have two methods to write data when uses JDBC API. #1. Uses _the exceuteUpdate_ method

[jira] [Updated] (PHOENIX-5066) The TimeZone is incorrectly used during writing or reading data

2018-12-10 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-5066: Description: We have two methods to write data when uses JDBC API. #1. Uses _the exceuteUpdate_ method

[jira] [Updated] (PHOENIX-4971) Drop index will execute successfully using Incorrect name of parent tables

2018-11-23 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4971: Attachment: PHOENIX-4971-master-v6.patch > Drop index will execute successfully using Incorrect name of

[jira] [Updated] (PHOENIX-4971) Drop index will execute successfully using Incorrect name of parent tables

2018-11-23 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4971: Affects Version/s: 4.14.1 Fix Version/s: 4.15.0 > Drop index will execute successfully using

[jira] [Updated] (PHOENIX-4971) Drop index will execute successfully using Incorrect name of parent tables

2018-11-23 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4971: Attachment: (was: PHOENIX-4971-master-v6.patch) > Drop index will execute successfully using

[jira] [Updated] (PHOENIX-4971) Drop index will execute successfully using Incorrect name of parent tables

2018-11-24 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4971: Attachment: (was: PHOENIX-4971-4.x-HBase-1.4-v6.patch) > Drop index will execute successfully using

[jira] [Updated] (PHOENIX-4971) Drop index will execute successfully using Incorrect name of parent tables

2018-11-25 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4971: Attachment: (was: PHOENIX-4971-4.x-HBase-1.2-v6.patch) > Drop index will execute successfully using

[jira] [Updated] (PHOENIX-4971) Drop index will execute successfully using Incorrect name of parent tables

2018-11-25 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4971: Attachment: (was: PHOENIX-4971-4.x-HBase-1.3-v6.patch) > Drop index will execute successfully using

[jira] [Updated] (PHOENIX-4971) Drop index will execute successfully using Incorrect name of parent tables

2018-11-24 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4971: Attachment: (was: PHOENIX-4971-4.x-HBase-1.1-v6.patch) > Drop index will execute successfully using

[jira] [Updated] (PHOENIX-4915) The client gets stuck when using same rows concurrently writing data table

2019-01-02 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-4915: Priority: Trivial (was: Blocker) > The client gets stuck when using same rows concurrently writing data

[jira] [Updated] (PHOENIX-4915) The client gets stuck when using same rows concurrently writing data table

2019-01-02 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-4915: Priority: Major (was: Trivial) > The client gets stuck when using same rows concurrently writing data

[jira] [Created] (PHOENIX-4904) NPE exception when use non-existing filed in function

2018-09-13 Thread Jaanai (JIRA)
Jaanai created PHOENIX-4904: --- Summary: NPE exception when use non-existing filed in function Key: PHOENIX-4904 URL: https://issues.apache.org/jira/browse/PHOENIX-4904 Project: Phoenix Issue Type:

[jira] [Updated] (PHOENIX-4904) NPE exception when use non-existing filed in function

2018-09-13 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4904: Issue Type: Bug (was: New Feature) > NPE exception when use non-existing filed in function >

[jira] [Updated] (PHOENIX-4901) support insert grammar for spark-phoenix module

2018-09-12 Thread Jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4901: Attachment: PHOENIX-4901.patch > support insert grammar for spark-phoenix module >

[jira] [Updated] (PHOENIX-5226) The format of VIEW_MODIFIED_PROPERTY_BYTES is incorrect as a tag of the cell

2019-04-02 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5226: Description: We use a tag of cell to indicat that some properties should not be derived from the base

[jira] [Created] (PHOENIX-5226) The format of VIEW_MODIFIED_PROPERTY_BYTES is incorrect as a tag of the cell

2019-04-02 Thread jaanai (JIRA)
jaanai created PHOENIX-5226: --- Summary: The format of VIEW_MODIFIED_PROPERTY_BYTES is incorrect as a tag of the cell Key: PHOENIX-5226 URL: https://issues.apache.org/jira/browse/PHOENIX-5226 Project:

[jira] [Updated] (PHOENIX-5226) The format of VIEW_MODIFIED_PROPERTY_BYTES is incorrect as a tag of the cell

2019-04-02 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5226: Environment: (was: {panel:title=My title} Some text with a title {panel} ) > The format of

[jira] [Updated] (PHOENIX-5169) Query logger is still initialized for each query when the log level is off

2019-03-26 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5169: Attachment: PHOENIX-5169-master-v4.patch > Query logger is still initialized for each query when the log

[jira] [Updated] (PHOENIX-5226) The format of VIEW_MODIFIED_PROPERTY_BYTES is incorrect as a tag of the cell

2019-04-03 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5226: Attachment: PHOENIX-5226-master.patch > The format of VIEW_MODIFIED_PROPERTY_BYTES is incorrect as a

[jira] [Updated] (PHOENIX-5226) The format of VIEW_MODIFIED_PROPERTY_BYTES is incorrect as a tag of the cell

2019-04-07 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5226: Attachment: PHOENIX-5226-master-v2.patch > The format of VIEW_MODIFIED_PROPERTY_BYTES is incorrect as a

[jira] [Updated] (PHOENIX-5169) Query logger is still initialized for each query when the log level is off

2019-02-28 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5169: Attachment: PHOENIX-5169-master-2.patch > Query logger is still initialized for each query when the log

[jira] [Updated] (PHOENIX-5171) SkipScan incorrectly filters composite primary key which the trailing is NULL

2019-03-04 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5171: Description: Running the below SQL: {code:sql} create table if not exists aiolos( vdate varchar, tab

[jira] [Created] (PHOENIX-5171) SkipScan incorrectly filters composite primary key which the trailing is NULL

2019-02-27 Thread jaanai (JIRA)
jaanai created PHOENIX-5171: --- Summary: SkipScan incorrectly filters composite primary key which the trailing is NULL Key: PHOENIX-5171 URL: https://issues.apache.org/jira/browse/PHOENIX-5171 Project:

[jira] [Created] (PHOENIX-5169) Query logger is still initialized for each query when the log level is off

2019-02-27 Thread jaanai (JIRA)
jaanai created PHOENIX-5169: --- Summary: Query logger is still initialized for each query when the log level is off Key: PHOENIX-5169 URL: https://issues.apache.org/jira/browse/PHOENIX-5169 Project: Phoenix

[jira] [Updated] (PHOENIX-5169) Query logger is still initialized for each query when the log level is off

2019-02-27 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5169: Description: we will still invoke createQueryLogger in PhoenixStatement for each query when query

[jira] [Updated] (PHOENIX-5169) Query logger is still initialized for each query when the log level is off

2019-02-28 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5169: Attachment: PHOENIX-5169-master.patch > Query logger is still initialized for each query when the log

[jira] [Updated] (PHOENIX-5171) SkipScan incorrectly filters composite primary key which the trailing is NULL

2019-02-28 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5171: Attachment: PHOENIX-5171-master.patch > SkipScan incorrectly filters composite primary key which the

[jira] [Updated] (PHOENIX-5171) SkipScan incorrectly filters composite primary key which the trailing is NULL

2019-02-28 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5171: Fix Version/s: (was: 5.0.0) 5.1.0 > SkipScan incorrectly filters composite

[jira] [Updated] (PHOENIX-5171) SkipScan incorrectly filters composite primary key which the key range contains all values

2019-03-10 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5171: Summary: SkipScan incorrectly filters composite primary key which the key range contains all values

[jira] [Updated] (PHOENIX-5171) SkipScan incorrectly filters composite primary key which the key range contains all values

2019-03-11 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5171: Description: Running the below SQL: {code:sql} create table if not exists aiolos( vdate varchar, tab

[jira] [Updated] (PHOENIX-5171) SkipScan incorrectly filters composite primary key which the key range contains all values

2019-03-11 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5171: Attachment: (was: PHOENIX-5171-master-v2.patch) > SkipScan incorrectly filters composite primary key

[jira] [Updated] (PHOENIX-5171) SkipScan incorrectly filters composite primary key which the key range contains all values

2019-03-10 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5171: Attachment: PHOENIX-5171-master-v2.patch > SkipScan incorrectly filters composite primary key which the

[jira] [Updated] (PHOENIX-5171) SkipScan incorrectly filters composite primary key which the key range contains all values

2019-03-10 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5171: Description: Running the below SQL: {code:sql} create table if not exists aiolos( vdate varchar, tab

[jira] [Updated] (PHOENIX-5171) SkipScan incorrectly filters composite primary key which the key range contains all values

2019-03-11 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5171: Description: Running the below SQL: {code:sql} create table if not exists aiolos( vdate varchar, tab

[jira] [Updated] (PHOENIX-5171) SkipScan incorrectly filters composite primary key which the key range contains all values

2019-03-11 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5171: Attachment: PHOENIX-5171-master-v2.patch > SkipScan incorrectly filters composite primary key which the

[jira] [Updated] (PHOENIX-5169) Query logger is still initialized for each query when the log level is off

2019-03-11 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5169: Attachment: (was: PHOENIX-5169-master-2.patch) > Query logger is still initialized for each query

[jira] [Updated] (PHOENIX-5169) Query logger is still initialized for each query when the log level is off

2019-03-11 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5169: Attachment: PHOENIX-5169-master-v2.patch > Query logger is still initialized for each query when the log

[jira] [Updated] (PHOENIX-5171) SkipScan incorrectly filters composite primary key which the key range contains all values

2019-03-11 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5171: Attachment: (was: PHOENIX-5171-master-v2.patch) > SkipScan incorrectly filters composite primary key

[jira] [Updated] (PHOENIX-5171) SkipScan incorrectly filters composite primary key which the key range contains all values

2019-03-11 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5171: Attachment: PHOENIX-5171-master-v2.patch > SkipScan incorrectly filters composite primary key which the

[jira] [Updated] (PHOENIX-5169) Query logger is still initialized for each query when the log level is off

2019-03-18 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5169: Attachment: PHOENIX-5169-master-v3.patch > Query logger is still initialized for each query when the log

[jira] [Resolved] (PHOENIX-5226) The format of VIEW_MODIFIED_PROPERTY_BYTES is incorrect as a tag of the cell

2019-04-18 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai resolved PHOENIX-5226. - Resolution: Fixed > The format of VIEW_MODIFIED_PROPERTY_BYTES is incorrect as a tag of the cell >

[jira] [Updated] (PHOENIX-5266) Client can only write on Index Table and skip data table if failure happens because of region split/move etc

2019-05-18 Thread jaanai (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5266: Fix Version/s: 5.0.1 > Client can only write on Index Table and skip data table if failure happens >

  1   2   >