I need avro version 1.11.0 in the below dependencies. Currently it is only supported in 1.8.2
https://raw.githubusercontent.com/apache/beam/v2.38.0/buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy
Thanks for the help
Thanks for the question. There are breaking changes in Avro so there is some tricky work to make Beam compatible with multiple versions at the same time. You can follow progress on https://issues.apache.org/jira/browse/BEAM-8388, https://github.com/apache/beam/pull/17372, https://github.com/apache/beam/pull/16271
Related
Good day!
Can you tell me how update the org.json:json component to a newer version? Current version - 20171018. Newer version - 20220924.
Assuming it's 100% backwards compatible you can just download the new jar (e.g. from here) and replace the old one with the new one in the broker distribution.
In ActiveMQ Artemis 2.27.1 json-20171018.jar is in the <ARTEMIS_HOME>/web/console.war archive in the /WEB-INF/lib directory.
What kind of benefits do you think upgrading the kafka version will provide and is it important? What are the advantages of switching from 2.8 to 3.1?
The Kafka release notes cover all added features and fixes. For example, as of Kafka 3.3.1 release, Zookeeper is no longer required.
Kafka 3.0 removed support for Scala 2.11, and maybe Java 7/8, and enables transactions by default, I believe.
Make sure that you read the upgrade notes for protocol changes that will make it impossible to downgrade in the event of errors.
Is httpclient-4.5.2.jar backward compatible with httpclient-4.3.6.jar?
Same question also for httpcore-4.4.4.jar with httpcore-4.3.3.jar?
I have to use a newer version for supporting some functionality. but is there any impact of my older code?
Is those jar version controlling working conventional way for backward compatibility support like java JDK?
Short answer no. For minor upgrades (4.3.3 to 4.3.4) things usually work, but when you go from 4.3 to 4.5 you can expect changes. See release notes for hints about what you can expect.
Having said that, if you can compile without errors you are usually safe!
did anyone try it? I need to generate scala classes for protobuf 2.5.0
Seems like ScalaPB supports protobuf 3.x and not 2.5.0
So... Nadav Samet answered to me in google group. it's impossible.
Quoting his answer:
The problem is that the different versions of protobuf-java are not
binary compatible. So if it would work with 2.5.0 it wouldn't work
with 3.4.0. If the reason you need protobuf 2.5.x support is because
there's some other library that is stuck on that version, consider
asking them to move forward, or use a shaded version of protobuf-java
so the versions won't conflict.
I am trying to use a library for implementing a OAuth2 server in play! 2.0.4 framework using this repo https://github.com/nulab/scala-oauth2-provider
I want to know if there is any way that I can use this library with play-2.0.4 by changing play version or sbt version. I do not want to break compile time or run time dependencies.
From what I have figured out. I think its not possible because the DataHandler trait in the library expects scala.concurrent.Future return type for some methods which were introduced with a later version of scala than the one play! 2.0.4 runs on.
Nope, this is not possible. Play 2.0.4 isn't built for Scala 2.10 or later, and scala-oauth2-provider requires Scala 2.10 or later. Even if you could get Play 2.0.x compiled on Scala 2.10.x, you'd probably still run into some API compatibility problems, as that library is geared towards Play 2.2.x and 2.3.x. Between Play 2.0.x and 2.2.x, there have been many breaking API changes you'd have to reconcile.
There hasn't been support for Play 2.0.x for almost two years now. It may be the time to upgrade. Migration breaks things, yes, but in the long run you're better off staying up-to-date.