Reynold Xin created HIVE-16391:
--
Summary: Publish proper Hive 1.2 jars (without including all
dependencies in uber jar)
Key: HIVE-16391
URL: https://issues.apache.org/jira/browse/HIVE-16391
Project
Aleksey Vovchenko created HIVE-16118:
Summary: Some queries with multiple inserts fail in Hive-1.2 and
work in Hive-0.13
Key: HIVE-16118
URL: https://issues.apache.org/jira/browse/HIVE-16118
Oleksiy Sayankin created HIVE-15082:
---
Summary: Hive-1.2 cannot read data from complex data types with
TIMESTAMP column, stored in Parquet
Key: HIVE-15082
URL: https://issues.apache.org/jira/browse/HIVE-15082
Rahul created HIVE-12729:
Summary: In Hive 1.2 - current_date() comparison results in Error
Unsupported conversion from type: interval_day_time
Key: HIVE-12729
URL: https://issues.apache.org/jira/browse/HIVE-12729
Na Yang created HIVE-11765:
--
Summary: SMB Join fails in Hive 1.2
Key: HIVE-11765
URL: https://issues.apache.org/jira/browse/HIVE-11765
Project: Hive
Issue Type: Bug
Components: Hive
Additionally, although it is a PoC you should have a realistic data model.
Furthermore, following good data modeling practices should be taken into
account. Joining on a double is not one of them. It should be int.
Furthermore, double is a type that is in most scenarios rarely used. In the
business
Thanks for the reply Noam. I have already tried the later point of dividing
the query. But the challenge comes during the joining of the table.
Thanks and Regards
Nishant Aggarwal, PMP
Cell No:- +91 99588 94305
On Thu, Aug 20, 2015 at 2:19 PM, Noam Hasson
wrote:
> Hi,
>
> Have you look at cou
Hi,
Have you look at counters in Hadoop side? It's possible you are dealing
with a bad join which causes multiplication of items, if you see huge
number of record input/output in map/reduce phase and keeps increasing
that's probably the case.
Another thing I would try is to divide the job into se
Please check out HIVE-11502. For your poc, you can simply get around using
other data types instead of double.
On Thu, Aug 20, 2015 at 2:08 AM, Nishant Aggarwal
wrote:
> Thanks for the reply Noam. I have already tried the later point of
> dividing the query. But the challenge comes during the jo
gurmukh singh created HIVE-10990:
Summary: Compatibility Hive-1.2 an hbase-1.0.1.1
Key: HIVE-10990
URL: https://issues.apache.org/jira/browse/HIVE-10990
Project: Hive
Issue Type: Bug
Thank you all for your requests for inclusion over at
https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
. This list is now frozen for any new requests for inclusion of
ordinary bugfixes or features, and we'll work our way through RCs
attempting to get all the outsta
Hi Folks,
As of yesterday, we had a dummy RC0 ready, and the time draws near to
start getting all the issues set about in
https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
to getting them resolved, and then rolling out an RC1. To do this, we
must first freeze the list over
Hi Folks,
As per the timeline set on
https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
, the time for requests for inclusion of any new features to
branch-1.2 is now closed. Any JIRAS already marked in the lists
previously will be honoured and considered release blockers
folks : If you have any other jira you
want included for 1.2, please go and add it to
https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
Tonight midnight will be the deadline for feature include requests,
and this list will go on lockdown for any further requests for fe
Also, Agreed with Sergio/Szehon, we should have a jira that's marked
as committed with a patch attached for the version bump patch.
Creating one.
On Mon, Apr 27, 2015 at 4:39 PM, Sushanth Sowmyan wrote:
> Vinod,
>
> If 2.7.0 is "not-yet-ready", then we should not be bumping 1.2 to
> 2.7.0. But, w
Vinod,
If 2.7.0 is "not-yet-ready", then we should not be bumping 1.2 to
2.7.0. But, we should be okay to bump master(1.3) up to 2.7.0 so that
we start general-purpose testing against that.
Please go ahead and create a jira for that, and we should be able to
bump up trunk to go against that.
Tha
nal their desire that this be included in 1.2 :
https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
A rough timeline I see for this process would be to fork this Friday
(24th Apr), and then start rolling out RC0 by, say, Wednesday next
week. This would mean that I would request
> so any new resolved jiras can be marked with this instead?
> >
> > Everyone else : Once this jira version is created, please use fix
> > version = 1.3.0 for any jiras you resolve in master.
> >
> > Also, please refer to
> > https://cwiki.apache.org/confluence/
0 for any jiras you resolve in master.
>
> Also, please refer to
> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
> for a proposed timeline of how I expect release candidates and the
> list for jira inclusion is intended to go for this release.
>
> Thanks
;
> Also, please refer to
> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
> for a proposed timeline of how I expect release candidates and the
> list for jira inclusion is intended to go for this release.
>
> Thanks!
> -Sushanth
>
>
> On Fri, Apr 24,
: Once this jira version is created, please use fix
version = 1.3.0 for any jiras you resolve in master.
Also, please refer to
https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
for a proposed timeline of how I expect release candidates and the
list for jira inclusion is
Hi Mithun,
I've added the lot into the wiki. I would suggest that we try to
rebase/review/get them in by about wednesday at the latest, which
means they might not get into RC0, but should be in RC1 after.
On Fri, Apr 24, 2015 at 3:45 PM, Mithun Radhakrishnan
wrote:
> Hey, Sush. Thanks for volunt
>
> Thanks
> Szehon
>
> On Fri, Apr 24, 2015 at 1:25 PM, Sushanth Sowmyan
> wrote:
>
>> Hi All,
>>
>> I'd like to send along a last reminder people to add any jiras that
>> people want included in 1.2 to
>> https://cwiki.apache.org/conflu
Hey, Sush. Thanks for volunteering, sir.
Sorry for my tardy response. There are a few JIRAs I was hoping to get into
this release:
1. HIVE-9674: DropPartitionEvent to support partition-sets. (Reviewed.)2.
HIVE-9681: HiveAuthProvider to handle partition-sets. (Yet to be reviewed.)3.
HIVE-9736: Ba
d along a last reminder people to add any jiras that
> people want included in 1.2 to
> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
> or reply to this mail with any further requests for inclusions.
>
> As it currently stands, even though we did have a couple
Hi All,
I'd like to send along a last reminder people to add any jiras that
people want included in 1.2 to
https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
or reply to this mail with any further requests for inclusions.
As it currently stands, even though we did h
r to manage under git. I would still
>> like to go ahead with a friday/weekend fork, and allow people to
>> continue submitting patches for inclusion up until we roll out an RC0,
>> and then lock it for bugfixes. (Note : If there are any other jiras
>> you are working on th
le to
> continue submitting patches for inclusion up until we roll out an RC0,
> and then lock it for bugfixes. (Note : If there are any other jiras
> you are working on that you want to see in this release, please go add
> it to that wiki list :
> https://cwiki.apache.org/confluence/d
working on that you want to see in this release, please go add
it to that wiki list :
https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
)
I would like to avoid a long-tail process as happened for 0.12.0 &
0.13.0 if possible. This way, I think we'll have mo
; >>
> > >> Per my mail 3 weeks back, we should start getting ready to release 1.2
> > >> as a rollup. And as per my proposal to manage this release, I'd like
> > >> to start off the process of forking 1.2, and making trunk 1.3.
> > >>
> >
back, we should start getting ready to release 1.2
> >> as a rollup. And as per my proposal to manage this release, I'd like
> >> to start off the process of forking 1.2, and making trunk 1.3.
> >>
> >> I've set up a cwiki page for people to land develop
of forking 1.2, and making trunk 1.3.
>>
>> I've set up a cwiki page for people to land development patches that
>> are almost done, to signal their desire that this be included in 1.2 :
>> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
>>
process of forking 1.2, and making trunk 1.3.
>
> I've set up a cwiki page for people to land development patches that
> are almost done, to signal their desire that this be included in 1.2 :
> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
>
> A rou
start off the process of forking 1.2, and making trunk 1.3.
>
> I've set up a cwiki page for people to land development patches that
> are almost done, to signal their desire that this be included in 1.2 :
> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
&g
are almost done, to signal their desire that this be included in 1.2 :
https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
A rough timeline I see for this process would be to fork this Friday
(24th Apr), and then start rolling out RC0 by, say, Wednesday next
week. This would m
+1
Thanks for volunteering Sushanth!
On Mon, Mar 30, 2015 at 10:02 AM, Sushanth Sowmyan wrote:
> Hi Folks,
>
> Given that we landed a bunch of changes in trunk shooting for 1.2
> after 1.1 was forked off, including some metastore changes, I propose
> that we have a feature rollup release of hive
Okay. Makes sense.
Thanks,
Xuefu
On Tue, Mar 31, 2015 at 11:38 AM, Thejas Nair wrote:
> Xuefu,
> Releases such as 1.1.1 are by convention bug fix releases, and only
> include a selected set of important bug fixes that have been applied
> to the release branch (branch-1.1 in this case).
>
> In t
Xuefu,
Releases such as 1.1.1 are by convention bug fix releases, and only
include a selected set of important bug fixes that have been applied
to the release branch (branch-1.1 in this case).
In the 2 months since the creation of branch-1.0, we have around 211
jiras that have been committed in tr
Hi Sushanth,
Thanks for starting this. Rapid releasing is good. However, could you
please provide a list of major changes or enhancement? I'd like to see
whether we are in position to release it as 1.1.1 or 1.2.0.
Thanks,
Xuefu
On Mon, Mar 30, 2015 at 10:02 AM, Sushanth Sowmyan
wrote:
> Hi Fo
Hi Folks,
Given that we landed a bunch of changes in trunk shooting for 1.2
after 1.1 was forked off, including some metastore changes, I propose
that we have a feature rollup release of hive that matches the state
of trunk sooner rather than later. For the timeline, I was thinking
that it'd be id
40 matches
Mail list logo
