I created https://issues.apache.org/jira/browse/ARROW-2055 to track. Also created the javadoc issue as subtask.
On Tue, Jan 30, 2018 at 11:44 AM, Dwight Gunning <[email protected]> wrote: > Thanks Li, > > There is no JIRA as yet except for Arrow 2015 for the JODA time migration > to Java 8 Time - so please create a JIRA. > > Cheers > > Dwight > > Sent from my iPhone > > > On Jan 30, 2018, at 11:35 AM, Li Jin <[email protected]> wrote: > > > > Thanks Dwight, > > > > I think it would be good to track the required items for moving to Java 8 > > support. > > > > As far as I know, Arrow works with Java 8 already so this shouldn't be > too > > hard. > > > > Dependencies wise downstream projects Spark 2.3 already drops Java 7 > > support, I am not sure about Dremio. > > > > Is there a Jira for this already? If not I can create one. > > > > Li > > > >> On Mon, Jan 29, 2018 at 1:28 PM, Dwight Gunning <[email protected]> > wrote: > >> > >> Arrow Java currently compiles against Java 7 and it is time to plan an > >> upgrade to a later compilation target. The most suitable candidate is > Java > >> 8 which according to Baeldung <http://www.baeldung.com/java-in-2017> > >> reached *75% developer penetration* in 2017. > >> > >> The immediate trigger for this discussion was Arrow 2015 - Use Java 8 > Date > >> and Time API instead of Joda Time > >> <https://issues.apache.org/jira/browse/ARROW-2015>*. *The Java 8 move > >> would > >> therefore be a prerequisite for that JIRA. > >> > >> Let's discuss any challenges for moving to Java 8. E.g. it was > mentioned in > >> the Jan 24th meetup that Java 8 impacted Javadoc generation. > >> > >> Thanks > >> Dwight Gunning > >> FINRA (Toronto) > >> >
