join
PartitionFilterOptimization, but could we make sure that other valid partitions
can be pushdown to LOAD operation?
> Pig 0.11 with HCatLoader partition filter does not push down valid conditions
> -
>
>
[
https://issues.apache.org/jira/browse/PIG-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated PIG-3594:
-
Summary: Pig 0.11 with HCatLoader partition filter does not push down valid
conditions (was: Pig with HCatLoader
was failing only with LIMIT as LimitAdjuster
was not setting the signature.
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
> Key: PIG-3222
>
base for Pig 0.11. But still the query
fails. I succeeds in Pig 0.12. I have asked Rohini if she has an idea on this.
Thanks again
Viraj
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCa
[
https://issues.apache.org/jira/browse/PIG-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887242#comment-13887242
]
Daniel Dai commented on PIG-3222:
-
PIG-3267 checked into Pig 0.11 branch (but no fur
[
https://issues.apache.org/jira/browse/PIG-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887216#comment-13887216
]
Viraj Bhat commented on PIG-3222:
-
Hi Feng,
Thanks for finding this error in Pig 0.11
test trunk.
> Macros that work in Pig 0.11 fail in Pig 0.12 :(
>
>
> Key: PIG-3630
> URL: https://issues.apache.org/jira/browse/PIG-3630
> Project: Pig
> Issue Type: Bug
>
ack to you...
> Macros that work in Pig 0.11 fail in Pig 0.12 :(
>
>
> Key: PIG-3630
> URL: https://issues.apache.org/jira/browse/PIG-3630
> Project: Pig
> Issue Type: Bug
&g
sing register statements. It does work in
11 if you work around the Avro stuff. Ok, now we have something to look at...
> Macros that work in Pig 0.11 fail in Pig 0.12 :(
>
>
> Key: PIG-3630
>
Do you have something that works in 11 but fails in 12?
> Macros that work in Pig 0.11 fail in Pig 0.12 :(
>
>
> Key: PIG-3630
> URL: https://issues.apache.org/jira/browse/PIG-3630
>
3630
Reproducible test case there. You will have to change the path to
Piggybank.jar, $HOME doesn't work in interactive mode so I don't use it.
> Macros that work in Pig 0.11 fail in Pig 0.12 :(
>
>
> Key: PIG-3630
&g
g version 0.12.1-SNAPSHOT (r1552124)
compiled Dec 18 2013, 14:00:21
Back to you to get a reproducible test case
> Macros that work in Pig 0.11 fail in Pig 0.12 :(
>
>
> Key: PIG-3630
> URL: https:
); at the end of your load.
> Macros that work in Pig 0.11 fail in Pig 0.12 :(
>
>
> Key: PIG-3630
> URL: https://issues.apache.org/jira/browse/PIG-3630
> Project: Pig
> Issue T
mails unknown.
(this is the same in both pig 0.11 and pig 0.12).
Can you provide a simple reproducible use case that doesn't involve Avro, etc?
Can you share what debugging you've done so far?
> Macros that work in Pig 0.11 fail in Pig 0.12 :(
> -
http://hortonworks.com/blog/pig-macro-for-tf-idf-makes-topic-summarization-2-lines-of-pig/
> Macros that work in Pig 0.11 fail in Pig 0.12 :(
>
>
> Key: PIG-3630
> URL: https://issues.apache.org/j
ield called tf_idf. Could you post a fully
reproducible test case?
> Macros that work in Pig 0.11 fail in Pig 0.12 :(
>
>
> Key: PIG-3630
> URL: https://issues.apache.org/jira/browse/PIG-3630
>
ttps://github.com/rjurney/Agile_Data_Code/blob/master/ch07/pig/ntfidf.macro
> Macros that work in Pig 0.11 fail in Pig 0.12 :(
>
>
> Key: PIG-3630
> URL: https://issues.apache.org/jira/browse/PIG-3630
&g
runt - ERROR
1025:
at expanding macro 'tf_idf' (per_business.pig:9)
Invalid field projection. Projected
field [tf_idf] does not exist in schema:
business_id:chararray,token:chararray,term_freq:double,num_docs_with_token:long.
> Macros that work in Pig 0.11
Russell Jurney created PIG-3630:
---
Summary: Macros that work in Pig 0.11 fail in Pig 0.12 :(
Key: PIG-3630
URL: https://issues.apache.org/jira/browse/PIG-3630
Project: Pig
Issue Type: Bug
eems that the breakage was
caused by this bug and the UDFContext error was just the red herring. Please
close this bug when the patch is merged. We can create a separate bug about the
multi-instantiation. Thanks a lot [~daijy]!
> New UDFContextSignature assignments in Pig 0.11
anks [~daijy]! I will try
the original query with the new version later.
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
> Key: PIG-3222
>
gt; New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
> Key: PIG-3222
> URL: https://issues.apache.org/jira/browse/PIG-3222
> Project: Pig
; PIG-3267-1.patch
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
> Key: PIG-3222
> URL: https://issues.apac
gt; New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
> Key: PIG-3222
> URL: https://issues.apache.org/jira/browse/PIG-3222
> Project
you using Apache released
version?
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
> Key: PIG-3222
> URL: https://issues.apache.
ried both pig-0.11 and
pig-0.12 and the patch doesn't apply cleanly. Right now I just manually added
the code on pig-0.11 and see if it works.
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalo
atch.
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
> Key: PIG-3222
> URL: https://issues.apache.org/jira/browse/PIG-3222
>
rror message. I open a separate
ticket PIG-3267 for it. Not sure why I cannot reproduce your error, but can you
try the patch?
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCa
ure assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
> Key: PIG-3222
> URL: https://issues.apache.org/jira/browse/PIG-3222
> Project: Pig
>
.log
2013-04-02 20:03:45,642 [Thread-5] INFO
org.apache.hcatalog.common.HiveClientCache - Cleaning up hive client cache in
ShutDown hook
{noformat}
> New UDFContextSignature assignments in Pig 0.11 break
parameters for the
call. The left most [N] indicates the unique instantiation id.
Let me rerun the query using HCatStorer directly to reproduce the issue.
> New UDFContextSignature assignments in Pig 0.11 breaks HC
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
> Key: PIG-3222
> URL: https://issues.apache.org/jira/browse/PIG-3222
> P
nique, (if not, we can enforce it in the normalization process), the
signature for every LoadFunc and StoreFunc will be unique and can be
constructed in a consistent way in both the frontend and backend.
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
> Key: PIG-3222
> URL: https://issues.apache.org/jira/browse/PIG-3222
> Project: Pig
imes: setStoreLocation,
checkOutputSpecs and commitJob. HCatStorer needs to cache the results in
UDFContext.
However, it doesn't seems to be a regression. I see the same behavior in
0.9/0.10.
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalo
how to fix this? Can we get away from
the whole instantiation thing, and maybe keep an object registry?
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
>
rmat
[1]setStoreLocation(testdb.samples,Job@603950563)
[2]setStoreFuncUDFContextSignature(samples_1-6)
[2]setStoreLocation(testdb.samples,Job@1203999762)
[2]getOutputFormat
{noformat}
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCa
with signature: samples_1-6
...
{noformat}
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
> Key: PIG-3222
> URL: https://issues.apa
ng
com.twitter.pig.test('org.apache.hcatalog.pig.HCatStorer',
'part_dt=20130101T01Z');
{noformat}
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
>
for the StoreFunc.
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
> Key: PIG-3222
> URL: https://issues.apache.org/jira/
d it showed that the same StoreFunc
is called with different signatures. I will see if I can come up with a simple
example.
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCa
r, I didn't see the issue.
Can you provide more details?
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
> Key: PIG-3222
>
>>>>> On Feb 20, 2013, at 11:33 AM, Russell Jurney wrote:
> > >> >>>>>>
> > >> >>>>>>> Isn't the point of an RC to find and fix bugs like these>
> > >> >>>>>>>
> > >> >&
gt;>
> >> >>>>>>>
> >> >>>>>>> On Wed, Feb 20, 2013 at 11:31 AM, Bill Graham <
> >> >>> billgra...@gmail.com>
> >> >>>>>> wrote:
> >> >>>>>>>
> >>
;> >>> billgra...@gmail.com>
>> >>>>>> wrote:
>> >>>>>>>
>> >>>>>>>> Regarding Pig 11 rc2, I propose we continue with the current
>> >> vote
>> >>>> as is
>> >>>>>>>> (which closes today EOD). Patches for 0.2
ple still running 0.20.2
> >> Clusters.
> >>>> If
> >>>>>>>>> you really have lots of data stored on HDFS and a continuously
> >>> busy
> >>>>>>>>> cluster, an upgrade is nothing you do "jus
>>>>>
>>>>>>>> On Wed, Feb 20, 2013 at 9:24 AM, Olga Natkovich <
>>>> onatkov...@yahoo.com
>>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I agree that supporting as much
, Olga Natkovich <
>>>> onatkov...@yahoo.com
>>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I agree that supporting as much as we can is a good goal. The
>>>> issue is
>>>>>>>>
gt; > >> On Wed, Feb 20, 2013 at 9:24 AM, Olga Natkovich <
> > > > onatkov...@yahoo.com
> > > > > > >>> wrote:
> > > > > > >>
> > > > > > >>> I agree that supporting as much as we can is a goo
t;> who
> > > > > >>> is going to be testing against all these versions? We found the
> > > issues
> > > > > >>> under discussion because of a customer report, not because we
> > > > > >> consistently
> > >
versions. Perhaps when we decide which versions
> to
> > > > >> support
> > > > >>> for next release we need also to agree who is going to be testing
> > and
> > > > >>> maintaining compatibility with a particular ve
kers for the 0.11 release I think.
Won't do that again.
> No docs for CUBE in Pig 0.11 :(
> ---
>
> Key: PIG-3220
> URL: https://issues.apache.org/jira/browse/PIG-3220
> Project: Pig
ers since they don't block projects from being
able to make progress (though they certainly make it easier to make progress).
> No docs for CUBE in Pig 0.11 :(
> ---
>
> Key: PIG-3220
> URL: https://issu
ore, when are they and aren't they
blockers?
> No docs for CUBE in Pig 0.11 :(
> ---
>
> Key: PIG-3220
> URL: https://issues.apache.org/jira/browse/PIG-3220
> Project: Pig
> Is
that reproduces the Pig bug
without HCatalog?
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
> Key: PIG-3222
> URL: https:
20130101T01Z');
{noformat}
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---
>
> Key: PIG-3222
> URL: https://issues.apache.or
[
https://issues.apache.org/jira/browse/PIG-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy V. Ryaboy updated PIG-3220:
---
Priority: Major (was: Blocker)
> No docs for CUBE in Pig 0
not blockers as blockers.
> No docs for CUBE in Pig 0.11 :(
> ---
>
> Key: PIG-3220
> URL: https://issues.apache.org/jira/browse/PIG-3220
> Project: Pig
> Issue Type: Bug
&g
Feng Peng created PIG-3222:
--
Summary: New UDFContextSignature assignments in Pig 0.11 breaks
HCatalog.HCatStorer
Key: PIG-3222
URL: https://issues.apache.org/jira/browse/PIG-3222
Project: Pig
://issues.apache.org/jira/browse/PIG-2765?focusedCommentId=13427021&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13427021
> No docs for CUBE in Pig 0.11 :(
> ---
>
> Key: PIG-3220
>
eady for 0.11.1 by Prasanth and Bill.
https://issues.apache.org/jira/browse/PIG-3202
> No docs for CUBE in Pig 0.11 :(
> ---
>
> Key: PIG-3220
> URL: https://issues.apache.org/jira/browse/PIG-3220
>
Russell Jurney created PIG-3220:
---
Summary: No docs for CUBE in Pig 0.11 :(
Key: PIG-3220
URL: https://issues.apache.org/jira/browse/PIG-3220
Project: Pig
Issue Type: Bug
Affects Versions
I pulled together some of the highlights of the pig 0.11 release on the
Apache Pig blog (which now officially exists!):
https://blogs.apache.org/pig/
D
[
https://issues.apache.org/jira/browse/PIG-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Graham updated PIG-3194:
-
Affects Version/s: 0.11
> Pig 0.11 candidate 2: Changes to ObjectSerializer.java break compatibil
and
> > > >>> maintaining compatibility with a particular version.
> > > >>>
> > > >>> For instance since Hadoop 23 compatibility is important for us at
> Yahoo
> > > >> we
> > > >>> have been maintaining compatibility
ibility is important for us at Yahoo
> > >> we
> > >>> have been maintaining compatibility with this version for 0.9, 0.10 and
> > >>> will do the same for 0.11 and going forward. I think we would need
> > others
> > >>> to step in and
is version for 0.9, 0.10 and
> >>> will do the same for 0.11 and going forward. I think we would need
> others
> >>> to step in and claim the versions of their interest.
> >>>
> >>> Olga
> >>>
> >>>
> >>> __
gt;> we
>>> have been maintaining compatibility with this version for 0.9, 0.10 and
>>> will do the same for 0.11 and going forward. I think we would need others
>>> to step in and claim the versions of their interest.
>>>
>>> Olga
>>>
>>
oing forward. I think we would need others
> > to step in and claim the versions of their interest.
> >
> > Olga
> >
> >
> > ________
> > From: Kai Londenberg
> > To: dev@pig.apache.org
> > Sent: Wednesday, February 20, 2013 1:51 AM
> > Subject: Re: pig 0.11 c
same for 0.11 and going forward. I think we would need others
> to step in and claim the versions of their interest.
>
> Olga
>
>
>
> From: Kai Londenberg
> To: dev@pig.apache.org
> Sent: Wednesday, February 20, 2013 1:51 AM
> Subject:
0.11 and going forward. I think we would need others to step in and
claim the versions of their interest.
Olga
From: Kai Londenberg
To: dev@pig.apache.org
Sent: Wednesday, February 20, 2013 1:51 AM
Subject: Re: pig 0.11 candidate 2 feedback: Several problems
;> which Hadoop versions it will support. I guess the main question is how
>>> we
>>>> decide on this. Perhaps we should say that Pig no longer supports older
>>>> Hadoop versions once the newer one is out for at least 6-12 month to make
>>>> sure it is stable. I don't think we can sup
versions it will support. I guess the main question is
> how
> >> we
> >> > decide on this. Perhaps we should say that Pig no longer supports
> older
> >> > Hadoop versions once the newer one is out for at least 6-12 month to
> make
> >> > sure it is stable. I don't think we can sup
n this. Perhaps we should say that Pig no longer supports older
>> > Hadoop versions once the newer one is out for at least 6-12 month to make
>> > sure it is stable. I don't think we can support old versions
>> indefinitely.
>> > It is in everybody's interest
can support old versions
> indefinitely.
> > It is in everybody's interest to keep moving forward.
> >
> > Olga
> >
> >
> > ____
> > From: Prashant Kommireddi
> > To: dev@pig.apache.org
> > Sent: Tuesday, February 19, 2013 10:57 AM
>
27;t think we can support old versions indefinitely.
> It is in everybody's interest to keep moving forward.
>
> Olga
>
>
>
> From: Prashant Kommireddi
> To: dev@pig.apache.org
> Sent: Tuesday, February 19, 2013 10:57 AM
> Subject:
it is stable. I
don't think we can support old versions indefinitely. It is in everybody's
interest to keep moving forward.
Olga
From: Prashant Kommireddi
To: dev@pig.apache.org
Sent: Tuesday, February 19, 2013 10:57 AM
Subject: Re: pig 0.11 c
to me.
> >
> > thanks,
> > Bill
> >
> > On Mon, Feb 18, 2013 at 2:27 AM, Kai Londenberg <
> > kai.londenb...@googlemail.com> wrote:
> >
> > > Hi,
> > >
> > > I just subscribed to the dev mailing list in order to give you som
IG-3144>)
> ready, which seems like the most pressing of the three to me.
>
> thanks,
> Bill
>
> On Mon, Feb 18, 2013 at 2:27 AM, Kai Londenberg <
> kai.londenb...@googlemail.com> wrote:
>
> > Hi,
> >
> > I just subscribed to the dev mailing list in or
ubscribed to the dev mailing list in order to give you some
> feedback on pig 0.11 candidate 2.
>
> The following three issues are currently present in 0.11 candidate 2:
>
> https://issues.apache.org/jira/browse/PIG-3144 - 'Erroneous map entry
> alias resolution leading to "
of pit itself.
> Pig 0.11 candidate 2: Changes to ObjectSerializer.java break compatibility
> with Hadoop 0.20.2
> -
>
> Key: PIG-3194
> URL
w=markup
> Pig 0.11 candidate 2: Changes to ObjectSerializer.java break compatibility
> with Hadoop 0.20.2
> -
>
> Key: PIG-3194
> URL: http
much.
Need to get to the bottom of why 1.4 is still getting brought in, though.
> Pig 0.11 candidate 2: Changes to ObjectSerializer.java break compatibility
> with Had
odec 1.3 (is that what hadoop 2 uses?)
then #2 seems like a no-brainer to me
> Pig 0.11 candidate 2: Changes to ObjectSerializer.java break compatibility
> with Had
r example pig.org.apache.commons.codec or something like
that.
> Pig 0.11 candidate 2: Changes to ObjectSerializer.java break compatibility
> with Hadoop 0.20.2
> -
>
>
he.org/jira/browse/PIG-2875
> > [2.2] https://issues.apache.org/jira/browse/PIG-2579
> >
> >
> >
> >
> >
> >
> > On Sun, Feb 17, 2013 at 5:29 PM, Russell Jurney <
> russell.jur...@gmail.com
> > >wrote:
> >
> > > A
mons codec 1.3? Do the newer versions of
Hadoop still use that version of commons codec?
> Pig 0.11 candidate 2: Changes to ObjectSerializer.java break compatibility
> with Had
Hi,
I just subscribed to the dev mailing list in order to give you some
feedback on pig 0.11 candidate 2.
The following three issues are currently present in 0.11 candidate 2:
https://issues.apache.org/jira/browse/PIG-3144 - 'Erroneous map entry
alias resolution leading to "Duplic
Kai Londenberg created PIG-3194:
---
Summary: Pig 0.11 candidate 2: Changes to ObjectSerializer.java
break compatibility with Hadoop 0.20.2
Key: PIG-3194
URL: https://issues.apache.org/jira/browse/PIG-3194
issues.apache.org/jira/browse/PIG-2579
>
>
>
>
>
>
> On Sun, Feb 17, 2013 at 5:29 PM, Russell Jurney >wrote:
>
> > Anyone up for doing a release 3-4 months after Pig 0.11, the way I think
> it
> > is 'supposed' to work? I want the new AvroStora
a/browse/PIG-2875
> [2.2] https://issues.apache.org/jira/browse/PIG-2579
>
>
>
>
>
>
> On Sun, Feb 17, 2013 at 5:29 PM, Russell Jurney
> wrote:
>
>> Anyone up for doing a release 3-4 months after Pig 0.11, the way I think it
>> is 'supposed' to
org/jira/browse/PIG-2875
[2.2] https://issues.apache.org/jira/browse/PIG-2579
On Sun, Feb 17, 2013 at 5:29 PM, Russell Jurney wrote:
> Anyone up for doing a release 3-4 months after Pig 0.11, the way I think it
> is 'supposed' to work? I want the new AvroStorage in my b
of Hadoop so that
>> there is a combination of release branches that can be documented to
>> accomplish this goal for devs/users.
>>
>> Thanks!
>>
>> John
>>
>> -Original Message-
>> From: Daniel Dai [mailto:da...@hortonworks.com]
>&
ginal Message-
> From: Daniel Dai [mailto:da...@hortonworks.com]
> Sent: Monday, January 21, 2013 1:34 PM
> To: dev@pig.apache.org
> Subject: Re: Getting Pig 0.11 out
>
> I am fine moving PIG-2973 to 0.12. I probably will check several in before
> 0.11 release, but this is not a blo
ed to accomplish this goal
for devs/users.
Thanks!
John
-Original Message-
From: Daniel Dai [mailto:da...@hortonworks.com]
Sent: Monday, January 21, 2013 1:34 PM
To: dev@pig.apache.org
Subject: Re: Getting Pig 0.11 out
I am fine moving PIG-2973 to 0.12. I probably will check several in before
ssue and it's subtasks account for 11 of the 15 issues. Can we move
>> this to Pig 0.12?
>>
>> - PIG-2972: Umbrella ticket for test failures in 0.11/trunk
>> This one has 4 unassigned open subtasks which are not tagged with 0.11. Any
>> takers?
>>
>> - PIG-
> - PIG-3109: License headers. This is a easy blocker to tackle.
>
> - PIG-2756: Pig 0.11 documentation umbrella. Sub-tasks are complete, no
> work required here.
>
> - PIG-3105: Fix TestJobSubmission unit test failure. Patch available,
> should be easy to verify.
>
>
> thanks,
> Bill
signature.asc
Description: Digital signature
. Any
takers?
- PIG-3109: License headers. This is a easy blocker to tackle.
- PIG-2756: Pig 0.11 documentation umbrella. Sub-tasks are complete, no
work required here.
- PIG-3105: Fix TestJobSubmission unit test failure. Patch available,
should be easy to verify.
thanks,
Bill
Olga
>>>
>>>
>>>
>>> - Original Message -
>>> From: Olga Natkovich
>>> To: "dev@pig.apache.org" ; Olga Natkovich
>>>
>>> Cc:
>>> Sent: Tuesday, October 30, 2012 9:07 AM
>>> Subject: Re: Pig 0.11
>
Olga Natkovich
>> To: "dev@pig.apache.org" ; Olga Natkovich
>>
>> Cc:
>> Sent: Tuesday, October 30, 2012 9:07 AM
>> Subject: Re: Pig 0.11
>>
>> We are down to 45 tickets. Thanks for everybody who helped with the cleanup.
>> We only have a
1 - 100 of 142 matches
Mail list logo
