> I must admit when the ORC unit tests failed with jdk11 and the debugger
showed that it was failing because it was in code that should have been
unreachable with the data values, I just went back to jdk10 rather than
diagnosing it.
Owen, could you check the bug you faced was the filed test failur
I appreciate your help, Ewan and Tsuyoshi.
Based on the discussion in this thread, after the bug reported by Owen
and Tsuyoshi is resolved, I'll close the jiras of supporting JDK9/10
and let's focus on supporting JDK 11 (and JDK 8).
>
>
> on 2018/11/11 23:35, "Tsuyoshi Ozawa" wrote:
>
> Than
Thanks Takanobu for stating the discussion, and thanks Ewan for
sharing the pointer.
I reproduced the bug Owen said only with OpenJDK 11, so I filed it on
ORC jira for now:
https://jira.apache.org/jira/browse/ORC-436
I looked over the bug, but I cannot identify the root cause - only on
OpenJDK 11
Hi all,
Reporting bugs to Java is a bit weird/nontrivial so I'm sympathetic to Owen's
situation. The openjdk bug tracker requires users be committers so no one can
comment unless they're already contributing.
Their tracker is here:
https://bugs.openjdk.java.net/projects/JDK/issues
To actually f
On Wed, Nov 7, 2018 at 2:18 AM Steve Loughran
wrote:
>
> If there are problems w/ JDK11 then we should be talking to oracle about
> them to have them fixed. Is there an ASF JIRA on this issue yet?
>
I must admit when the ORC unit tests failed with jdk11 and the debugger
showed that it was failin
Not to throw fuel on the fire so to say, nor to make any statement about
not wanting anybody to spend time on JDK 9 or 10, but our general thinking
at Twitter is that we'll skip over these versions as well and move straight
to JDK 11 as well.
That said, this is still a bit of an aspiration for us
Steve,
Thank you very much. I am honored to hear you say that. I also thank to
Akira and the others for driving this work.
I agree to being proactive since software depending on Hadoop is
increasing. And it's good to adopt functional programming features
gradually.
Regards,
- Takanobu
> on 20
If there are problems w/ JDK11 then we should be talking to oracle about them
to have them fixed. Is there an ASF JIRA on this issue yet?
As usual, the large physical clusters will be slow to upgrade,
but the smaller cloud ones can get away with being agile, and as I believe that
YARN does let
Thanks for your reply, Owen.
> That said, I’d be surprised if the work items for JDK 9 and 10 aren’t a
strict subset of the issues getting to JDK 11.
Most of the issues that we have fixed are subset of the ones of JDK 11. But
there seem to be some exceptions. HADOOP-15905 is a bug of JDK 9/10 whi
I’m less convinced. I’ve hit at least one pretty serious JVM bug in JDK 11, so
there is value in enabling JDK 9 and 10 even with blockers on JDK 11.
That said, I’d be surprised if the work items for JDK 9 and 10 aren’t a strict
subset of the issues getting to JDK 11.
.. Owen
> On Nov 5, 2018,
+1 It makes sense to converge on the LTS version.
Thanks for the initiative.
73
Kihwal
On Sun, Nov 4, 2018 at 10:10 PM Takanobu Asanuma
wrote:
> Hi all,
>
> As discussed in HADOOP-11123, we stop fixing incompatibilities of JDK9 and
> JDK10, and would like to focus on supporting JDK11.
> This we
Hi all,
As discussed in HADOOP-11123, we stop fixing incompatibilities of JDK9 and
JDK10, and would like to focus on supporting JDK11.
This week, I plan to close HADOOP-11123(Support Java 9) and
HADOOP-11423(Support Java 10) as duplicate/superceded, and move the
unresolved sub-tasks to under HADOO
12 matches
Mail list logo
