[jira] [Updated] (PHOENIX-5026) Add client setting to disable server side mutations

2018-11-21 Thread Lars Hofhansl (JIRA)


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

Lars Hofhansl updated PHOENIX-5026:
---
Comment: was deleted

(was: Stupid question... Are the 4.x-HBase-1.1 and 4.x-HBase-0.98 branches 
still active?
Their commit history seems to be quite different.)

> Add client setting to disable server side mutations
> ---
>
> Key: PHOENIX-5026
> URL: https://issues.apache.org/jira/browse/PHOENIX-5026
> Project: Phoenix
>  Issue Type: Improvement
>Affects Versions: 4.15.0, 4.14.1
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
>Priority: Major
> Attachments: 5026-withtests-v2.txt, 5026-withtests.txt, 5026.txt
>
>
> Like PHOENIX-3818 server side deletes.
> We've seen issues with larger deletes (see PHOENIX-5007).
> In many case it is probably better to handle deletes from the client. That 
> way requests are properly chunked, handler threads are not tied up, and 
> there's no "funniness" with issues mutation from a scan RPC.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (PHOENIX-5026) Add client setting to disable server side mutations

2018-11-21 Thread Lars Hofhansl (JIRA)


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

Lars Hofhansl resolved PHOENIX-5026.

   Resolution: Fixed
Fix Version/s: 4.14.2
   4.15.0

> Add client setting to disable server side mutations
> ---
>
> Key: PHOENIX-5026
> URL: https://issues.apache.org/jira/browse/PHOENIX-5026
> Project: Phoenix
>  Issue Type: Improvement
>Affects Versions: 4.15.0, 4.14.1
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
>Priority: Major
> Fix For: 4.15.0, 4.14.2
>
> Attachments: 5026-withtests-v2.txt, 5026-withtests.txt, 5026.txt
>
>
> Like PHOENIX-3818 server side deletes.
> We've seen issues with larger deletes (see PHOENIX-5007).
> In many case it is probably better to handle deletes from the client. That 
> way requests are properly chunked, handler threads are not tied up, and 
> there's no "funniness" with issues mutation from a scan RPC.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-5026) Add client setting to disable server side mutations

2018-11-21 Thread Lars Hofhansl (JIRA)


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

Lars Hofhansl updated PHOENIX-5026:
---
Summary: Add client setting to disable server side mutations  (was: Add 
client setting to disable server side deletes)

> Add client setting to disable server side mutations
> ---
>
> Key: PHOENIX-5026
> URL: https://issues.apache.org/jira/browse/PHOENIX-5026
> Project: Phoenix
>  Issue Type: Improvement
>Affects Versions: 4.15.0, 4.14.1
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
>Priority: Major
> Attachments: 5026-withtests-v2.txt, 5026-withtests.txt, 5026.txt
>
>
> Like PHOENIX-3818 server side deletes.
> We've seen issues with larger deletes (see PHOENIX-5007).
> In many case it is probably better to handle deletes from the client. That 
> way requests are properly chunked, handler threads are not tied up, and 
> there's no "funniness" with issues mutation from a scan RPC.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [ANNOUNCE] Apache Phoenix 4.14.1 released

2018-11-21 Thread Batyrshin Alexander
Looks like bin packed with some non standard options.

Extracting on Ubuntu-16.04 looks like this:
$ tar -xzf apache-phoenix-4.14.1-HBase-1.4-bin.tar.gz
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.creationtime'
tar: Ignoring unknown extended header keyword 'SCHILY.dev'
tar: Ignoring unknown extended header keyword 'SCHILY.ino'
tar: Ignoring unknown extended header keyword 'SCHILY.nlink'
tar: Ignoring unknown extended header keyword 'SCHILY.dev'
tar: Ignoring unknown extended header keyword 'SCHILY.ino'
...

> On 15 Nov 2018, at 00:39, Vincent Poon  wrote:
> 
> The Apache Phoenix team is pleased to announce the immediate availability
> of the 4.14.1 patch release. Apache Phoenix enables SQL-based OLTP and
> operational analytics for Apache Hadoop using Apache HBase as its backing
> store and providing integration with other projects in the Apache ecosystem
> such as Spark, Hive, Pig, Flume, and MapReduce.
> 
> This patch release has feature parity with supported HBase versions and 
> includes critical bug fixes for secondary indexes.
> 
> Download source and binaries here [1].
> 
> Thanks,
> Vincent (on behalf of the Apache Phoenix team)
> 
> [1] http://phoenix.apache.org/download.html 
> 



[jira] [Updated] (PHOENIX-5040) Release Audit Warning on missing license in OrderIT.java

2018-11-21 Thread Artem Ervits (JIRA)


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

Artem Ervits updated PHOENIX-5040:
--
Attachment: PHOENIX-5040-v01.patch

> Release Audit Warning on missing license in OrderIT.java
> 
>
> Key: PHOENIX-5040
> URL: https://issues.apache.org/jira/browse/PHOENIX-5040
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Attachments: PHOENIX-5040-v01.patch
>
>
> over on Phoenix-5036, noticed a failing license audit. OrderIT.java is 
> missing a license.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (PHOENIX-5040) Release Audit Warning on missing license in OrderIT.java

2018-11-21 Thread Artem Ervits (JIRA)
Artem Ervits created PHOENIX-5040:
-

 Summary: Release Audit Warning on missing license in OrderIT.java
 Key: PHOENIX-5040
 URL: https://issues.apache.org/jira/browse/PHOENIX-5040
 Project: Phoenix
  Issue Type: Improvement
Reporter: Artem Ervits
Assignee: Artem Ervits


over on Phoenix-5036, noticed a failing license audit. OrderIT.java is missing 
a license.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-4765) Add client and server side config property to enable rollback of splittable System Catalog if required

2018-11-21 Thread Thomas D'Silva (JIRA)


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

Thomas D'Silva updated PHOENIX-4765:

Attachment: PHOENIX-4765-v2-4.x-HBase-1.3.patch

> Add client and server side config property to enable rollback of splittable 
> System Catalog if required
> --
>
> Key: PHOENIX-4765
> URL: https://issues.apache.org/jira/browse/PHOENIX-4765
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Thomas D'Silva
>Assignee: Thomas D'Silva
>Priority: Blocker
> Attachments: PHOENIX-4765-v2-4.x-HBase-1.3.patch, 
> PHOENIX-4765-v2.patch
>
>
> After the server has been upgraded we will have a client and server side 
> config property that will allow us to rollback the upgrade if required. This 
> config will:
> 1. Continue storing parent column metadata along with a child view 
> 2. Disallow metadata changes to a base table that require being propagated to 
> child views.
> 3. Prevent SYSTEM.CATALOG from splitting.
> If the client is older than the server we also disallow metadata changes to a 
> base table with child views since we no longer lock the parent on the server 
> side. This is handled on the client side as part of PHOENIX-3534.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-4765) Add client and server side config property to enable rollback of splittable System Catalog if required

2018-11-21 Thread Thomas D'Silva (JIRA)


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

Thomas D'Silva updated PHOENIX-4765:

Attachment: (was: PHOENIX-4765-v2-HBase-1.3.patch)

> Add client and server side config property to enable rollback of splittable 
> System Catalog if required
> --
>
> Key: PHOENIX-4765
> URL: https://issues.apache.org/jira/browse/PHOENIX-4765
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Thomas D'Silva
>Assignee: Thomas D'Silva
>Priority: Blocker
> Attachments: PHOENIX-4765-v2.patch
>
>
> After the server has been upgraded we will have a client and server side 
> config property that will allow us to rollback the upgrade if required. This 
> config will:
> 1. Continue storing parent column metadata along with a child view 
> 2. Disallow metadata changes to a base table that require being propagated to 
> child views.
> 3. Prevent SYSTEM.CATALOG from splitting.
> If the client is older than the server we also disallow metadata changes to a 
> base table with child views since we no longer lock the parent on the server 
> side. This is handled on the client side as part of PHOENIX-3534.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-4765) Add client and server side config property to enable rollback of splittable System Catalog if required

2018-11-21 Thread Thomas D'Silva (JIRA)


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

Thomas D'Silva updated PHOENIX-4765:

Attachment: PHOENIX-4765-v2-HBase-1.3.patch

> Add client and server side config property to enable rollback of splittable 
> System Catalog if required
> --
>
> Key: PHOENIX-4765
> URL: https://issues.apache.org/jira/browse/PHOENIX-4765
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Thomas D'Silva
>Assignee: Thomas D'Silva
>Priority: Blocker
> Attachments: PHOENIX-4765-v2-HBase-1.3.patch, PHOENIX-4765-v2.patch
>
>
> After the server has been upgraded we will have a client and server side 
> config property that will allow us to rollback the upgrade if required. This 
> config will:
> 1. Continue storing parent column metadata along with a child view 
> 2. Disallow metadata changes to a base table that require being propagated to 
> child views.
> 3. Prevent SYSTEM.CATALOG from splitting.
> If the client is older than the server we also disallow metadata changes to a 
> base table with child views since we no longer lock the parent on the server 
> side. This is handled on the client side as part of PHOENIX-3534.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-4765) Add client and server side config property to enable rollback of splittable System Catalog if required

2018-11-21 Thread Thomas D'Silva (JIRA)


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

Thomas D'Silva updated PHOENIX-4765:

Attachment: PHOENIX-4765-v2.patch

> Add client and server side config property to enable rollback of splittable 
> System Catalog if required
> --
>
> Key: PHOENIX-4765
> URL: https://issues.apache.org/jira/browse/PHOENIX-4765
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Thomas D'Silva
>Assignee: Thomas D'Silva
>Priority: Blocker
> Attachments: PHOENIX-4765-v2-HBase-1.3.patch, PHOENIX-4765-v2.patch
>
>
> After the server has been upgraded we will have a client and server side 
> config property that will allow us to rollback the upgrade if required. This 
> config will:
> 1. Continue storing parent column metadata along with a child view 
> 2. Disallow metadata changes to a base table that require being propagated to 
> child views.
> 3. Prevent SYSTEM.CATALOG from splitting.
> If the client is older than the server we also disallow metadata changes to a 
> base table with child views since we no longer lock the parent on the server 
> side. This is handled on the client side as part of PHOENIX-3534.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-4765) Add client and server side config property to enable rollback of splittable System Catalog if required

2018-11-21 Thread Thomas D'Silva (JIRA)


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

Thomas D'Silva updated PHOENIX-4765:

Attachment: (was: PHOENIX-4765-v1.patch)

> Add client and server side config property to enable rollback of splittable 
> System Catalog if required
> --
>
> Key: PHOENIX-4765
> URL: https://issues.apache.org/jira/browse/PHOENIX-4765
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Thomas D'Silva
>Assignee: Thomas D'Silva
>Priority: Blocker
> Attachments: PHOENIX-4765-v2-HBase-1.3.patch, PHOENIX-4765-v2.patch
>
>
> After the server has been upgraded we will have a client and server side 
> config property that will allow us to rollback the upgrade if required. This 
> config will:
> 1. Continue storing parent column metadata along with a child view 
> 2. Disallow metadata changes to a base table that require being propagated to 
> child views.
> 3. Prevent SYSTEM.CATALOG from splitting.
> If the client is older than the server we also disallow metadata changes to a 
> base table with child views since we no longer lock the parent on the server 
> side. This is handled on the client side as part of PHOENIX-3534.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-5039) Fix for warning: The POM for net.minidev:json-smart:jar:2.3-SNAPSHOT is missing, no dependency information available

2018-11-21 Thread Artem Ervits (JIRA)


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

Artem Ervits updated PHOENIX-5039:
--
Docs Text:   (was: unlike minidev, javax.el warning cannot be easily 
excluded

[WARNING] The POM for org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT is missing, 
no dependency information available
[WARNING] The POM for org.glassfish:javax.el:jar:3.0.1-b07-SNAPSHOT is missing, 
no dependency information available
[WARNING] The POM for org.glassfish:javax.el:jar:3.0.1-b08-SNAPSHOT is missing, 
no dependency information available
I'm able to remove the warning by explicitly adding a dependency to project's 
pom but the following messages still appear

[WARNING] jsp-api-2.1.jar, javax.el-3.0.1-b11-SNAPSHOT.jar define 26 
overlapping classes:
[WARNING] - javax.el.ELException
[WARNING] - javax.el.MethodInfo
[WARNING] - javax.el.CompositeELResolver
[WARNING] - javax.el.ELContext
[WARNING] - javax.el.ELContextListener
[WARNING] - javax.el.VariableMapper
[WARNING] - javax.el.CompositeELResolver$CompositeIterator
[WARNING] - javax.el.ResourceBundleELResolver
[WARNING] - javax.el.ValueExpression
[WARNING] - javax.el.MethodExpression
[WARNING] - 16 more...
)

> Fix for warning: The POM for net.minidev:json-smart:jar:2.3-SNAPSHOT is 
> missing, no dependency information available
> 
>
> Key: PHOENIX-5039
> URL: https://issues.apache.org/jira/browse/PHOENIX-5039
> Project: Phoenix
>  Issue Type: Improvement
> Environment: {code:java}
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
> 2018-06-17T14:33:14-04:00)
> Maven home: /opt/apache-maven-3.5.4
> Java version: 1.8.0_172, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"{code}
>  
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
>
> {code:java}
> The POM for net.minidev:json-smart:jar:2.3-SNAPSHOT is missing, no dependency 
> information available{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-5039) Fix for warning: The POM for net.minidev:json-smart:jar:2.3-SNAPSHOT is missing, no dependency information available

2018-11-21 Thread Artem Ervits (JIRA)


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

Artem Ervits updated PHOENIX-5039:
--
Attachment: PHOENIX-5039-v01.patch

> Fix for warning: The POM for net.minidev:json-smart:jar:2.3-SNAPSHOT is 
> missing, no dependency information available
> 
>
> Key: PHOENIX-5039
> URL: https://issues.apache.org/jira/browse/PHOENIX-5039
> Project: Phoenix
>  Issue Type: Improvement
> Environment: {code:java}
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
> 2018-06-17T14:33:14-04:00)
> Maven home: /opt/apache-maven-3.5.4
> Java version: 1.8.0_172, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"{code}
>  
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Attachments: PHOENIX-5039-v01.patch
>
>
> {code:java}
> The POM for net.minidev:json-smart:jar:2.3-SNAPSHOT is missing, no dependency 
> information available{code}
> unlike minidev, javax.el warning cannot be easily excluded
> {code:java}
> [WARNING] The POM for org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT is 
> missing, no dependency information available
> [WARNING] The POM for org.glassfish:javax.el:jar:3.0.1-b07-SNAPSHOT is 
> missing, no dependency information available
> [WARNING] The POM for org.glassfish:javax.el:jar:3.0.1-b08-SNAPSHOT is 
> missing, no dependency information available{code}
> I'm able to remove the warning by explicitly adding a dependency to project's 
> pom but the following messages still appears
> {code:java}
> [WARNING] jsp-api-2.1.jar, javax.el-3.0.1-b11-SNAPSHOT.jar define 26 
> overlapping classes:
> [WARNING] - javax.el.ELException
> [WARNING] - javax.el.MethodInfo
> [WARNING] - javax.el.CompositeELResolver
> [WARNING] - javax.el.ELContext
> [WARNING] - javax.el.ELContextListener
> [WARNING] - javax.el.VariableMapper
> [WARNING] - javax.el.CompositeELResolver$CompositeIterator
> [WARNING] - javax.el.ResourceBundleELResolver
> [WARNING] - javax.el.ValueExpression
> [WARNING] - javax.el.MethodExpression
> [WARNING] - 16 more...{code}
> pinging [~elserj] for thoughts?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-5039) Fix for warning: The POM for net.minidev:json-smart:jar:2.3-SNAPSHOT is missing, no dependency information available

2018-11-21 Thread Artem Ervits (JIRA)


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

Artem Ervits updated PHOENIX-5039:
--
Description: 
{code:java}
The POM for net.minidev:json-smart:jar:2.3-SNAPSHOT is missing, no dependency 
information available{code}
unlike minidev, javax.el warning cannot be easily excluded
{code:java}
[WARNING] The POM for org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT is missing, 
no dependency information available
[WARNING] The POM for org.glassfish:javax.el:jar:3.0.1-b07-SNAPSHOT is missing, 
no dependency information available
[WARNING] The POM for org.glassfish:javax.el:jar:3.0.1-b08-SNAPSHOT is missing, 
no dependency information available{code}
I'm able to remove the warning by explicitly adding a dependency to project's 
pom but the following messages still appears
{code:java}
[WARNING] jsp-api-2.1.jar, javax.el-3.0.1-b11-SNAPSHOT.jar define 26 
overlapping classes:
[WARNING] - javax.el.ELException
[WARNING] - javax.el.MethodInfo
[WARNING] - javax.el.CompositeELResolver
[WARNING] - javax.el.ELContext
[WARNING] - javax.el.ELContextListener
[WARNING] - javax.el.VariableMapper
[WARNING] - javax.el.CompositeELResolver$CompositeIterator
[WARNING] - javax.el.ResourceBundleELResolver
[WARNING] - javax.el.ValueExpression
[WARNING] - javax.el.MethodExpression
[WARNING] - 16 more...{code}
pinging [~elserj] for thoughts?

  was:
{code:java}
The POM for net.minidev:json-smart:jar:2.3-SNAPSHOT is missing, no dependency 
information available{code}


> Fix for warning: The POM for net.minidev:json-smart:jar:2.3-SNAPSHOT is 
> missing, no dependency information available
> 
>
> Key: PHOENIX-5039
> URL: https://issues.apache.org/jira/browse/PHOENIX-5039
> Project: Phoenix
>  Issue Type: Improvement
> Environment: {code:java}
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
> 2018-06-17T14:33:14-04:00)
> Maven home: /opt/apache-maven-3.5.4
> Java version: 1.8.0_172, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"{code}
>  
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
>
> {code:java}
> The POM for net.minidev:json-smart:jar:2.3-SNAPSHOT is missing, no dependency 
> information available{code}
> unlike minidev, javax.el warning cannot be easily excluded
> {code:java}
> [WARNING] The POM for org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT is 
> missing, no dependency information available
> [WARNING] The POM for org.glassfish:javax.el:jar:3.0.1-b07-SNAPSHOT is 
> missing, no dependency information available
> [WARNING] The POM for org.glassfish:javax.el:jar:3.0.1-b08-SNAPSHOT is 
> missing, no dependency information available{code}
> I'm able to remove the warning by explicitly adding a dependency to project's 
> pom but the following messages still appears
> {code:java}
> [WARNING] jsp-api-2.1.jar, javax.el-3.0.1-b11-SNAPSHOT.jar define 26 
> overlapping classes:
> [WARNING] - javax.el.ELException
> [WARNING] - javax.el.MethodInfo
> [WARNING] - javax.el.CompositeELResolver
> [WARNING] - javax.el.ELContext
> [WARNING] - javax.el.ELContextListener
> [WARNING] - javax.el.VariableMapper
> [WARNING] - javax.el.CompositeELResolver$CompositeIterator
> [WARNING] - javax.el.ResourceBundleELResolver
> [WARNING] - javax.el.ValueExpression
> [WARNING] - javax.el.MethodExpression
> [WARNING] - 16 more...{code}
> pinging [~elserj] for thoughts?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (PHOENIX-5039) Fix for warning: The POM for net.minidev:json-smart:jar:2.3-SNAPSHOT is missing, no dependency information available

2018-11-21 Thread Artem Ervits (JIRA)
Artem Ervits created PHOENIX-5039:
-

 Summary: Fix for warning: The POM for 
net.minidev:json-smart:jar:2.3-SNAPSHOT is missing, no dependency information 
available
 Key: PHOENIX-5039
 URL: https://issues.apache.org/jira/browse/PHOENIX-5039
 Project: Phoenix
  Issue Type: Improvement
 Environment: {code:java}
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
2018-06-17T14:33:14-04:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_172, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"{code}
 
Reporter: Artem Ervits
Assignee: Artem Ervits


{code:java}
The POM for net.minidev:json-smart:jar:2.3-SNAPSHOT is missing, no dependency 
information available{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-5037) Fix for warning: Reporting configuration should be done in section, not in maven-site-plugin as reportPlugins parameter

2018-11-21 Thread Artem Ervits (JIRA)


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

Artem Ervits updated PHOENIX-5037:
--
Description: 
{code:java}
[WARNING] Some problems were encountered while building the effective model for 
org.apache.phoenix:phoenix-core:jar:5.1.0-HBase-2.0-SNAPSHOT
[WARNING] Reporting configuration should be done in  section, not in 
maven-site-plugin  as reportPlugins parameter. @ 
org.apache.phoenix:phoenix-core:[unknown-version], 
/Users/aervits/NetBeansProjects/APACHE-PHOENIX/phoenix/phoenix-core/pom.xml, 
line 65, column 23
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.phoenix:phoenix-flume:jar:5.1.0-HBase-2.0-SNAPSHOT
[WARNING] Reporting configuration should be done in  section, not in 
maven-site-plugin  as reportPlugins parameter.
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.phoenix:phoenix-kafka:jar:5.1.0-HBase-2.0-SNAPSHOT
[WARNING] Reporting configuration should be done in  section, not in 
maven-site-plugin  as reportPlugins parameter. @ 
org.apache.phoenix:phoenix-kafka:[unknown-version], 
/Users/aervits/NetBeansProjects/APACHE-PHOENIX/phoenix/phoenix-kafka/pom.xml, 
line 351, column 20
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.phoenix:phoenix-pig:jar:5.1.0-HBase-2.0-SNAPSHOT
[WARNING] Reporting configuration should be done in  section, not in 
maven-site-plugin  as reportPlugins parameter.
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.phoenix:phoenix-queryserver-client:jar:5.1.0-HBase-2.0-SNAPSHOT
[WARNING] Reporting configuration should be done in  section, not in 
maven-site-plugin  as reportPlugins parameter.
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.phoenix:phoenix-queryserver:jar:5.1.0-HBase-2.0-SNAPSHOT
[WARNING] Reporting configuration should be done in  section, not in 
maven-site-plugin  as reportPlugins parameter.
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.phoenix:phoenix-spark:jar:5.1.0-HBase-2.0-SNAPSHOT
[WARNING] Reporting configuration should be done in  section, not in 
maven-site-plugin  as reportPlugins parameter.
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.phoenix:phoenix-hive:jar:5.1.0-HBase-2.0-SNAPSHOT
[WARNING] Reporting configuration should be done in  section, not in 
maven-site-plugin  as reportPlugins parameter.
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.phoenix:phoenix-client:jar:5.1.0-HBase-2.0-SNAPSHOT
[WARNING] Reporting configuration should be done in  section, not in 
maven-site-plugin  as reportPlugins parameter. @ 
org.apache.phoenix:phoenix-client:[unknown-version], 
/Users/aervits/NetBeansProjects/APACHE-PHOENIX/phoenix/phoenix-client/pom.xml, 
line 52, column 24
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.phoenix:phoenix-server:jar:5.1.0-HBase-2.0-SNAPSHOT
[WARNING] Reporting configuration should be done in  section, not in 
maven-site-plugin  as reportPlugins parameter. @ 
org.apache.phoenix:phoenix-server:[unknown-version], 
/Users/aervits/NetBeansProjects/APACHE-PHOENIX/phoenix/phoenix-server/pom.xml, 
line 51, column 24
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.phoenix:phoenix-assembly:pom:5.1.0-HBase-2.0-SNAPSHOT
[WARNING] Reporting configuration should be done in  section, not in 
maven-site-plugin  as reportPlugins parameter.{code}

> Fix for warning: Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter
> ---
>
> Key: PHOENIX-5037
> URL: https://issues.apache.org/jira/browse/PHOENIX-5037
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Attachments: PHOENIX-5037-v01.patch
>
>
> {code:java}
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.phoenix:phoenix-core:jar:5.1.0-HBase-2.0-SNAPSHOT
> [WARNING] Reporting configuration should be done in  section, not 
> in maven-site-plugin  as reportPlugins parameter. @ 
> org.apache.phoenix:phoenix-core:[unknown-version], 
> /Users/aervits/NetBeansProjects/APACHE-PHOENIX/phoenix/phoenix-core/pom.xml, 
> line 65, column 23
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.phoenix:p

[jira] [Created] (PHOENIX-5038) Fix for warning: Multiple versions of scala detected in phoenix-spark

2018-11-21 Thread Artem Ervits (JIRA)
Artem Ervits created PHOENIX-5038:
-

 Summary: Fix for warning: Multiple versions of scala detected in 
phoenix-spark
 Key: PHOENIX-5038
 URL: https://issues.apache.org/jira/browse/PHOENIX-5038
 Project: Phoenix
  Issue Type: Improvement
 Environment: {code:java}
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
2018-06-17T14:33:14-04:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_172, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"{code}
Reporter: Artem Ervits
Assignee: Artem Ervits
 Attachments: PHOENIX-5038-v01.patch

{code:java}
[WARNING] Expected all dependencies to require Scala version: 2.11.8
[WARNING] org.apache.phoenix:phoenix-spark:5.1.0-HBase-2.0-SNAPSHOT requires 
scala version: 2.11.8
[WARNING] com.twitter:chill_2.11:0.8.4 requires scala version: 2.11.8
[WARNING] org.apache.spark:spark-core_2.11:2.3.0 requires scala version: 2.11.8
[WARNING] org.json4s:json4s-jackson_2.11:3.2.11 requires scala version: 2.11.0
[WARNING] Multiple versions of scala libraries detected!{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-5038) Fix for warning: Multiple versions of scala detected in phoenix-spark

2018-11-21 Thread Artem Ervits (JIRA)


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

Artem Ervits updated PHOENIX-5038:
--
Attachment: PHOENIX-5038-v01.patch

> Fix for warning: Multiple versions of scala detected in phoenix-spark
> -
>
> Key: PHOENIX-5038
> URL: https://issues.apache.org/jira/browse/PHOENIX-5038
> Project: Phoenix
>  Issue Type: Improvement
> Environment: {code:java}
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
> 2018-06-17T14:33:14-04:00)
> Maven home: /opt/apache-maven-3.5.4
> Java version: 1.8.0_172, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"{code}
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Attachments: PHOENIX-5038-v01.patch
>
>
> {code:java}
> [WARNING] Expected all dependencies to require Scala version: 2.11.8
> [WARNING] org.apache.phoenix:phoenix-spark:5.1.0-HBase-2.0-SNAPSHOT requires 
> scala version: 2.11.8
> [WARNING] com.twitter:chill_2.11:0.8.4 requires scala version: 2.11.8
> [WARNING] org.apache.spark:spark-core_2.11:2.3.0 requires scala version: 
> 2.11.8
> [WARNING] org.json4s:json4s-jackson_2.11:3.2.11 requires scala version: 2.11.0
> [WARNING] Multiple versions of scala libraries detected!{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-5037) Fix for warning: Reporting configuration should be done in section, not in maven-site-plugin as reportPlugins parameter

2018-11-21 Thread Artem Ervits (JIRA)


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

Artem Ervits updated PHOENIX-5037:
--
Attachment: PHOENIX-5037-v01.patch

> Fix for warning: Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter
> ---
>
> Key: PHOENIX-5037
> URL: https://issues.apache.org/jira/browse/PHOENIX-5037
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Attachments: PHOENIX-5037-v01.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (PHOENIX-5037) Fix for warning: Reporting configuration should be done in section, not in maven-site-plugin as reportPlugins parameter

2018-11-21 Thread Artem Ervits (JIRA)
Artem Ervits created PHOENIX-5037:
-

 Summary: Fix for warning: Reporting configuration should be done 
in  section, not in maven-site-plugin  as 
reportPlugins parameter
 Key: PHOENIX-5037
 URL: https://issues.apache.org/jira/browse/PHOENIX-5037
 Project: Phoenix
  Issue Type: Improvement
Reporter: Artem Ervits
Assignee: Artem Ervits






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-5036) Fix for warning: 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: junit:junit:jar -> duplicate declaration of version

2018-11-21 Thread Artem Ervits (JIRA)


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

Artem Ervits updated PHOENIX-5036:
--
Attachment: PHOENIX-5036-v01.patch

> Fix for warning: 
> 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be 
> unique: junit:junit:jar -> duplicate declaration of version
> ---
>
> Key: PHOENIX-5036
> URL: https://issues.apache.org/jira/browse/PHOENIX-5036
> Project: Phoenix
>  Issue Type: Improvement
> Environment: {code:java}
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
> 2018-06-17T14:33:14-04:00)
> Maven home: /opt/apache-maven-3.5.4
> Java version: 1.8.0_172, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"{code}
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Attachments: PHOENIX-5036-v01.patch
>
>
> this patch removes a build warning for
> {code:java}
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.phoenix:phoenix-pherf:jar:5.1.0-HBase-2.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: junit:junit:jar -> duplicate declaration of version (?) @ 
> org.apache.phoenix:phoenix-pherf:[unknown-version], 
> /Users/aervits/NetBeansProjects/APACHE-PHOENIX/phoenix/phoenix-pherf/pom.xml, 
> line 113, column 17
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (PHOENIX-5036) Fix for warning: 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: junit:junit:jar -> duplicate declaration of version

2018-11-21 Thread Artem Ervits (JIRA)
Artem Ervits created PHOENIX-5036:
-

 Summary: Fix for warning: 
'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: 
junit:junit:jar -> duplicate declaration of version
 Key: PHOENIX-5036
 URL: https://issues.apache.org/jira/browse/PHOENIX-5036
 Project: Phoenix
  Issue Type: Improvement
 Environment: {code:java}
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
2018-06-17T14:33:14-04:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_172, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"{code}
Reporter: Artem Ervits
Assignee: Artem Ervits


this patch removes a build warning for
{code:java}
[WARNING] Some problems were encountered while building the effective model for 
org.apache.phoenix:phoenix-pherf:jar:5.1.0-HBase-2.0-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
be unique: junit:junit:jar -> duplicate declaration of version (?) @ 
org.apache.phoenix:phoenix-pherf:[unknown-version], 
/Users/aervits/NetBeansProjects/APACHE-PHOENIX/phoenix/phoenix-pherf/pom.xml, 
line 113, column 17
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: When is best moment to release Phoenix 5.1

2018-11-21 Thread Jaanai Zhang
I mean, do we have any plan to release?  @Thomas @Josh :)



   Jaanai Zhang
   Best regards!



Jaanai  于2018年11月21日周三 下午4:38写道:

> I wonder if we had planned to release Phoenix 5.1.  as far as I am
> concerned Pheonix 5.1 is a stable version against 5.0,  so I and my
> co-workers decide to use this version for HBase 2.x on public cloud service.
>
> For you provide any information, I'd appreciate it.
>
> Thanks!
>


When is best moment to release Phoenix 5.1

2018-11-21 Thread Jaanai
I wonder if we had planned to release Phoenix 5.1.  as far as I am concerned 
Pheonix 5.1 is a stable version against 5.0,  so I and my co-workers decide to 
use this version for HBase 2.x on public cloud service.

For you provide any information, I'd appreciate it.

Thanks!