[jira] [Updated] (PHOENIX-6617) IndexRegionObserver should create mutations for the transforming table

2021-12-21 Thread Gokcen Iskender (Jira) 


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

Gokcen Iskender updated PHOENIX-6617:
-
Summary: IndexRegionObserver should create mutations for the transforming 
table  (was: TransformTool should fix unverified rows and do validation like 
IndexTool)

> IndexRegionObserver should create mutations for the transforming table
> --
>
> Key: PHOENIX-6617
> URL: https://issues.apache.org/jira/browse/PHOENIX-6617
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Gokcen Iskender
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (PHOENIX-6617) TransformTool should fix unverified rows and do validation like IndexTool

2021-12-21 Thread Gokcen Iskender (Jira) 
Gokcen Iskender created PHOENIX-6617:


 Summary: TransformTool should fix unverified rows and do 
validation like IndexTool
 Key: PHOENIX-6617
 URL: https://issues.apache.org/jira/browse/PHOENIX-6617
 Project: Phoenix
  Issue Type: Sub-task
Reporter: Gokcen Iskender






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Resolved] (PHOENIX-6612) Add TransformTool

2021-12-21 Thread Gokcen Iskender (Jira) 


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

Gokcen Iskender resolved PHOENIX-6612.
--
Resolution: Fixed

> Add TransformTool
> -
>
> Key: PHOENIX-6612
> URL: https://issues.apache.org/jira/browse/PHOENIX-6612
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Gokcen Iskender
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (TEPHRA-320) Compiling Tephra with Hadoop 3.3.1

2021-12-21 Thread Lars Hofhansl (Jira) 


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

Lars Hofhansl updated TEPHRA-320:
-
Description: 
Turns out this was missing Hadoop's thirdparty library.
{code}
diff --git a/tephra-distribution/pom.xml b/tephra-distribution/pom.xml
index 6a9494e2..1f192c3d 100644
--- a/tephra-distribution/pom.xml
+++ b/tephra-distribution/pom.xml
@@ -97,6 +97,11 @@
tephra-hbase-compat-2.3
${project.version}

+    
+      org.apache.hadoop.thirdparty
+      hadoop-shaded-guava
+      1.1.1
+    



{code}

  was:
Turns out this was missing Hadoop's thirdparty library.

diff --git a/tephra-distribution/pom.xml b/tephra-distribution/pom.xml
index 6a9494e2..1f192c3d 100644
--- a/tephra-distribution/pom.xml
+++ b/tephra-distribution/pom.xml
@@ -97,6 +97,11 @@
tephra-hbase-compat-2.3
${project.version}

+    
+      org.apache.hadoop.thirdparty
+      hadoop-shaded-guava
+      1.1.1
+    





> Compiling Tephra with Hadoop 3.3.1
> --
>
> Key: TEPHRA-320
> URL: https://issues.apache.org/jira/browse/TEPHRA-320
> Project: Phoenix Tephra
>  Issue Type: Bug
>Reporter: Lars Hofhansl
>Assignee: Poorna Chandra
>Priority: Major
>
> Turns out this was missing Hadoop's thirdparty library.
> {code}
> diff --git a/tephra-distribution/pom.xml b/tephra-distribution/pom.xml
> index 6a9494e2..1f192c3d 100644
> --- a/tephra-distribution/pom.xml
> +++ b/tephra-distribution/pom.xml
> @@ -97,6 +97,11 @@
> tephra-hbase-compat-2.3
> ${project.version}
> 
> +    
> +      org.apache.hadoop.thirdparty
> +      hadoop-shaded-guava
> +      1.1.1
> +    
> 
> 
> {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (TEPHRA-319) HBase 2.4 is missing from Tephra-Distribution

2021-12-21 Thread Lars Hofhansl (Jira) 


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

Lars Hofhansl updated TEPHRA-319:
-
Description: 
Just needs this:
{code}
diff --git a/tephra-distribution/pom.xml b/tephra-distribution/pom.xml
index 6a9494e2..1f192c3d 100644
— a/tephra-distribution/pom.xml
+++ b/tephra-distribution/pom.xml
@@ -97,6 +97,11 @@
tephra-hbase-compat-2.3
${project.version}

+    
+      org.apache.tephra
+      tephra-hbase-compat-2.4
+      ${project.version}
+    



{code}

  was:
Just needs this:

diff --git a/tephra-distribution/pom.xml b/tephra-distribution/pom.xml
index 6a9494e2..1f192c3d 100644
--- a/tephra-distribution/pom.xml
+++ b/tephra-distribution/pom.xml
@@ -97,6 +97,11 @@
tephra-hbase-compat-2.3
${project.version}

+    
+      org.apache.tephra
+      tephra-hbase-compat-2.4
+      ${project.version}
+    





> HBase 2.4 is missing from Tephra-Distribution
> -
>
> Key: TEPHRA-319
> URL: https://issues.apache.org/jira/browse/TEPHRA-319
> Project: Phoenix Tephra
>  Issue Type: Bug
>Affects Versions: 0.16.1
>Reporter: Lars Hofhansl
>Assignee: Poorna Chandra
>Priority: Major
>
> Just needs this:
> {code}
> diff --git a/tephra-distribution/pom.xml b/tephra-distribution/pom.xml
> index 6a9494e2..1f192c3d 100644
> — a/tephra-distribution/pom.xml
> +++ b/tephra-distribution/pom.xml
> @@ -97,6 +97,11 @@
> tephra-hbase-compat-2.3
> ${project.version}
> 
> +    
> +      org.apache.tephra
> +      tephra-hbase-compat-2.4
> +      ${project.version}
> +    
> 
> 
> {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (TEPHRA-320) Compiling Tephra with Hadoop 3.3.1

2021-12-21 Thread Lars Hofhansl (Jira) 
Lars Hofhansl created TEPHRA-320:


 Summary: Compiling Tephra with Hadoop 3.3.1
 Key: TEPHRA-320
 URL: https://issues.apache.org/jira/browse/TEPHRA-320
 Project: Phoenix Tephra
  Issue Type: Bug
Reporter: Lars Hofhansl
Assignee: Poorna Chandra


Turns out this was missing Hadoop's thirdparty library.

diff --git a/tephra-distribution/pom.xml b/tephra-distribution/pom.xml
index 6a9494e2..1f192c3d 100644
--- a/tephra-distribution/pom.xml
+++ b/tephra-distribution/pom.xml
@@ -97,6 +97,11 @@
tephra-hbase-compat-2.3
${project.version}

+    
+      org.apache.hadoop.thirdparty
+      hadoop-shaded-guava
+      1.1.1
+    






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (TEPHRA-319) HBase 2.4 is missing from Tephra-Distribution

2021-12-21 Thread Lars Hofhansl (Jira) 
Lars Hofhansl created TEPHRA-319:


 Summary: HBase 2.4 is missing from Tephra-Distribution
 Key: TEPHRA-319
 URL: https://issues.apache.org/jira/browse/TEPHRA-319
 Project: Phoenix Tephra
  Issue Type: Bug
Affects Versions: 0.16.1
Reporter: Lars Hofhansl
Assignee: Poorna Chandra


Just needs this:

diff --git a/tephra-distribution/pom.xml b/tephra-distribution/pom.xml
index 6a9494e2..1f192c3d 100644
--- a/tephra-distribution/pom.xml
+++ b/tephra-distribution/pom.xml
@@ -97,6 +97,11 @@
tephra-hbase-compat-2.3
${project.version}

+    
+      org.apache.tephra
+      tephra-hbase-compat-2.4
+      ${project.version}
+    






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (PHOENIX-6616) Alter table command can be used to set normalization_enabled=true on salted tables

2021-12-21 Thread Aman Poonia (Jira) 
Aman Poonia created PHOENIX-6616:


 Summary: Alter table command can be used to set 
normalization_enabled=true on salted tables
 Key: PHOENIX-6616
 URL: https://issues.apache.org/jira/browse/PHOENIX-6616
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 5.1.2, 4.16.1
Reporter: Aman Poonia


Here is what i found

CREATE TABLE IF NOT EXISTS table1(a BIGINT NOT NULL, b BIGINT NOT NULL  
CONSTRAINT PK PRIMARY KEY (a, b)) TTL=7776000, NORMALIZATION_ENABLED=true, 
SALT_BUCKETS=16, DISABLE_TABLE_SOR=true, NORMALIZER_TARGET_REGION_SIZE=5200;


Error: ERROR 1147 (42Y86): Should not enable normalizer on salted table. 
tableName=TABLE1 (state=42Y86,code=1147)
java.sql.SQLException: ERROR 1147 (42Y86): Should not enable normalizer on 
salted table. tableName=TABLE1
    at 
org.apache.phoenix.exception.SQLExceptionCode$Factory$1.newException(SQLExceptionCode.java:618)
    at 
org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:228)
    at 
org.apache.phoenix.query.ConnectionQueryServicesImpl.ensureTableCreated(ConnectionQueryServicesImpl.java:1462)
    at 
org.apache.phoenix.query.ConnectionQueryServicesImpl.createTable(ConnectionQueryServicesImpl.java:1983)
    at 
org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:3094)
    at 
org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:1118)
    at 
org.apache.phoenix.compile.CreateTableCompiler$CreateTableMutationPlan.execute(CreateTableCompiler.java:421)
    at 
org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:516)
    at 
org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:482)
    at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
    at 
org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:481)
    at 
org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:469)
    at 
org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:2036)
    at sqlline.Commands.execute(Commands.java:814)
    at sqlline.Commands.sql(Commands.java:754)

 

 

0: jdbc:phoenix:localhost:50141> CREATE TABLE IF NOT EXISTS table1(a BIGINT NOT 
NULL, b BIGINT NOT NULL  CONSTRAINT PK PRIMARY KEY (a, b)) TTL=7776000, 
NORMALIZATION_ENABLED=false, SALT_BUCKETS=16, DISABLE_TABLE_SOR=true, 
NORMALIZER_TARGET_REGION_SIZE=5200;
No rows affected (2.295 seconds)


0: jdbc:phoenix:localhost:50141> ALTER TABLE table1 set 
NORMALIZATION_ENABLED=true;
No rows affected (1.374 seconds)


 So basically we are still able to set the normalization if we go through the 
alter table. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)