Re: Moving Hive Jenkins jobs to builds.apache.org

[Sergio Pena]

Hi All,

I just finished moving all Jenkins jobs to https://builds.apache.org. I
will keep monitoring the jobs during the week to make sure they runs fine.
There is a view in Jenkins where you can see all Hive jobs,
https://builds.apache.org/view/H-L/view/Hive/

There are a couple of jobs that I don't know if they are still be used,
"hive-trunk" and "hive-0.14"
Please let me know if someone is using those jobs, or if I can destroy them
so that we can keep this view clean.

Please let me know If you have problems with Jenkins.

- Sergio

On Sun, May 29, 2016 at 9:40 PM, Sergio Pena 
wrote:

> Hi All,
>
> Just to let you know that I will plan to move our Jenkins jobs and
> configurations to the builds.apache.org site during this week.  ASF has a
> good infrastructure for Jenkins, and have all jobs backed up in case of
> server failures.
>
> Also, some people in the Hive community is showing interest in helping on
> Jenkins, so I would like to give that benefit by moving it to ASF Jenkins.
>
> For now, only Jenkins will be moved, but the cluster will still be
> private. However, I will continue working on making this more open too.
>
> Just one thing about ASF jenkins is that it has too many jobs from all
> Apache projects. Hopefully you don't get lost on it when looking for Hive
> :P.
>
> I'll let you know when all this happens.
>
> - Sergio
>

[jira] [Created] (HIVE-13949) Investigate why Filter mechanism does not work for XSRF filtering from HS2

[Sushanth Sowmyan (JIRA)]

Sushanth Sowmyan created HIVE-13949:
---

 Summary: Investigate why Filter mechanism does not work for XSRF 
filtering from HS2
 Key: HIVE-13949
 URL: https://issues.apache.org/jira/browse/HIVE-13949
 Project: Hive
  Issue Type: Bug
  Components: HiveServer2
Reporter: Sushanth Sowmyan


While working on HIVE-13853, it was found that simply using the constructed 
Filter as-is from ThriftHttpCLIService was not working, and thus, needed 
explicit calling of the filtering method from ThriftHttpServlet was needed.

We should investigate why that other method did not work, and make it fall 
inline with filter usage, so as to not need to call functions inside the 
filter. Also, this is a prerequisite for eventually getting rid of our shim if 
we later update to always expecting hadoop versions that contain the filter



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [discuss] jdk8 support

[Gopal Vijayaraghavan]

+1 from me, it's been more than a year since JDK7 EOL.

This needs a separate voting thread away from [discuss].

Cheers,
Gopal

On 6/4/16, 11:14 AM, "Lars Francke"  wrote:

>+1 for option 3 to drop Java 7 and start using Java8 features in code as
>well
>
>On Fri, Jun 3, 2016 at 9:38 PM, Reuben Kuhnert
>
>wrote:
>
>> +1 Drop Java7 support, start using JDK8 features.
>>
>> On Fri, Jun 3, 2016 at 12:39 PM, Prasanth Jayachandran <
>> pjayachand...@hortonworks.com> wrote:
>>
>> > +1 for using jdk8 as minimum required version.
>> >
>> > Thanks
>> > Prasanth
>> >
>> >
>> >
>> >
>> > On Fri, Jun 3, 2016 at 10:21 AM -0700, "Siddharth Seth" <
>> ss...@apache.org
>> > > wrote:
>> >
>> > +1. Drop Java7 support, and start using JDK8 features.
>> >
>> > On Fri, Jun 3, 2016 at 8:13 AM, Ashutosh Chauhan
>>
>> > wrote:
>> >
>> > > What I meant was that we start compiling using jdk8 as well. That
>>will
>> > > allow devs to use jdk8 only features (lambda functions etc.)
>> > >
>> > > On Fri, Jun 3, 2016 at 8:10 AM, Sergio Pena
>>
>> > > wrote:
>> > >
>> > > > Hey Ashutosh,
>> > > >
>> > > > I switched to JDK8 in master last weekend. Jenkins has been
>>running
>> all
>> > > > tests in Java8 successfully for a week now.
>> > > > There are still a few tests we need to fix, but so far is looking
>> good.
>> > > >
>> > > > Sergio
>> > > >
>> > > > On Fri, Jun 3, 2016 at 12:02 AM, Ashutosh Chauhan <
>> > hashut...@apache.org>
>> > > > wrote:
>> > > >
>> > > > > Now that branch-2.1 has been cut, I think its an opportune time
>>to
>> > drop
>> > > > > support of jdk7 altogether in master. That is we compile using
>>jdk8
>> > as
>> > > > > well. What do others think?
>> > > > >
>> > > > > Ashutosh
>> > > > >
>> > > > > On Fri, May 27, 2016 at 7:41 PM, Sergio Pena <
>> > sergio.p...@cloudera.com
>> > > >
>> > > > > wrote:
>> > > > >
>> > > > > > I did the change to JDK8 on Ptest now.
>> > > > > >
>> > > > > > Please let me tknow if there are issues with Java8.
>> > > > > >
>> > > > > > - Sergio
>> > > > > >
>> > > > > > On Fri, May 27, 2016 at 2:45 PM, Sergio Pena <
>> > > sergio.p...@cloudera.com
>> > > > >
>> > > > > > wrote:
>> > > > > >
>> > > > > > > Thanks Mohit.
>> > > > > > >
>> > > > > > > I will plan to do the JDK8 change on Jenkins today EOD and
>> > monitor
>> > > > any
>> > > > > > > issues through the weekend.
>> > > > > > >
>> > > > > > > - Sergio
>> > > > > > >
>> > > > > > >
>> > > > > > > On Fri, May 27, 2016 at 2:58 AM, Mohit Sabharwal <
>> > > mo...@cloudera.com
>> > > > >
>> > > > > > > wrote:
>> > > > > > >
>> > > > > > >> Update on moving Hive2 tests to JDK8: I've addressed almost
>> all
>> > > test
>> > > > > > >> failures in HIVE-13547 on java8 branch. There is one
>>remaining
>> > > > > > >> open item (HIVE-13834) which is currently assigned. Given
>> > current
>> > > > > > >> state of flaky test runs, there might be few more.
>> > > > > > >>
>> > > > > > >> I will work with Sergio to merge the test fixes to master
>>and
>> > > switch
>> > > > > > >> the Hive2 pre-commit job to use JDK8, hopefully sometime
>> > tomorrow.
>> > > > > > >>
>> > > > > > >> After Hive2 tests switch, if your patch sees ordering
>>related
>> > test
>> > > > > > >> failures in pre-commit run, it's likely JDK version related
>> and
>> > > > you'll
>> > > > > > >> need to build & re-run the test using JDK8. Number of such
>> tests
>> > > > > > >> should be relatively small.
>> > > > > > >>
>> > > > > > >> On Tue, Apr 19, 2016 at 10:43 AM, Mohit Sabharwal <
>> > > > mo...@cloudera.com
>> > > > > >
>> > > > > > >> wrote:
>> > > > > > >>
>> > > > > > >> > Created HIVE-13547 to track switching 2x tests to JDK8.
>> > > > > > >> >
>> > > > > > >> > On Wed, Apr 13, 2016 at 10:02 AM, Sergio Pena <
>> > > > > > sergio.p...@cloudera.com
>> > > > > > >> >
>> > > > > > >> > wrote:
>> > > > > > >> >
>> > > > > > >> >> I agree with such change as JDK7 is not longer
>>supported.
>> > > > > > >> >>
>> > > > > > >> >> Changes on Jenkins and Hive PTest shouldn't be hard. We
>> just
>> > > need
>> > > > > to
>> > > > > > >> >> replace the path from java7 to java8. But I think we
>>should
>> > fix
>> > > > all
>> > > > > > >> JDK8
>> > > > > > >> >> issues or most of them before doing the change or we
>>will
>> end
>> > > up
>> > > > > > >> having a
>> > > > > > >> >> lot of failures on all JIRAs running pre-commit tests.
>> > > > > > >> >>
>> > > > > > >> >> +1 with the change.
>> > > > > > >> >>
>> > > > > > >> >> On Mon, Apr 11, 2016 at 9:34 PM, Siddharth Seth <
>> > > > ss...@apache.org>
>> > > > > > >> wrote:
>> > > > > > >> >>
>> > > > > > >> >> > Option 3 sounds good. I'd ideally like to make JDK8
>>the
>> > > minimum
>> > > > > > >> >> requirement
>> > > > > > >> >> > soon as well.
>> > > > > > >> >> >
>> > > > > > >> >> > On Mon, Apr 11, 2016 at 4:59 PM, Szehon Ho <
>> > > > sze...@cloudera.com>
>> > > > > > >> wrote: