[jira] [Commented] (CASSANDRA-15248) Upgrade Guava to latest on master branch
[
https://issues.apache.org/jira/browse/CASSANDRA-15248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17425792#comment-17425792
]
Tomo Suzuki commented on CASSANDRA-15248:
-
Update
{quote}Cassandra-all:3.11's dependency is blocking Beam's Guava dependency
(BEAM-8911).
{quote}
Somehow Beam team managed to unblock the Guava version problem and Beam
declares a newer version of Guava. I'm not waiting for Cassandra's Guava
dependency now.
> Upgrade Guava to latest on master branch
>
>
> Key: CASSANDRA-15248
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15248
> Project: Cassandra
> Issue Type: Task
> Components: Build, Dependencies, Packaging
>Reporter: Abhijit Sarkar
>Priority: Normal
>
> Upgrade Guava to latest on master branch. See
> https://issues.apache.org/jira/browse/CASSANDRA-15245.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15453) Upgrade Guava to the same version as master on 3.11 branch
[
https://issues.apache.org/jira/browse/CASSANDRA-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056126#comment-17056126
]
Tomo Suzuki edited comment on CASSANDRA-15453 at 3/10/20, 7:11 PM:
---
I tried upgrading the Guava version to 28.0 in 3.11 branch
([suztomo/CASSANDRA-15453
917464e|https://github.com/suztomo/cassandra/commit/917464eb3fe666be8c00672b905741befea8a66e]).
The test failure revealed that cassandra-driver-core is not compatible with
the Guava version on {{NoSuchMethodError:
com.google.common.base.Objects.firstNonNull}}
([log|https://gist.github.com/suztomo/3af9dd38b82335b2f0c1813595c6e536]).
While cassandra-driver-core version 3.0.1-shaded has references to the removed
methods, 3.6.0-shaded does not have references.
{noformat}
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
/tmp/cassandra-driver-core-3.6.0-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
cassandra-driver-core-3.0.1-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
#67 = Utf8 firstNonNull
#69 = NameAndType#67:#68 //
firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
#70 = Methodref #66.#69 //
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
28: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
41: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
54: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
67: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
80: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
{noformat}
Attempt with cassandra-driver-core 3.6.0 failed
([log|https://gist.github.com/suztomo/20e16ad85b019b919f7b148eab652f30]).
Notables:
{noformat}
[junit-timeout] Testcase:
testGroupByWithRangeNamesQueryWithPaging(org.apache.cassandra.cql3.validation.operations.SelectGroupByTest):
Caused an ERROR
[junit-timeout] Can not use V5 protocol version. Newest supported protocol
version is: V4. For beta versions, use `allowBetaProtocolVersion` instead
[junit-timeout] Testcase:
testJavascriptUserType(org.apache.cassandra.cql3.validation.entities.UFPureScriptTest):
Caused an ERROR
[junit-timeout] execution of 'cql_test_keyspace.function_43[type_41]' failed:
java.lang.RuntimeException: java.lang.NoClassDefFoundError: Could not
initialize class com.datastax.driver.core.Metadata
[junit-timeout] Testcase:
testJavascriptUTCollections(org.apache.cassandra.cql3.validation.entities.UFPureScriptTest):
Caused an ERROR
[junit-timeout] execution of
'cql_test_keyspace.function_6[list>]' failed:
java.lang.RuntimeException: java.lang.ExceptionInInitializerError
[junit-timeout] Testcase:
testNoArgs(org.apache.cassandra.tools.CompactionStressTest): Caused an ERROR
[junit-timeout] java.lang.ClassNotFoundException:
org.apache.cassandra.stress.CompactionStress
[junit-timeout] java.lang.RuntimeException: java.lang.ClassNotFoundException:
org.apache.cassandra.stress.CompactionStress
[junit-timeout] Testcase:
testCustomIndexExpressionSyntax(org.apache.cassandra.index.CustomIndexTest):
FAILED
[junit-timeout] Query should be invalid but wrong error was thrown. Expected:
com.datastax.driver.core.exceptions.QueryValidationException, got:
java.lang.IllegalArgumentException. Query is: SELECT * FROM %s WHERE
expr(no_such_index, 'foo bar baz ') (values: [])
{noformat}
The older version used in trunk
- 3.6.0 on [Apr 10,
2018|https://github.com/apache/cassandra/commit/38b49904dd1c71fcb16abfbc205edfd6ce008b76]
- 3.4.0-SNAPSHOT on [Feb 1,
2018|https://github.com/apache/cassandra/blame/e8ff2f2b8ebb3990b99c81f839f6463bbff381f4/build.xml]
- 4.0.0-SNAPSHOT on [Nov 9,
2017|https://github.com/apache/cassandra/blame/59a4624d5f9b2c414b200e65b45beed9c5f4db52/build.xml]
- 3.0.1 on [May 23,
2016|https://github.com/apache/cassandra/blame/4de7a65ed9f3c97658a80dd64032ad6e82e9d58b/build.xml]
Attemtp with cassandra-driver-core 3.4.0 failed (). Notables:
{noformat}
[junit-timeout] Testcase: org.apache.cassandra.cql3.ViewTest: Caused an ERROR
[junit-timeout]
com.google.common.util.concurrent.MoreExecutors.sameThreadExecutor()Lcom/google/common/util/concurrent/ListeningExecutorService;
[junit-timeout] java.lang.NoSuchMethodError:
[jira] [Comment Edited] (CASSANDRA-15453) Upgrade Guava to the same version as master on 3.11 branch
[
https://issues.apache.org/jira/browse/CASSANDRA-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056126#comment-17056126
]
Tomo Suzuki edited comment on CASSANDRA-15453 at 3/10/20, 7:10 PM:
---
I tried upgrading the Guava version to 28.0 in 3.11 branch
([suztomo/CASSANDRA-15453
917464e|https://github.com/suztomo/cassandra/commit/917464eb3fe666be8c00672b905741befea8a66e]).
The test failure revealed that cassandra-driver-core is not compatible with
the Guava version on {{NoSuchMethodError:
com.google.common.base.Objects.firstNonNull}}
([log|https://gist.github.com/suztomo/3af9dd38b82335b2f0c1813595c6e536]).
While cassandra-driver-core version 3.0.1-shaded has references to the removed
methods, 3.6.0-shaded does not have references.
{noformat}
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
/tmp/cassandra-driver-core-3.6.0-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
cassandra-driver-core-3.0.1-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
#67 = Utf8 firstNonNull
#69 = NameAndType#67:#68 //
firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
#70 = Methodref #66.#69 //
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
28: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
41: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
54: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
67: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
80: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
{noformat}
Attempt with cassandra-driver-core 3.6.0 failed
([log|https://gist.github.com/suztomo/20e16ad85b019b919f7b148eab652f30]).
Notables:
{noformat}
[junit-timeout] Testcase:
testGroupByWithRangeNamesQueryWithPaging(org.apache.cassandra.cql3.validation.operations.SelectGroupByTest):
Caused an ERROR
[junit-timeout] Can not use V5 protocol version. Newest supported protocol
version is: V4. For beta versions, use `allowBetaProtocolVersion` instead
[junit-timeout] Testcase:
testJavascriptUserType(org.apache.cassandra.cql3.validation.entities.UFPureScriptTest):
Caused an ERROR
[junit-timeout] execution of 'cql_test_keyspace.function_43[type_41]' failed:
java.lang.RuntimeException: java.lang.NoClassDefFoundError: Could not
initialize class com.datastax.driver.core.Metadata
[junit-timeout] Testcase:
testJavascriptUTCollections(org.apache.cassandra.cql3.validation.entities.UFPureScriptTest):
Caused an ERROR
[junit-timeout] execution of
'cql_test_keyspace.function_6[list>]' failed:
java.lang.RuntimeException: java.lang.ExceptionInInitializerError
[junit-timeout] Testcase:
testNoArgs(org.apache.cassandra.tools.CompactionStressTest): Caused an ERROR
[junit-timeout] java.lang.ClassNotFoundException:
org.apache.cassandra.stress.CompactionStress
[junit-timeout] java.lang.RuntimeException: java.lang.ClassNotFoundException:
org.apache.cassandra.stress.CompactionStress
[junit-timeout] Testcase:
testCustomIndexExpressionSyntax(org.apache.cassandra.index.CustomIndexTest):
FAILED
[junit-timeout] Query should be invalid but wrong error was thrown. Expected:
com.datastax.driver.core.exceptions.QueryValidationException, got:
java.lang.IllegalArgumentException. Query is: SELECT * FROM %s WHERE
expr(no_such_index, 'foo bar baz ') (values: [])
{noformat}
The older version used in trunk
- 3.6.0 on [Apr 10,
2018|https://github.com/apache/cassandra/commit/38b49904dd1c71fcb16abfbc205edfd6ce008b76]
- 3.4.0-SNAPSHOT on [Feb 1,
2018|https://github.com/apache/cassandra/blame/e8ff2f2b8ebb3990b99c81f839f6463bbff381f4/build.xml]
- 4.0.0-SNAPSHOT on [Nov 9,
2017|https://github.com/apache/cassandra/blame/59a4624d5f9b2c414b200e65b45beed9c5f4db52/build.xml]
- 3.0.1 on [May 23,
2016|https://github.com/apache/cassandra/blame/4de7a65ed9f3c97658a80dd64032ad6e82e9d58b/build.xml]
Attemtp with cassandra-driver-core 3.4.0 failed (). Notables:
{noformat}
[junit-timeout] Testcase: org.apache.cassandra.cql3.ViewTest: Caused an ERROR
[junit-timeout]
com.google.common.util.concurrent.MoreExecutors.sameThreadExecutor()Lcom/google/common/util/concurrent/ListeningExecutorService;
[junit-timeout] java.lang.NoSuchMethodError:
[jira] [Comment Edited] (CASSANDRA-15453) Upgrade Guava to the same version as master on 3.11 branch
[
https://issues.apache.org/jira/browse/CASSANDRA-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056126#comment-17056126
]
Tomo Suzuki edited comment on CASSANDRA-15453 at 3/10/20, 7:01 PM:
---
I tried upgrading the Guava version to 28.0 in 3.11 branch
([suztomo/CASSANDRA-15453
917464e|https://github.com/suztomo/cassandra/commit/917464eb3fe666be8c00672b905741befea8a66e]).
The test failure revealed that cassandra-driver-core is not compatible with
the Guava version on {{NoSuchMethodError:
com.google.common.base.Objects.firstNonNull}}
([log|https://gist.github.com/suztomo/3af9dd38b82335b2f0c1813595c6e536]).
While cassandra-driver-core version 3.0.1-shaded has references to the removed
methods, 3.6.0-shaded does not have references.
{noformat}
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
/tmp/cassandra-driver-core-3.6.0-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
cassandra-driver-core-3.0.1-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
#67 = Utf8 firstNonNull
#69 = NameAndType#67:#68 //
firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
#70 = Methodref #66.#69 //
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
28: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
41: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
54: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
67: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
80: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
{noformat}
Attempt with cassandra-driver-core 3.6.0 failed
([log|https://gist.github.com/suztomo/20e16ad85b019b919f7b148eab652f30]).
Notables:
{noformat}
[junit-timeout] Testcase:
testGroupByWithRangeNamesQueryWithPaging(org.apache.cassandra.cql3.validation.operations.SelectGroupByTest):
Caused an ERROR
[junit-timeout] Can not use V5 protocol version. Newest supported protocol
version is: V4. For beta versions, use `allowBetaProtocolVersion` instead
[junit-timeout] Testcase:
testJavascriptUserType(org.apache.cassandra.cql3.validation.entities.UFPureScriptTest):
Caused an ERROR
[junit-timeout] execution of 'cql_test_keyspace.function_43[type_41]' failed:
java.lang.RuntimeException: java.lang.NoClassDefFoundError: Could not
initialize class com.datastax.driver.core.Metadata
[junit-timeout] Testcase:
testJavascriptUTCollections(org.apache.cassandra.cql3.validation.entities.UFPureScriptTest):
Caused an ERROR
[junit-timeout] execution of
'cql_test_keyspace.function_6[list>]' failed:
java.lang.RuntimeException: java.lang.ExceptionInInitializerError
[junit-timeout] Testcase:
testNoArgs(org.apache.cassandra.tools.CompactionStressTest): Caused an ERROR
[junit-timeout] java.lang.ClassNotFoundException:
org.apache.cassandra.stress.CompactionStress
[junit-timeout] java.lang.RuntimeException: java.lang.ClassNotFoundException:
org.apache.cassandra.stress.CompactionStress
[junit-timeout] Testcase:
testCustomIndexExpressionSyntax(org.apache.cassandra.index.CustomIndexTest):
FAILED
[junit-timeout] Query should be invalid but wrong error was thrown. Expected:
com.datastax.driver.core.exceptions.QueryValidationException, got:
java.lang.IllegalArgumentException. Query is: SELECT * FROM %s WHERE
expr(no_such_index, 'foo bar baz ') (values: [])
{noformat}
The older version used in trunk
- 3.6.0 on [Apr 10,
2018|https://github.com/apache/cassandra/commit/38b49904dd1c71fcb16abfbc205edfd6ce008b76]
- 3.4.0-SNAPSHOT on [Feb 1,
2018|https://github.com/apache/cassandra/blame/e8ff2f2b8ebb3990b99c81f839f6463bbff381f4/build.xml]
- 4.0.0-SNAPSHOT on [Nov 9,
2017|https://github.com/apache/cassandra/blame/59a4624d5f9b2c414b200e65b45beed9c5f4db52/build.xml]
- 3.0.1 on [May 23,
2016|https://github.com/apache/cassandra/blame/4de7a65ed9f3c97658a80dd64032ad6e82e9d58b/build.xml]
was (Author: suztomo):
I tried upgrading the Guava version to 28.0 in 3.11 branch
([suztomo/CASSANDRA-15453
917464e|https://github.com/suztomo/cassandra/commit/917464eb3fe666be8c00672b905741befea8a66e]).
The test failure revealed that cassandra-driver-core is not compatible with
the Guava version on {{NoSuchMethodError:
com.google.common.base.Objects.firstNonNull}}
[jira] [Comment Edited] (CASSANDRA-15453) Upgrade Guava to the same version as master on 3.11 branch
[
https://issues.apache.org/jira/browse/CASSANDRA-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056126#comment-17056126
]
Tomo Suzuki edited comment on CASSANDRA-15453 at 3/10/20, 5:26 PM:
---
I tried upgrading the Guava version to 28.0 in 3.11 branch
([suztomo/CASSANDRA-15453
917464e|https://github.com/suztomo/cassandra/commit/917464eb3fe666be8c00672b905741befea8a66e]).
The test failure revealed that cassandra-driver-core is not compatible with
the Guava version on {{NoSuchMethodError:
com.google.common.base.Objects.firstNonNull}}
([log|https://gist.github.com/suztomo/3af9dd38b82335b2f0c1813595c6e536]).
While cassandra-driver-core version 3.0.1-shaded has references to the removed
methods, 3.6.0-shaded does not have references.
{noformat}
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
/tmp/cassandra-driver-core-3.6.0-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
cassandra-driver-core-3.0.1-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
#67 = Utf8 firstNonNull
#69 = NameAndType#67:#68 //
firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
#70 = Methodref #66.#69 //
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
28: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
41: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
54: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
67: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
80: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
{noformat}
Attempt with cassandra-driver-core 3.6.0 failed
([log|https://gist.github.com/suztomo/20e16ad85b019b919f7b148eab652f30]).
Notables:
{noformat}
[junit-timeout] Testcase:
testGroupByWithRangeNamesQueryWithPaging(org.apache.cassandra.cql3.validation.operations.SelectGroupByTest):
Caused an ERROR
[junit-timeout] Can not use V5 protocol version. Newest supported protocol
version is: V4. For beta versions, use `allowBetaProtocolVersion` instead
[junit-timeout] Testcase:
testJavascriptUserType(org.apache.cassandra.cql3.validation.entities.UFPureScriptTest):
Caused an ERROR
[junit-timeout] execution of 'cql_test_keyspace.function_43[type_41]' failed:
java.lang.RuntimeException: java.lang.NoClassDefFoundError: Could not
initialize class com.datastax.driver.core.Metadata
[junit-timeout] Testcase:
testJavascriptUTCollections(org.apache.cassandra.cql3.validation.entities.UFPureScriptTest):
Caused an ERROR
[junit-timeout] execution of
'cql_test_keyspace.function_6[list>]' failed:
java.lang.RuntimeException: java.lang.ExceptionInInitializerError
[junit-timeout] Testcase:
testNoArgs(org.apache.cassandra.tools.CompactionStressTest): Caused an ERROR
[junit-timeout] java.lang.ClassNotFoundException:
org.apache.cassandra.stress.CompactionStress
[junit-timeout] java.lang.RuntimeException: java.lang.ClassNotFoundException:
org.apache.cassandra.stress.CompactionStress
[junit-timeout] Testcase:
testCustomIndexExpressionSyntax(org.apache.cassandra.index.CustomIndexTest):
FAILED
[junit-timeout] Query should be invalid but wrong error was thrown. Expected:
com.datastax.driver.core.exceptions.QueryValidationException, got:
java.lang.IllegalArgumentException. Query is: SELECT * FROM %s WHERE
expr(no_such_index, 'foo bar baz ') (values: [])
{noformat}
was (Author: suztomo):
I tried upgrading the Guava version to 28.0 in 3.11 branch
([suztomo/CASSANDRA-15453
917464e|https://github.com/suztomo/cassandra/commit/917464eb3fe666be8c00672b905741befea8a66e]).
The test failure revealed that cassandra-driver-core is not compatible with
the Guava version on {{NoSuchMethodError:
com.google.common.base.Objects.firstNonNull}}
([log|https://gist.github.com/suztomo/3af9dd38b82335b2f0c1813595c6e536]).
While cassandra-driver-core version 3.0.1-shaded has references to the removed
methods, 3.6.0-shaded does not have references.
{noformat}
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
/tmp/cassandra-driver-core-3.6.0-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
cassandra-driver-core-3.0.1-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder'
[jira] [Comment Edited] (CASSANDRA-15453) Upgrade Guava to the same version as master on 3.11 branch
[
https://issues.apache.org/jira/browse/CASSANDRA-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056126#comment-17056126
]
Tomo Suzuki edited comment on CASSANDRA-15453 at 3/10/20, 5:25 PM:
---
I tried upgrading the Guava version to 28.0 in 3.11 branch
([suztomo/CASSANDRA-15453
917464e|https://github.com/suztomo/cassandra/commit/917464eb3fe666be8c00672b905741befea8a66e]).
The test failure revealed that cassandra-driver-core is not compatible with
the Guava version on {{NoSuchMethodError:
com.google.common.base.Objects.firstNonNull}}
([log|https://gist.github.com/suztomo/3af9dd38b82335b2f0c1813595c6e536]).
While cassandra-driver-core version 3.0.1-shaded has references to the removed
methods, 3.6.0-shaded does not have references.
{noformat}
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
/tmp/cassandra-driver-core-3.6.0-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
cassandra-driver-core-3.0.1-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
#67 = Utf8 firstNonNull
#69 = NameAndType#67:#68 //
firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
#70 = Methodref #66.#69 //
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
28: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
41: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
54: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
67: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
80: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
{noformat}
Attempt with cassandra-driver-core 3.6.0 failed
([log|https://gist.github.com/suztomo/20e16ad85b019b919f7b148eab652f30]):
{noformat}
[junit-timeout] Testcase:
testGroupByWithRangeNamesQueryWithPaging(org.apache.cassandra.cql3.validation.operations.SelectGroupByTest):
Caused an ERROR
[junit-timeout] Can not use V5 protocol version. Newest supported protocol
version is: V4. For beta versions, use `allowBetaProtocolVersion` instead
[junit-timeout] Testcase:
testJavascriptUserType(org.apache.cassandra.cql3.validation.entities.UFPureScriptTest):
Caused an ERROR
[junit-timeout] execution of 'cql_test_keyspace.function_43[type_41]' failed:
java.lang.RuntimeException: java.lang.NoClassDefFoundError: Could not
initialize class com.datastax.driver.core.Metadata
[junit-timeout] Testcase:
testJavascriptUTCollections(org.apache.cassandra.cql3.validation.entities.UFPureScriptTest):
Caused an ERROR
[junit-timeout] execution of
'cql_test_keyspace.function_6[list>]' failed:
java.lang.RuntimeException: java.lang.ExceptionInInitializerError
[junit-timeout] Testcase:
testNoArgs(org.apache.cassandra.tools.CompactionStressTest): Caused an ERROR
[junit-timeout] java.lang.ClassNotFoundException:
org.apache.cassandra.stress.CompactionStress
[junit-timeout] java.lang.RuntimeException: java.lang.ClassNotFoundException:
org.apache.cassandra.stress.CompactionStress
[junit-timeout] Testcase:
testCustomIndexExpressionSyntax(org.apache.cassandra.index.CustomIndexTest):
FAILED
[junit-timeout] Query should be invalid but wrong error was thrown. Expected:
com.datastax.driver.core.exceptions.QueryValidationException, got:
java.lang.IllegalArgumentException. Query is: SELECT * FROM %s WHERE
expr(no_such_index, 'foo bar baz ') (values: [])
{noformat}
was (Author: suztomo):
I tried upgrading the Guava version to 28.0 in 3.11 branch
([suztomo/CASSANDRA-15453
917464e|https://github.com/suztomo/cassandra/commit/917464eb3fe666be8c00672b905741befea8a66e]).
The test failure revealed that cassandra-driver-core is not compatible with
the Guava version on {{NoSuchMethodError:
com.google.common.base.Objects.firstNonNull}}
([log|https://gist.github.com/suztomo/3af9dd38b82335b2f0c1813595c6e536]).
While cassandra-driver-core version 3.0.1-shaded has references to the removed
methods, 3.6.0-shaded does not have references.
{noformat}
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
/tmp/cassandra-driver-core-3.6.0-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
cassandra-driver-core-3.0.1-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep
[jira] [Comment Edited] (CASSANDRA-15453) Upgrade Guava to the same version as master on 3.11 branch
[
https://issues.apache.org/jira/browse/CASSANDRA-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056126#comment-17056126
]
Tomo Suzuki edited comment on CASSANDRA-15453 at 3/10/20, 4:58 PM:
---
I tried upgrading the Guava version to 28.0 in 3.11 branch
([suztomo/CASSANDRA-15453
917464e|https://github.com/suztomo/cassandra/commit/917464eb3fe666be8c00672b905741befea8a66e]).
The test failure revealed that cassandra-driver-core is not compatible with
the Guava version on {{NoSuchMethodError:
com.google.common.base.Objects.firstNonNull}}
([log|https://gist.github.com/suztomo/3af9dd38b82335b2f0c1813595c6e536]).
While cassandra-driver-core version 3.0.1-shaded has references to the removed
methods, 3.6.0-shaded does not have references.
{noformat}
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
/tmp/cassandra-driver-core-3.6.0-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
cassandra-driver-core-3.0.1-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
#67 = Utf8 firstNonNull
#69 = NameAndType#67:#68 //
firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
#70 = Methodref #66.#69 //
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
28: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
41: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
54: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
67: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
80: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
{noformat}
was (Author: suztomo):
I tried upgrading the Guava version to 28.0 in 3.11 branch
([suztomo/CASSANDRA-15453|https://github.com/suztomo/cassandra/tree/CASSANDRA-15453]).
The test failure revealed that cassandra-driver-core is not compatible with
the Guava version on {{NoSuchMethodError:
com.google.common.base.Objects.firstNonNull}}
([log|https://gist.github.com/suztomo/3af9dd38b82335b2f0c1813595c6e536]).
While cassandra-driver-core version 3.0.1-shaded has references to the removed
methods, 3.6.0-shaded does not have references.
{noformat}
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
/tmp/cassandra-driver-core-3.6.0-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
cassandra-driver-core-3.0.1-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
#67 = Utf8 firstNonNull
#69 = NameAndType#67:#68 //
firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
#70 = Methodref #66.#69 //
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
28: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
41: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
54: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
67: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
80: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
{noformat}
> Upgrade Guava to the same version as master on 3.11 branch
> --
>
> Key: CASSANDRA-15453
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15453
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies
>Reporter: Tomo Suzuki
>Priority: Normal
>
> Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
> h3. Background
> I'm trying to upgrade Apache Beam's dependencies to latest versions. Apache
> Beam depends on Cassandra 3 ({{org.apache.cassandra:cassandra-all:3.11.3}}).
> Cassandra 3 touches on Guava's
[jira] [Comment Edited] (CASSANDRA-15453) Upgrade Guava to the same version as master on 3.11 branch
[
https://issues.apache.org/jira/browse/CASSANDRA-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056126#comment-17056126
]
Tomo Suzuki edited comment on CASSANDRA-15453 at 3/10/20, 4:53 PM:
---
I tried upgrading the Guava version to 28.0 in 3.11 branch
([suztomo/CASSANDRA-15453|https://github.com/suztomo/cassandra/tree/CASSANDRA-15453]).
The test failure revealed that cassandra-driver-core is not compatible with
the Guava version on {{NoSuchMethodError:
com.google.common.base.Objects.firstNonNull}}
([log|https://gist.github.com/suztomo/3af9dd38b82335b2f0c1813595c6e536]).
While cassandra-driver-core version 3.0.1-shaded has references to the removed
methods, 3.6.0-shaded does not have references.
{noformat}
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
/tmp/cassandra-driver-core-3.6.0-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
suztomo@suxtomo24:~/cassandra/lib$ javap -v -cp
cassandra-driver-core-3.0.1-shaded.jar
'com.datastax.driver.core.policies.Policies$Builder' |grep firstNonNull
#67 = Utf8 firstNonNull
#69 = NameAndType#67:#68 //
firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
#70 = Methodref #66.#69 //
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
28: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
41: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
54: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
67: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
80: invokestatic #70 // Method
com/google/common/base/Objects.firstNonNull:(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
{noformat}
was (Author: suztomo):
I tried upgrading the Guava version to 28.0 in 3.11 branch
([suztomo/CASSANDRA-15453|https://github.com/suztomo/cassandra/tree/CASSANDRA-15453]).
The test failure revealed that cassandra-driver-core is not compatible with
the Guava version on {{NoSuchMethodError:
com.google.common.base.Objects.firstNonNull}}
([log|https://gist.github.com/suztomo/3af9dd38b82335b2f0c1813595c6e536]).
> Upgrade Guava to the same version as master on 3.11 branch
> --
>
> Key: CASSANDRA-15453
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15453
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies
>Reporter: Tomo Suzuki
>Priority: Normal
>
> Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
> h3. Background
> I'm trying to upgrade Apache Beam's dependencies to latest versions. Apache
> Beam depends on Cassandra 3 ({{org.apache.cassandra:cassandra-all:3.11.3}}).
> Cassandra 3 touches on Guava's old fields (and potentially methods), such as
> CharMatcher.DIGIT, are blocking Apache Beam's Guava dependency upgrade
> (BEAM-8911); the field is removed in Guava 26.0. Because of this, Apache
> Beam's Guava dependency must be lower than version 26.0.
> I see the latest cassandra-all release on 3.X is 3.11.5, which still relies
> on Guava 18. This version does not have {{CharMatcher.digit()}}, the
> replacement of old {{CharMatcher.DIGIT}}. To get rid of {{CharMatcher.DIGIT}}
> and thus let Apache Beam to use Guava 26 and higher, we need to upgrade
> Cassandra3's Guava version.
> h4. Test failure Beam's HadoopFormatIOCassandraTest
> Apache Beam's {{:sdks:java:io:hadoop-format}} has
> {{HadoopFormatIOCassandraTest}} that failed when I tried to upgrade Guava
> version to 26:
> https://github.com/GoogleCloudPlatform/cloud-opensource-java/issues/1028#issuecomment-557680928
> .
> h3. How about waiting for Cassandra version 4(-alpha)?
> I thought about Cassandra "4", which has a recent version of Guava. However,
> I believe quite a few Cassandra/Beam users will keep using Casandra 3 for
> several years. I want such users to be able to use the higher version of
> Guava.
> h3. Shading?
> Shading makes build process complex. When things go wrong due to this, it's
> hard to debug ([JLBP18|https://jlbp.dev/JLBP-18.html]).
> h3. CASSANDRA-15248 "Upgrade Guava to latest on master branch",
> I found CASSANDRA-15248 "Upgrade Guava to latest on master branch", but this
> did not go into 3.11 branch. Can we backport this Guava version upgrade
> (CASSANDRA-15248) into 3.11 branch?
--
[jira] [Commented] (CASSANDRA-15453) Upgrade Guava to the same version as master on 3.11 branch
[
https://issues.apache.org/jira/browse/CASSANDRA-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056126#comment-17056126
]
Tomo Suzuki commented on CASSANDRA-15453:
-
I tried upgrading the Guava version to 28.0 in 3.11 branch
([suztomo/CASSANDRA-15453|https://github.com/suztomo/cassandra/tree/CASSANDRA-15453]).
The test failure revealed that cassandra-driver-core is not compatible with
the Guava version on {{NoSuchMethodError:
com.google.common.base.Objects.firstNonNull}}
([log|https://gist.github.com/suztomo/3af9dd38b82335b2f0c1813595c6e536]).
> Upgrade Guava to the same version as master on 3.11 branch
> --
>
> Key: CASSANDRA-15453
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15453
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies
>Reporter: Tomo Suzuki
>Priority: Normal
>
> Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
> h3. Background
> I'm trying to upgrade Apache Beam's dependencies to latest versions. Apache
> Beam depends on Cassandra 3 ({{org.apache.cassandra:cassandra-all:3.11.3}}).
> Cassandra 3 touches on Guava's old fields (and potentially methods), such as
> CharMatcher.DIGIT, are blocking Apache Beam's Guava dependency upgrade
> (BEAM-8911); the field is removed in Guava 26.0. Because of this, Apache
> Beam's Guava dependency must be lower than version 26.0.
> I see the latest cassandra-all release on 3.X is 3.11.5, which still relies
> on Guava 18. This version does not have {{CharMatcher.digit()}}, the
> replacement of old {{CharMatcher.DIGIT}}. To get rid of {{CharMatcher.DIGIT}}
> and thus let Apache Beam to use Guava 26 and higher, we need to upgrade
> Cassandra3's Guava version.
> h4. Test failure Beam's HadoopFormatIOCassandraTest
> Apache Beam's {{:sdks:java:io:hadoop-format}} has
> {{HadoopFormatIOCassandraTest}} that failed when I tried to upgrade Guava
> version to 26:
> https://github.com/GoogleCloudPlatform/cloud-opensource-java/issues/1028#issuecomment-557680928
> .
> h3. How about waiting for Cassandra version 4(-alpha)?
> I thought about Cassandra "4", which has a recent version of Guava. However,
> I believe quite a few Cassandra/Beam users will keep using Casandra 3 for
> several years. I want such users to be able to use the higher version of
> Guava.
> h3. Shading?
> Shading makes build process complex. When things go wrong due to this, it's
> hard to debug ([JLBP18|https://jlbp.dev/JLBP-18.html]).
> h3. CASSANDRA-15248 "Upgrade Guava to latest on master branch",
> I found CASSANDRA-15248 "Upgrade Guava to latest on master branch", but this
> did not go into 3.11 branch. Can we backport this Guava version upgrade
> (CASSANDRA-15248) into 3.11 branch?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-12995) update hppc dependency to 0.7
[ https://issues.apache.org/jira/browse/CASSANDRA-12995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023158#comment-17023158 ] Tomo Suzuki commented on CASSANDRA-12995: - Thanks. Looking forward to 4.0 release. > update hppc dependency to 0.7 > - > > Key: CASSANDRA-12995 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12995 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies, Packaging >Reporter: Tomas Repik >Priority: Normal > Labels: easyfix > Fix For: 4.0 > > Attachments: cassandra-3.11.0-hppc.patch > > > Cassandra 3.11.0 is about to be included in Fedora. There are some tweaks to > the sources we need to do in order to successfully build it. Cassandra > depends on hppc 0.5.4, but In Fedora we have the newer version 0.7.1 Upstream > released even newer version 0.7.2. I attached a patch updating cassandra > sources to depend on the 0.7.1 hppc sources. It should be also compatible > with the newest upstream version. The only actual changes are the removal of > Open infix in class names. The issue was discussed in here: > https://bugzilla.redhat.com/show_bug.cgi?id=1340876 Please consider updating. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-12995) update hppc dependency to 0.7
[ https://issues.apache.org/jira/browse/CASSANDRA-12995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022429#comment-17022429 ] Tomo Suzuki commented on CASSANDRA-12995: - This ticket is asking for the upgrade for the sake of compatibility with other libraries, not security or vulnerability. As Cassandra 3.X keeps using classes and methods that are not available in newer versions of popular libraries (such as hpcc and Guava), Cassandra 3.X users have hard time to run it with other libraries and frameworks, as well as the developers who would like to integrate their products with Cassandra. > update hppc dependency to 0.7 > - > > Key: CASSANDRA-12995 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12995 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies, Packaging >Reporter: Tomas Repik >Priority: Normal > Labels: easyfix > Fix For: 4.0 > > Attachments: cassandra-3.11.0-hppc.patch > > > Cassandra 3.11.0 is about to be included in Fedora. There are some tweaks to > the sources we need to do in order to successfully build it. Cassandra > depends on hppc 0.5.4, but In Fedora we have the newer version 0.7.1 Upstream > released even newer version 0.7.2. I attached a patch updating cassandra > sources to depend on the 0.7.1 hppc sources. It should be also compatible > with the newest upstream version. The only actual changes are the removal of > Open infix in class names. The issue was discussed in here: > https://bugzilla.redhat.com/show_bug.cgi?id=1340876 Please consider updating. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-12995) update hppc dependency to 0.7
[
https://issues.apache.org/jira/browse/CASSANDRA-12995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17016208#comment-17016208
]
Tomo Suzuki commented on CASSANDRA-12995:
-
[~brandon.williams] I don't see the ticket or associated PR
[cassandra-dtest#55|https://github.com/apache/cassandra-dtest/pull/55] touched
{{com.carrotsearch:hppc dependency}} dependency.
And I still see the below in
https://github.com/apache/cassandra/blob/82dc720/build.xml#L577
{noformat}
{noformat}
> update hppc dependency to 0.7
> -
>
> Key: CASSANDRA-12995
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12995
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies, Packaging
>Reporter: Tomas Repik
>Priority: Normal
> Labels: easyfix
> Fix For: 4.0
>
> Attachments: cassandra-3.11.0-hppc.patch
>
>
> Cassandra 3.11.0 is about to be included in Fedora. There are some tweaks to
> the sources we need to do in order to successfully build it. Cassandra
> depends on hppc 0.5.4, but In Fedora we have the newer version 0.7.1 Upstream
> released even newer version 0.7.2. I attached a patch updating cassandra
> sources to depend on the 0.7.1 hppc sources. It should be also compatible
> with the newest upstream version. The only actual changes are the removal of
> Open infix in class names. The issue was discussed in here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1340876 Please consider updating.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15455) Upgrade com.carrotsearch:hppc dependency
[ https://issues.apache.org/jira/browse/CASSANDRA-15455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomo Suzuki updated CASSANDRA-15455: Resolution: Duplicate Status: Resolved (was: Triage Needed) [~gus] Thanks. I'm closing this ticket. > Upgrade com.carrotsearch:hppc dependency > > > Key: CASSANDRA-15455 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15455 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Tomo Suzuki >Priority: Normal > > Upgrade com.carrotsearch:hppc dependency. > Current version 0.5 causes diamond dependency conflict with other dependency > (via Elasticsearch) in Apache Beam. > https://gist.github.com/suztomo/6fe16f6bda526aab97e879feac70309d -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Issue Comment Deleted] (CASSANDRA-15455) Upgrade com.carrotsearch:hppc dependency
[
https://issues.apache.org/jira/browse/CASSANDRA-15455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomo Suzuki updated CASSANDRA-15455:
Comment: was deleted
(was: [~brandon.williams] I don't see the ticket or associated PR
[cassandra-dtest#55|https://github.com/apache/cassandra-dtest/pull/55] touched
{{com.carrotsearch:hppc dependency}} dependency.
And I still see the below in
https://github.com/apache/cassandra/blob/82dc720/build.xml#L577
{noformat}
{noformat}
)
> Upgrade com.carrotsearch:hppc dependency
>
>
> Key: CASSANDRA-15455
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15455
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies
>Reporter: Tomo Suzuki
>Priority: Normal
>
> Upgrade com.carrotsearch:hppc dependency.
> Current version 0.5 causes diamond dependency conflict with other dependency
> (via Elasticsearch) in Apache Beam.
> https://gist.github.com/suztomo/6fe16f6bda526aab97e879feac70309d
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15455) Upgrade com.carrotsearch:hppc dependency
[
https://issues.apache.org/jira/browse/CASSANDRA-15455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17016205#comment-17016205
]
Tomo Suzuki commented on CASSANDRA-15455:
-
[~brandon.williams] I don't see the ticket or associated PR
[cassandra-dtest#55|https://github.com/apache/cassandra-dtest/pull/55] touched
{{com.carrotsearch:hppc dependency}} dependency.
And I still see the below in
https://github.com/apache/cassandra/blob/82dc720/build.xml#L577
{noformat}
{noformat}
> Upgrade com.carrotsearch:hppc dependency
>
>
> Key: CASSANDRA-15455
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15455
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies
>Reporter: Tomo Suzuki
>Priority: Normal
>
> Upgrade com.carrotsearch:hppc dependency.
> Current version 0.5 causes diamond dependency conflict with other dependency
> (via Elasticsearch) in Apache Beam.
> https://gist.github.com/suztomo/6fe16f6bda526aab97e879feac70309d
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15453) Upgrade Guava to the same version as master on 3.11 branch
[
https://issues.apache.org/jira/browse/CASSANDRA-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16999277#comment-16999277
]
Tomo Suzuki commented on CASSANDRA-15453:
-
[~benedict] Thank you for response. Russell said:
{quote}The hadoop formats should be compatible with any Cassandra version
regardless of which Cassandra-all you include since they communicate with
the driver under the hood and not Cassandra internal libraries. This means
you should feel free to use Cassandra 4 in your integration without fear of
losing backwards compatibility. In fact it should be able to speak to
Cassandra 2.x as well.{quote}
So I'll wait for Cassandra 4 and if that does not work, I'll revisit this
ticket.
> Upgrade Guava to the same version as master on 3.11 branch
> --
>
> Key: CASSANDRA-15453
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15453
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies
>Reporter: Tomo Suzuki
>Priority: Normal
>
> Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
> h3. Background
> I'm trying to upgrade Apache Beam's dependencies to latest versions. Apache
> Beam depends on Cassandra 3 ({{org.apache.cassandra:cassandra-all:3.11.3}}).
> Cassandra 3 touches on Guava's old fields (and potentially methods), such as
> CharMatcher.DIGIT, are blocking Apache Beam's Guava dependency upgrade
> (BEAM-8911); the field is removed in Guava 26.0. Because of this, Apache
> Beam's Guava dependency must be lower than version 26.0.
> I see the latest cassandra-all release on 3.X is 3.11.5, which still relies
> on Guava 18. This version does not have {{CharMatcher.digit()}}, the
> replacement of old {{CharMatcher.DIGIT}}. To get rid of {{CharMatcher.DIGIT}}
> and thus let Apache Beam to use Guava 26 and higher, we need to upgrade
> Cassandra3's Guava version.
> h4. Test failure Beam's HadoopFormatIOCassandraTest
> Apache Beam's {{:sdks:java:io:hadoop-format}} has
> {{HadoopFormatIOCassandraTest}} that failed when I tried to upgrade Guava
> version to 26:
> https://github.com/GoogleCloudPlatform/cloud-opensource-java/issues/1028#issuecomment-557680928
> .
> h3. How about waiting for Cassandra version 4(-alpha)?
> I thought about Cassandra "4", which has a recent version of Guava. However,
> I believe quite a few Cassandra/Beam users will keep using Casandra 3 for
> several years. I want such users to be able to use the higher version of
> Guava.
> h3. Shading?
> Shading makes build process complex. When things go wrong due to this, it's
> hard to debug ([JLBP18|https://jlbp.dev/JLBP-18.html]).
> h3. CASSANDRA-15248 "Upgrade Guava to latest on master branch",
> I found CASSANDRA-15248 "Upgrade Guava to latest on master branch", but this
> did not go into 3.11 branch. Can we backport this Guava version upgrade
> (CASSANDRA-15248) into 3.11 branch?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15455) Upgrade com.carrotsearch:hppc dependency
Tomo Suzuki created CASSANDRA-15455: --- Summary: Upgrade com.carrotsearch:hppc dependency Key: CASSANDRA-15455 URL: https://issues.apache.org/jira/browse/CASSANDRA-15455 Project: Cassandra Issue Type: Improvement Components: Dependencies Reporter: Tomo Suzuki Upgrade com.carrotsearch:hppc dependency. Current version 0.5 causes diamond dependency conflict with other dependency (via Elasticsearch) in Apache Beam. https://gist.github.com/suztomo/6fe16f6bda526aab97e879feac70309d -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15453) Upgrade Guava to the same version as master on 3.11 branch
[
https://issues.apache.org/jira/browse/CASSANDRA-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomo Suzuki updated CASSANDRA-15453:
Description:
Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
h3. Background
I'm trying to upgrade Apache Beam's dependencies to latest versions. Apache
Beam depends on Cassandra 3 ({{org.apache.cassandra:cassandra-all:3.11.3}}).
Cassandra 3 touches on Guava's old fields (and potentially methods), such as
CharMatcher.DIGIT, are blocking Apache Beam's Guava dependency upgrade
(BEAM-8911); the field is removed in Guava 26.0. Because of this, Apache Beam's
Guava dependency must be lower than version 26.0.
I see the latest cassandra-all release on 3.X is 3.11.5, which still relies on
Guava 18. This version does not have {{CharMatcher.digit()}}, the replacement
of old {{CharMatcher.DIGIT}}. To get rid of {{CharMatcher.DIGIT}} and thus let
Apache Beam to use Guava 26 and higher, we need to upgrade Cassandra3's Guava
version.
h4. Test failure Beam's HadoopFormatIOCassandraTest
Apache Beam's {{:sdks:java:io:hadoop-format}} has
{{HadoopFormatIOCassandraTest}} that failed when I tried to upgrade Guava
version to 26:
https://github.com/GoogleCloudPlatform/cloud-opensource-java/issues/1028#issuecomment-557680928
.
h3. How about waiting for Cassandra version 4(-alpha)?
I thought about Cassandra "4", which has a recent version of Guava. However, I
believe quite a few Cassandra/Beam users will keep using Casandra 3 for several
years. I want such users to be able to use the higher version of Guava.
h3. Shading?
Shading makes build process complex. When things go wrong due to this, it's
hard to debug ([JLBP18|https://jlbp.dev/JLBP-18.html]).
h3. CASSANDRA-15248 "Upgrade Guava to latest on master branch",
I found CASSANDRA-15248 "Upgrade Guava to latest on master branch", but this
did not go into 3.11 branch. Can we backport this Guava version upgrade
(CASSANDRA-15248) into 3.11 branch?
was:
Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
h3. Background
I'm trying to upgrade Apache Beam's dependencies to latest versions. Apache
Beam depends on Cassandra 3 ({{org.apache.cassandra:cassandra-all:3.11.3}}).
Cassandra 3 touches on Guava's old fields (and potentially methods), such as
CharMatcher.DIGIT, are blocking Apache Beam's Guava dependency upgrade
(BEAM-8911); the field is removed in Guava 26.0. Because of this, Apache Beam's
Guava dependency must be lower than version 26.0.
I see the latest cassandra-all release on 3.X is 3.11.5, which still relies on
Guava 18. This version does not have {{CharMatcher.digit()}}, the replacement
of old {{CharMatcher.DIGIT}}. To get rid of {{CharMatcher.DIGIT}} and thus let
Apache Beam to use Guava 26 and higher, we need to upgrade Cassandra3's Guava
version.
h3. How about waiting for Cassandra version 4(-alpha)?
I thought about Cassandra "4", which has a recent version of Guava. However, I
believe quite a few Cassandra/Beam users will keep using Casandra 3 for several
years. I want such users to be able to use the higher version of Guava.
h3. Shading?
Shading makes build process complex. When things go wrong due to this, it's
hard to debug ([JLBP18|https://jlbp.dev/JLBP-18.html]).
h3. CASSANDRA-15248 "Upgrade Guava to latest on master branch",
I found CASSANDRA-15248 "Upgrade Guava to latest on master branch", but this
did not go into 3.11 branch. Can we backport this Guava version upgrade
(CASSANDRA-15248) into 3.11 branch?
> Upgrade Guava to the same version as master on 3.11 branch
> --
>
> Key: CASSANDRA-15453
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15453
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies
>Reporter: Tomo Suzuki
>Priority: Normal
>
> Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
> h3. Background
> I'm trying to upgrade Apache Beam's dependencies to latest versions. Apache
> Beam depends on Cassandra 3 ({{org.apache.cassandra:cassandra-all:3.11.3}}).
> Cassandra 3 touches on Guava's old fields (and potentially methods), such as
> CharMatcher.DIGIT, are blocking Apache Beam's Guava dependency upgrade
> (BEAM-8911); the field is removed in Guava 26.0. Because of this, Apache
> Beam's Guava dependency must be lower than version 26.0.
> I see the latest cassandra-all release on 3.X is 3.11.5, which still relies
> on Guava 18. This version does not have {{CharMatcher.digit()}}, the
> replacement of old {{CharMatcher.DIGIT}}. To get rid of {{CharMatcher.DIGIT}}
> and thus let Apache Beam to use Guava 26 and higher, we need to upgrade
> Cassandra3's Guava version.
> h4. Test failure Beam's HadoopFormatIOCassandraTest
> Apache Beam's
[jira] [Updated] (CASSANDRA-15453) Upgrade Guava to the same version as master on 3.11 branch
[
https://issues.apache.org/jira/browse/CASSANDRA-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomo Suzuki updated CASSANDRA-15453:
Description:
Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
h3. Background
I'm trying to upgrade Apache Beam's dependencies to latest versions. Apache
Beam depends on Cassandra 3 ({{org.apache.cassandra:cassandra-all:3.11.3}}).
Cassandra 3 touches on Guava's old fields (and potentially methods), such as
CharMatcher.DIGIT, are blocking Apache Beam's Guava dependency upgrade
(BEAM-8911); the field is removed in Guava 26.0. Because of this, Apache Beam's
Guava dependency must be lower than version 26.0.
I see the latest cassandra-all release on 3.X is 3.11.5, which still relies on
Guava 18. This version does not have {{CharMatcher.digit()}}, the replacement
of old {{CharMatcher.DIGIT}}. To get rid of {{CharMatcher.DIGIT}} and thus let
Apache Beam to use Guava 26 and higher, we need to upgrade Cassandra3's Guava
version.
h3. How about waiting for Cassandra version 4(-alpha)?
I thought about Cassandra "4", which has a recent version of Guava. However, I
believe quite a few Cassandra/Beam users will keep using Casandra 3 for several
years. I want such users to be able to use the higher version of Guava.
h3. Shading?
Shading makes build process complex. When things go wrong due to this, it's
hard to debug ([JLBP18|https://jlbp.dev/JLBP-18.html]).
h3. CASSANDRA-15248 "Upgrade Guava to latest on master branch",
I found CASSANDRA-15248 "Upgrade Guava to latest on master branch", but this
did not go into 3.11 branch. Can we backport this Guava version upgrade
(CASSANDRA-15248) into 3.11 branch?
was:
Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
h3. Background
I'm trying to upgrade Apache Beam's dependencies to latest versions. Apache
Beam depends on Cassandra 3 ({{org.apache.cassandra:cassandra-all:3.11.3}}).
Cassandra 3's dependency on Guava's old fields (potentially and methods), such
as CharMatcher.DIGIT, are blocking Apache Beam's Guava dependency upgrade
(BEAM-8911). The field is removed in Guava 26.0. Because of this, Apache Beam's
Guava dependency must be lower than version 26.0.
I see the latest cassandra-all release on 3.X is 3.11.5, which still relies on
Guava 18. This version does not have {{CharMatcher.digit()}}, the replacement
of old {{CharMatcher.DIGIT}}. To get rid of {{CharMatcher.DIGIT}} and thus let
Apache Beam to use Guava 26 and higher, we need to upgrade Cassandra's Guava
version.
h3. How about waiting for Cassandra version 4(-alpha)?
I thought about Cassandra "4", which has a recent version of Guava. However, I
believe quite a few Cassandra/Beam users will keep using Casandra 3 for several
years. I want such users to be able to use the higher version of Guava.
h3. Shading?
Shading makes build process complex. When things go wrong due to this, it's
hard to debug ([JLBP18|https://jlbp.dev/JLBP-18.html]).
h3. CASSANDRA-15248 "Upgrade Guava to latest on master branch",
I found CASSANDRA-15248 "Upgrade Guava to latest on master branch", but this
did not go into 3.11 branch. Can we backport this Guava version upgrade
(CASSANDRA-15248) into 3.11 branch?
> Upgrade Guava to the same version as master on 3.11 branch
> --
>
> Key: CASSANDRA-15453
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15453
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies
>Reporter: Tomo Suzuki
>Priority: Normal
>
> Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
> h3. Background
> I'm trying to upgrade Apache Beam's dependencies to latest versions. Apache
> Beam depends on Cassandra 3 ({{org.apache.cassandra:cassandra-all:3.11.3}}).
> Cassandra 3 touches on Guava's old fields (and potentially methods), such as
> CharMatcher.DIGIT, are blocking Apache Beam's Guava dependency upgrade
> (BEAM-8911); the field is removed in Guava 26.0. Because of this, Apache
> Beam's Guava dependency must be lower than version 26.0.
> I see the latest cassandra-all release on 3.X is 3.11.5, which still relies
> on Guava 18. This version does not have {{CharMatcher.digit()}}, the
> replacement of old {{CharMatcher.DIGIT}}. To get rid of {{CharMatcher.DIGIT}}
> and thus let Apache Beam to use Guava 26 and higher, we need to upgrade
> Cassandra3's Guava version.
> h3. How about waiting for Cassandra version 4(-alpha)?
> I thought about Cassandra "4", which has a recent version of Guava. However,
> I believe quite a few Cassandra/Beam users will keep using Casandra 3 for
> several years. I want such users to be able to use the higher version of
> Guava.
> h3. Shading?
> Shading makes build process complex. When
[jira] [Updated] (CASSANDRA-15453) Upgrade Guava to the same version as master on 3.11 branch
[
https://issues.apache.org/jira/browse/CASSANDRA-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomo Suzuki updated CASSANDRA-15453:
Description:
Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
h3. Background
I'm trying to upgrade Apache Beam's dependencies to latest versions. Apache
Beam depends on Cassandra 3 ({{org.apache.cassandra:cassandra-all:3.11.3}}).
Cassandra 3's dependency on Guava's old fields (potentially and methods), such
as CharMatcher.DIGIT, are blocking Apache Beam's Guava dependency upgrade
(BEAM-8911). The field is removed in Guava 26.0. Because of this, Apache Beam's
Guava dependency must be lower than version 26.0.
I see the latest cassandra-all release on 3.X is 3.11.5, which still relies on
Guava 18. This version does not have {{CharMatcher.digit()}}, the replacement
of old {{CharMatcher.DIGIT}}. To get rid of {{CharMatcher.DIGIT}} and thus let
Apache Beam to use Guava 26 and higher, we need to upgrade Cassandra's Guava
version.
h3. How about waiting for Cassandra version 4(-alpha)?
I thought about Cassandra "4", which has a recent version of Guava. However, I
believe quite a few Cassandra/Beam users will keep using Casandra 3 for several
years. I want such users to be able to use the higher version of Guava.
h3. Shading?
Shading makes build process complex. When things go wrong due to this, it's
hard to debug ([JLBP18|https://jlbp.dev/JLBP-18.html]).
h3. CASSANDRA-15248 "Upgrade Guava to latest on master branch",
I found CASSANDRA-15248 "Upgrade Guava to latest on master branch", but this
did not go into 3.11 branch. Can we backport this Guava version upgrade
(CASSANDRA-15248) into 3.11 branch?
was:
Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
h3. Background
I'm trying to upgrade Apache Beam's dependencies to latest versions. Apache
Beam depends on Cassandra 3 ({{org.apache.cassandra:cassandra-all:3.11.3}}).
Cassandra 3's dependency on Guava's old fields (potentially and methods), such
as CharMatcher.DIGIT, are blocking Apache Beam's Guava dependency upgrade
(BEAM-8911). The field is removed in Guava 26.0. Because of this, Apache Beam's
Guava dependency must be lower than version 26.0.
I see the latest cassandra-all release on 3.X is 3.11.5, which still relies on
Guava 18. This version does not have {{CharMatcher.digit()}}, the replacement
of old {{CharMatcher.DIGIT}}. To get rid of {{CharMatcher.DIGIT}} and thus let
Apache Beam to use Guava 26 and higher, we need to upgrade Cassandra's Guava
version.
h3. How about waiting for Cassandra version 4(-alpha)?
I thought about Cassandra "4", which has a recent version of Guava. However, I
believe quite a few Cassandra/Beam users will keep using Casandra 3 for several
years. I want such users to be able to use the higher version of Guava.
h3. CASSANDRA-15248 "Upgrade Guava to latest on master branch",
h3. Shading?
Shading makes build process complex. When things go wrong due to this, it's
hard to debug ([JLBP18|https://jlbp.dev/JLBP-18.html]).
I found CASSANDRA-15248 "Upgrade Guava to latest on master branch", but this
did not go into 3.11 branch. Can we backport this Guava version upgrade
(CASSANDRA-15248) into 3.11 branch?
> Upgrade Guava to the same version as master on 3.11 branch
> --
>
> Key: CASSANDRA-15453
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15453
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies
>Reporter: Tomo Suzuki
>Priority: Normal
>
> Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
> h3. Background
> I'm trying to upgrade Apache Beam's dependencies to latest versions. Apache
> Beam depends on Cassandra 3 ({{org.apache.cassandra:cassandra-all:3.11.3}}).
> Cassandra 3's dependency on Guava's old fields (potentially and methods),
> such as CharMatcher.DIGIT, are blocking Apache Beam's Guava dependency
> upgrade (BEAM-8911). The field is removed in Guava 26.0. Because of this,
> Apache Beam's Guava dependency must be lower than version 26.0.
> I see the latest cassandra-all release on 3.X is 3.11.5, which still relies
> on Guava 18. This version does not have {{CharMatcher.digit()}}, the
> replacement of old {{CharMatcher.DIGIT}}. To get rid of {{CharMatcher.DIGIT}}
> and thus let Apache Beam to use Guava 26 and higher, we need to upgrade
> Cassandra's Guava version.
> h3. How about waiting for Cassandra version 4(-alpha)?
> I thought about Cassandra "4", which has a recent version of Guava. However,
> I believe quite a few Cassandra/Beam users will keep using Casandra 3 for
> several years. I want such users to be able to use the higher version of
> Guava.
> h3. Shading?
> Shading makes build process complex.
[jira] [Updated] (CASSANDRA-15453) Upgrade Guava to the same version as master on 3.11 branch
[
https://issues.apache.org/jira/browse/CASSANDRA-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomo Suzuki updated CASSANDRA-15453:
Description:
Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
h3. Background
I'm trying to upgrade Apache Beam's dependencies to latest versions. Apache
Beam depends on Cassandra 3 ({{org.apache.cassandra:cassandra-all:3.11.3}}).
Cassandra 3's dependency on Guava's old fields (potentially and methods), such
as CharMatcher.DIGIT, are blocking Apache Beam's Guava dependency upgrade
(BEAM-8911). The field is removed in Guava 26.0. Because of this, Apache Beam's
Guava dependency must be lower than version 26.0.
I see the latest cassandra-all release on 3.X is 3.11.5, which still relies on
Guava 18. This version does not have {{CharMatcher.digit()}}, the replacement
of old {{CharMatcher.DIGIT}}. To get rid of {{CharMatcher.DIGIT}} and thus let
Apache Beam to use Guava 26 and higher, we need to upgrade Cassandra's Guava
version.
h3. How about waiting for Cassandra version 4(-alpha)?
I thought about Cassandra "4", which has a recent version of Guava. However, I
believe quite a few Cassandra/Beam users will keep using Casandra 3 for several
years. I want such users to be able to use the higher version of Guava.
h3. CASSANDRA-15248 "Upgrade Guava to latest on master branch",
h3. Shading?
Shading makes build process complex. When things go wrong due to this, it's
hard to debug ([JLBP18|https://jlbp.dev/JLBP-18.html]).
I found CASSANDRA-15248 "Upgrade Guava to latest on master branch", but this
did not go into 3.11 branch. Can we backport this Guava version upgrade
(CASSANDRA-15248) into 3.11 branch?
was:
Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
h3. Background
Cassandra 3's dependency on old fields (potentially and methods), such as
CharMatcher.DIGIT, is blocking Apache Beam's Guava dependency upgrade
(BEAM-8911). Beam's Guava dependency is limited at most lower than version 26.0.
I see the latest cassandra-all release on 3.X is 3.11.5, which still relies on
Guava 18. This version does not have {{CharMatcher.digit()}}, the replacement
of old {{CharMatcher.DIGIT}}. To get rid of {{CharMatcher.DIGIT}} and thus let
Apache Beam to use Guava 26 and higher, we need to upgrade Cassandra's Guava
version.
h3. How about waiting for Cassandra version 4(-alpha)?
I thought about Cassandra "4", which has a recent version of Guava. However, I
believe quite a few Cassandra/Beam users will keep using Casandra 3 for several
years. I want such users to be able to use the higher version of Guava.
h3. CASSANDRA-15248 "Upgrade Guava to latest on master branch",
I found CASSANDRA-15248 "Upgrade Guava to latest on master branch", but this
did not go into 3.11 branch. Can we backport this Guava version upgrade
(CASSANDRA-15248) into 3.11 branch?
> Upgrade Guava to the same version as master on 3.11 branch
> --
>
> Key: CASSANDRA-15453
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15453
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies
>Reporter: Tomo Suzuki
>Priority: Normal
>
> Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
> h3. Background
> I'm trying to upgrade Apache Beam's dependencies to latest versions. Apache
> Beam depends on Cassandra 3 ({{org.apache.cassandra:cassandra-all:3.11.3}}).
> Cassandra 3's dependency on Guava's old fields (potentially and methods),
> such as CharMatcher.DIGIT, are blocking Apache Beam's Guava dependency
> upgrade (BEAM-8911). The field is removed in Guava 26.0. Because of this,
> Apache Beam's Guava dependency must be lower than version 26.0.
> I see the latest cassandra-all release on 3.X is 3.11.5, which still relies
> on Guava 18. This version does not have {{CharMatcher.digit()}}, the
> replacement of old {{CharMatcher.DIGIT}}. To get rid of {{CharMatcher.DIGIT}}
> and thus let Apache Beam to use Guava 26 and higher, we need to upgrade
> Cassandra's Guava version.
> h3. How about waiting for Cassandra version 4(-alpha)?
> I thought about Cassandra "4", which has a recent version of Guava. However,
> I believe quite a few Cassandra/Beam users will keep using Casandra 3 for
> several years. I want such users to be able to use the higher version of
> Guava.
> h3. CASSANDRA-15248 "Upgrade Guava to latest on master branch",
> h3. Shading?
> Shading makes build process complex. When things go wrong due to this, it's
> hard to debug ([JLBP18|https://jlbp.dev/JLBP-18.html]).
> I found CASSANDRA-15248 "Upgrade Guava to latest on master branch", but this
> did not go into 3.11 branch. Can we backport this Guava version upgrade
> (CASSANDRA-15248) into 3.11 branch?
--
[jira] [Created] (CASSANDRA-15453) Upgrade Guava to the same version as master on 3.11 branch
Tomo Suzuki created CASSANDRA-15453:
---
Summary: Upgrade Guava to the same version as master on 3.11 branch
Key: CASSANDRA-15453
URL: https://issues.apache.org/jira/browse/CASSANDRA-15453
Project: Cassandra
Issue Type: Improvement
Components: Dependencies
Reporter: Tomo Suzuki
Can we backport the Guava version upgrade (CASSANDRA-15248) into 3.11 branch?
h3. Background
Cassandra 3's dependency on old fields (potentially and methods), such as
CharMatcher.DIGIT, is blocking Apache Beam's Guava dependency upgrade
(BEAM-8911). Beam's Guava dependency is limited at most lower than version 26.0.
I see the latest cassandra-all release on 3.X is 3.11.5, which still relies on
Guava 18. This version does not have {{CharMatcher.digit()}}, the replacement
of old {{CharMatcher.DIGIT}}. To get rid of {{CharMatcher.DIGIT}} and thus let
Apache Beam to use Guava 26 and higher, we need to upgrade Cassandra's Guava
version.
h3. How about waiting for Cassandra version 4(-alpha)?
I thought about Cassandra "4", which has a recent version of Guava. However, I
believe quite a few Cassandra/Beam users will keep using Casandra 3 for several
years. I want such users to be able to use the higher version of Guava.
h3. CASSANDRA-15248 "Upgrade Guava to latest on master branch",
I found CASSANDRA-15248 "Upgrade Guava to latest on master branch", but this
did not go into 3.11 branch. Can we backport this Guava version upgrade
(CASSANDRA-15248) into 3.11 branch?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15248) Upgrade Guava to latest on master branch
[
https://issues.apache.org/jira/browse/CASSANDRA-15248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995952#comment-16995952
]
Tomo Suzuki commented on CASSANDRA-15248:
-
Can this enhancement merged to 3.11 branch and released?
{{Cassandra-all:3.11}}'s dependency is blocking Beam's Guava dependency
(BEAM-8911).
> Upgrade Guava to latest on master branch
>
>
> Key: CASSANDRA-15248
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15248
> Project: Cassandra
> Issue Type: Task
> Components: Build, Dependencies, Packaging
>Reporter: Abhijit Sarkar
>Priority: Normal
>
> Upgrade Guava to latest on master branch. See
> https://issues.apache.org/jira/browse/CASSANDRA-15245.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15248) Upgrade Guava to latest on master branch
[
https://issues.apache.org/jira/browse/CASSANDRA-15248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995952#comment-16995952
]
Tomo Suzuki edited comment on CASSANDRA-15248 at 12/13/19 10:05 PM:
Would you merge this great enhancement to 3.11 branch and have it released?
{{Cassandra-all:3.11}}'s dependency is blocking Beam's Guava dependency
(BEAM-8911).
was (Author: suztomo):
Can this enhancement merged to 3.11 branch and released?
{{Cassandra-all:3.11}}'s dependency is blocking Beam's Guava dependency
(BEAM-8911).
> Upgrade Guava to latest on master branch
>
>
> Key: CASSANDRA-15248
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15248
> Project: Cassandra
> Issue Type: Task
> Components: Build, Dependencies, Packaging
>Reporter: Abhijit Sarkar
>Priority: Normal
>
> Upgrade Guava to latest on master branch. See
> https://issues.apache.org/jira/browse/CASSANDRA-15245.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
