Re: [DISCUSS] deprecation policy

Hello, Regarding dropping index support: I've thinked about it a few times earlier because it complicates things; on the other hand I think there are no real user base behind it because parquet/orc does a similar(better) optimization - without the extra need of sql ddls...the ticket have

Re: [DISCUSS] deprecation policy

+1 to Ed’s comments. Alan. On Tue, Feb 13, 2018 at 7:08 AM, Edward Capriolo wrote: > I do not think we should remove: > > https://issues.apache.org/jira/browse/HIVE-18692 > > One of the challenges of HQL is not having a procedure language. This > forces users into

Re: [DISCUSS] deprecation policy

I do not think we should remove: https://issues.apache.org/jira/browse/HIVE-18692 One of the challenges of HQL is not having a procedure language. This forces users into oozie/airflow/spark even to orchestrate simple flows. Lets give that one some time to marinate, but I agree technically it

[DISCUSS] deprecation policy

Hi Team, I am seeing several jiras proposing removing functions from Hive: HIVE-18691 Drop Support for Explicit Table Lock From Apache Hive HIVE-18692 Remove HPL/SQL From Apache Hive HIVE-18448 Drop Support For Indexes From Apache Hive I generally agree with removing unused functions. Especially