Yes, I knew what you meant. I don’t think a major version change is warranted
just because Flume now requires Java 11. In fact, the 1.8 release bumped the
JDK requirement from 1.7 to 1.8 so there is already precedent for this.
In my view a 2.0 release would need to be much more invasive such
: Updating 3rd party dependencies
[EXTERNAL EMAIL]
I meant the other way around as Java 8 is EOL and users have to upgrade to Java
11.
I would like to achieve Java 11 support and now Flume does _not_ run with Java
11 because of its dependencies.
for example from the unit tests:
- Hive sink
I meant the other way around as Java 8 is EOL and users have to upgrade to
Java 11.
I would like to achieve Java 11 support and now Flume does _not_ run with
Java 11 because of its dependencies.
for example from the unit tests:
- Hive sink does not work with Java 11
- Elasticsearch sink does not
I don’t think a major version change should be necessary just because the JDK
dependency changed. Changing the major version number should tied to major
changes in the project itself.
I am curious to know what dependencies now only run on Java 11.
Ralph
> On May 3, 2019, at 5:02 AM, Ferenc
