[jira] [Assigned] (PHOENIX-6730) Revert protobuf-java version to 2.5.0

2022-06-13 Thread Istvan Toth (Jira)


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

Istvan Toth reassigned PHOENIX-6730:


Assignee: Istvan Toth

> Revert protobuf-java version to 2.5.0
> -
>
> Key: PHOENIX-6730
> URL: https://issues.apache.org/jira/browse/PHOENIX-6730
> Project: Phoenix
>  Issue Type: Bug
>  Components: connectors, spark-connector
>Affects Versions: connectors-6.0.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>
> Recently a dependabot commit has landed on connectors that upgrades the 
> version of protobuf-java to 3.6.1
> I think that we should revert that.
> Part of the HBase 2 public API is that the public coprocessors use HBase 2 
> for communication.
> See [https://hbase.apache.org/book.html#cpeps]
> Using unshaded 3.6.1 in the connector breaks that contract.
> The shaded connector artifacts do not include protobuf-java, so the change is 
> effectively a NOOP for the shaded connector JAR.
> However, in case someone depends on the core artifact, the change in the 
> protobuf-java version may cause problems.
> [~rajeshbabu]  I know that you have added the explicit dependency for the 
> table metadata broadcast featrue, and that you've applied the dependabot PR, 
> but I think that we should stick to the protobuf pulled in by HBase.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Updated] (PHOENIX-6730) Revert protobuf-java version to 2.5.0

2022-06-13 Thread Istvan Toth (Jira)


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

Istvan Toth updated PHOENIX-6730:
-
Description: 
Recently a dependabot commit has landed on connectors that upgrades the version 
of protobuf-java to 3.6.1

I think that we should revert that.

Part of the HBase 2 public API is that the public coprocessors use HBase 2 for 
communication.
See [https://hbase.apache.org/book.html#cpeps]

Using unshaded 3.6.1 in the connector breaks that contract.

The shaded connector artifacts do not include protobuf-java, so the change is 
effectively a NOOP for the shaded connector JAR.

However, in case someone depends on the core artifact, the change in the 
protobuf-java version may cause problems.

[~rajeshbabu]  I know that you have added the explicit dependency for the table 
metadata broadcast featrue, and that you've applied the dependabot PR, but I 
think that we should stick to the protobuf pulled in by HBase.

  was:
Recently a dependabot commit has landed on connectors that upgrades the version 
of protobuf-java to 3.6.1

I think that we should revert that.

Part of the HBase 2 public API is that the public coprocessors use HBase 2 for 
communication.
See [https://hbase.apache.org/book.html#cpeps]

Using unshaded 3.6.1 in the connector breaks that contract.

The shaded connector artifacts do not include protobuf-java, so the change is 
effectively a NOOP. However, in case someone depends on the core artifact, the 
change in the protobuf-java version may cause problems.

[~rajeshbabu]  I know that you have added the explicit dependency for the table 
metadata broadcast featre, and that you've applied the dependabot PR, but 
I think that we should stick to the protobuf pulled in used by HBase.


> Revert protobuf-java version to 2.5.0
> -
>
> Key: PHOENIX-6730
> URL: https://issues.apache.org/jira/browse/PHOENIX-6730
> Project: Phoenix
>  Issue Type: Bug
>  Components: connectors, spark-connector
>Affects Versions: connectors-6.0.0
>Reporter: Istvan Toth
>Priority: Major
>
> Recently a dependabot commit has landed on connectors that upgrades the 
> version of protobuf-java to 3.6.1
> I think that we should revert that.
> Part of the HBase 2 public API is that the public coprocessors use HBase 2 
> for communication.
> See [https://hbase.apache.org/book.html#cpeps]
> Using unshaded 3.6.1 in the connector breaks that contract.
> The shaded connector artifacts do not include protobuf-java, so the change is 
> effectively a NOOP for the shaded connector JAR.
> However, in case someone depends on the core artifact, the change in the 
> protobuf-java version may cause problems.
> [~rajeshbabu]  I know that you have added the explicit dependency for the 
> table metadata broadcast featrue, and that you've applied the dependabot PR, 
> but I think that we should stick to the protobuf pulled in by HBase.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Created] (PHOENIX-6730) Revert protobuf-java version to 2.5.0

2022-06-13 Thread Istvan Toth (Jira)
Istvan Toth created PHOENIX-6730:


 Summary: Revert protobuf-java version to 2.5.0
 Key: PHOENIX-6730
 URL: https://issues.apache.org/jira/browse/PHOENIX-6730
 Project: Phoenix
  Issue Type: Bug
  Components: connectors, spark-connector
Affects Versions: connectors-6.0.0
Reporter: Istvan Toth


Recently a dependabot commit has landed on connectors that upgrades the version 
of protobuf-java to 3.6.1

I think that we should revert that.

Part of the HBase 2 public API is that the public coprocessors use HBase 2 for 
communication.
See [https://hbase.apache.org/book.html#cpeps]

Using unshaded 3.6.1 in the connector breaks that contract.

The shaded connector artifacts do not include protobuf-java, so the change is 
effectively a NOOP. However, in case someone depends on the core artifact, the 
change in the protobuf-java version may cause problems.

[~rajeshbabu]  I know that you have added the explicit dependency for the table 
metadata broadcast featre, and that you've applied the dependabot PR, but 
I think that we should stick to the protobuf pulled in used by HBase.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Resolved] (OMID-215) CI job on travis-ci.org has ceased working

2022-06-13 Thread Istvan Toth (Jira)


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

Istvan Toth resolved OMID-215.
--
Resolution: Fixed

It's working again.
Either someone has set up Omid on travis.com, or they have migrated the job 
from travis.org automagically.

> CI job on travis-ci.org has ceased working
> --
>
> Key: OMID-215
> URL: https://issues.apache.org/jira/browse/OMID-215
> Project: Phoenix Omid
>  Issue Type: Bug
>Reporter: Istvan Toth
>Priority: Major
>
> Travis-ci.org has been retired some time ago.
> We need to move the CI job to travis-ci.com, or another site, such as the ASF 
> infra.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[GitHub] [phoenix-omid] stoty commented on pull request #105: OMID-222 Remove HBase1 support and update HBase 2 version to 2.4

2022-06-13 Thread GitBox


stoty commented on PR #105:
URL: https://github.com/apache/phoenix-omid/pull/105#issuecomment-1154680247

   I had to pause working on 5.2 stuff due to @dayjob deadlines, but now I can 
resume work on it. (Bar the usual summer PTOs)
   Can you please re-review @gjacoby126  ?
   We can change/drop the enforcer rules in any way you see fit, it's not an 
essential part of the patch.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@phoenix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[jira] [Updated] (OMID-222) Remove HBase1 support and update HBase 2 version to 2.4

2022-06-13 Thread Istvan Toth (Jira)


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

Istvan Toth updated OMID-222:
-
Description: We don't support HBase 1 in upcoming Phoenix releases, and 
dropping the HBase 1 support removes a lot of complexity.

> Remove HBase1 support and update HBase 2 version to 2.4
> ---
>
> Key: OMID-222
> URL: https://issues.apache.org/jira/browse/OMID-222
> Project: Phoenix Omid
>  Issue Type: Improvement
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>
> We don't support HBase 1 in upcoming Phoenix releases, and dropping the HBase 
> 1 support removes a lot of complexity.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Assigned] (OMID-222) Remove HBase1 support and update HBase 2 version to 2.4

2022-06-13 Thread Istvan Toth (Jira)


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

Istvan Toth reassigned OMID-222:


Assignee: Istvan Toth

> Remove HBase1 support and update HBase 2 version to 2.4
> ---
>
> Key: OMID-222
> URL: https://issues.apache.org/jira/browse/OMID-222
> Project: Phoenix Omid
>  Issue Type: Improvement
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Created] (PHOENIX-6729) Enable staing website for phoenix

2022-06-13 Thread Kiran Kumar Maturi (Jira)
Kiran Kumar Maturi created PHOENIX-6729:
---

 Summary: Enable staing website for phoenix 
 Key: PHOENIX-6729
 URL: https://issues.apache.org/jira/browse/PHOENIX-6729
 Project: Phoenix
  Issue Type: Sub-task
Reporter: Kiran Kumar Maturi
Assignee: Kiran Kumar Maturi


Based on the instructions mentioned here: 
https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories
 . I am planning to test the changes by enabling this for the stage profile



--
This message was sent by Atlassian Jira
(v8.20.7#820007)