[
https://issues.apache.org/jira/browse/PIG-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901150#comment-13901150
]
Daniel Dai commented on PIG-3675:
-
The source is in
http://svn.apache.org/viewvc/pig/trunk/
[
https://issues.apache.org/jira/browse/PIG-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901148#comment-13901148
]
Daniel Dai commented on PIG-3675:
-
[~elserj], you can refer to HBaseStorage at
http://pig.a
[
https://issues.apache.org/jira/browse/PIG-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901114#comment-13901114
]
Josh Elser commented on PIG-3675:
-
Bump, [~daijy]?
> Documentation for AccumuloStorage
> --
For 0.13, can we get
PIG-3508 (covered by Daniel's PIG-3545)
Otherwise, "explain" would show pre-optimized logical plan in 0.13.
> I can wrap a 0.12.1 release in a couple of weeks.
>
Great!
Koji
On Feb 13, 2014, at 7:11 PM, Daniel Dai wrote:
> Ok, it seems to leave no choice for a sooner
Issue Subscription
Filter: PIG patch available (12 issues)
Subscriber: pigdaily
Key Summary
PIG-3761Outer join fail on tez
https://issues.apache.org/jira/browse/PIG-3761
PIG-3759CombinerOptimizer should not optimize cogroup case in tez
https://issues.apache
Prashant Kommireddi created PIG-3765:
Summary: Ability to disable Pig commands and operators
Key: PIG-3765
URL: https://issues.apache.org/jira/browse/PIG-3765
Project: Pig
Issue Type: New
[
https://issues.apache.org/jira/browse/PIG-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Dai updated PIG-3529:
Fix Version/s: 0.12.1
We are still using 0.95-SNAPSHOT in pig 0.12.0 release. I am goint to commit
this patc
Ok, it seems to leave no choice for a sooner 0.14.0 release then.
On Thu, Feb 13, 2014 at 3:50 PM, Julien Le Dem wrote:
> We can't use SNAPSHOT releases as dependencies of our official releases.
> They can change and disappear.
> Let's use the official release of hive when it's available.
>
> On
We can't use SNAPSHOT releases as dependencies of our official releases.
They can change and disappear.
Let's use the official release of hive when it's available.
On Feb 13, 2014, at 3:33 PM, Daniel Dai wrote:
> I can also use a hive 0.13.0 SNAPSHOT in PIG-3558, and then switch to
> a released v
I can also use a hive 0.13.0 SNAPSHOT in PIG-3558, and then switch to
a released version later. Seems that's much easier.
On Thu, Feb 13, 2014 at 2:35 PM, Daniel Dai wrote:
> That works. I will roll a 0.14.0 release as soon as Hive 0.13.0 released.
>
> On Thu, Feb 13, 2014 at 2:25 PM, Julien Le D
That works. I will roll a 0.14.0 release as soon as Hive 0.13.0 released.
On Thu, Feb 13, 2014 at 2:25 PM, Julien Le Dem wrote:
> I think it would be OK to release Pig 0.14 soon after if you want new
> features in.
> It's not more work to release 0.14 than 0.13.1 and that keeps the semantic
> v
I think it would be OK to release Pig 0.14 soon after if you want new features
in.
It's not more work to release 0.14 than 0.13.1 and that keeps the semantic
versioning.
On Feb 13, 2014, at 1:29 PM, Daniel Dai wrote:
> Hive-0.13.0 will be release sometime March AFAIK. If we cannot make
> PIG-35
Hive-0.13.0 will be release sometime March AFAIK. If we cannot make
PIG-3558 to Pig 0.13.0, I still want to put in Pig 0.13.1, though it
is a new feature.
Other than those listed Jiras, there are also several unit
tests/system tests failures (eg, TestHBaseStorage) we need to fix.
On Thu, Feb 13,
Sounds good. Do we know a timeline for Hive-0.13 release? If its not too
far, we can try to do Pig-0.13 it a few weeks after that.
So far we have following jiras to wrap up before Pig-0.13 release.
PIG-3591
PIG-3740
PIG-3745
PIG-3347
PIG-3731
PIG-3558
Any other? We can start marking jiras with co
I'd like to get PIG-3558 in, which depends on HIVE-0.13.0 release in
weeks. Otherwise I am fine with a Pig 0.13.0 release.
I can wrap a 0.12.1 release in a couple of weeks.
Thanks,
Daniel
On Thu, Feb 13, 2014 at 3:38 AM, Gianmarco De Francisci Morales
wrote:
> +1 on releasing a 0.13 and if some
Thats great to hear. Surely someone will mentor ON ERROR?
On Thu, Feb 13, 2014 at 3:09 AM, Lorand Bendig wrote:
> Russel,
>
> I'd be keen on working this. Already have some initial code fragments.
>
> -Lorand
>
>
> On 02/13/2014 01:45 AM, Russell Jurney wrote:
>
>> Suggestion: ON ERROR: https:/
I had a partial implementation of Pig mavenization last year (that of
course now is obsolete).
I think it's not as complicated as it sounds, just time consuming.
+1 on the idea, might even have some time to co-mentor.
--
Gianmarco
On 11 February 2014 20:49, Julien Le Dem wrote:
> Some project
+1 on releasing a 0.13 and if somebody feels strongly about releasing a
0.12.1 that fixes PIG-3492 I am +1 on that too.
--
Gianmarco
On 13 February 2014 03:08, Dmitriy Ryaboy wrote:
> So I think we agree that we should branch 0.13 at this point, right?
>
> (and possibly look at releasing an in
Russel,
I'd be keen on working this. Already have some initial code fragments.
-Lorand
On 02/13/2014 01:45 AM, Russell Jurney wrote:
Suggestion: ON ERROR: https://wiki.apache.org/pig/PigErrorHandlingInScripts
On Wed, Feb 12, 2014 at 1:26 PM, Aniket Mokashi wrote:
I have a small prototype
19 matches
Mail list logo
