[jira] [Commented] (FALCON-1870) Archival lifecycle stage

[ https://issues.apache.org/jira/browse/FALCON-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207872#comment-15207872 ] Ajay Yadava commented on FALCON-1870: - Yes, that makes sense. I highlighted the use c

[jira] [Updated] (FALCON-1870) Archival lifecycle stage

[ https://issues.apache.org/jira/browse/FALCON-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated FALCON-1870: Description: Introduce another lifecycle stage - archival. One very common use case is to support a

[jira] [Updated] (FALCON-1870) Archival lifecycle stage

[ https://issues.apache.org/jira/browse/FALCON-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated FALCON-1870: Summary: Archival lifecycle stage (was: Support Archival to S3 as part of archival lifecycle stage

Re: Reminder : Falcon Bi-Weekly meeting Mar 22nd 9PM Pacific Time (Mar23rd, 9:30 AM IST)

Sorry I meant 9:30 AM IST (Thursday) 9 PM (Wednesday on US west coast). On Wed, Mar 23, 2016 at 10:30 AM, Ajay Yadav wrote: > Hey guys, > > Sorry to miss the meetup, for us the meetup was still showing at 10:30 > IST. I have some important things to discuss regarding 1.0 so that we can > start w

Re: Reminder : Falcon Bi-Weekly meeting Mar 22nd 9PM Pacific Time (Mar23rd, 9:30 AM IST)

Hey guys, Sorry to miss the meetup, for us the meetup was still showing at 10:30 IST. I have some important things to discuss regarding 1.0 so that we can start working on that. Is it possible to reschedule it to tomorrow morning IST 9:30 AM(I guess it will be 9 PM tomorrow morning in US west coas

Re: Meetup on Data Management and Data Movement

Reminder: Meetup this Thursday Thanks Venkat On 3/14/16, 3:43 PM, "Venkat Ranganathan" wrote: >There will be Falcon content and also Sqoop content with user stories on using >Falcon and Sqoop along with other components. Please see the following info > >== >Hadoop Data Management and Da

Re: Reminder : Falcon Bi-Weekly meeting Mar 22nd 9PM Pacific Time (Mar23rd, 9:30 AM IST)

yes. we have missed dst shift. let's cancel it then. Venkat, Can you share the timings for falcon talk and whole meetup over this mail? Thanks. On Mar 23, 2016 9:46 AM, "Venkat Ranganathan" wrote: > Most likely the DST change caught the folks off guard. Let us cancel > today’s sync up. >

Re: Reminder : Falcon Bi-Weekly meeting Mar 22nd 9PM Pacific Time (Mar23rd, 9:30 AM IST)

Most likely the DST change caught the folks off guard. Let us cancel today’s sync up. We have a meetup with lots of Falcon content this Thursday - Don’t miss Thanks Venkat On 3/22/16, 9:10 PM, "Venkat Ramachandran" wrote: >hear music... > >On Tue, Mar 22, 2016 at 9:09 PM, Ying Zheng wro

Re: Reminder : Falcon Bi-Weekly meeting Mar 22nd 9PM Pacific Time (Mar23rd, 9:30 AM IST)

did it get preponed by 1 hour?. we generally have it around 10:30 am IST On Mar 23, 2016 9:40 AM, "Venkat Ramachandran" wrote: > hear music... > > On Tue, Mar 22, 2016 at 9:09 PM, Ying Zheng > wrote: > > > Also waiting. Please let us know when it starts. Thank you. > > > > On 3/22/16, 9:04 PM, "

Re: Reminder : Falcon Bi-Weekly meeting Mar 22nd 9PM Pacific Time (Mar23rd, 9:30 AM IST)

hear music... On Tue, Mar 22, 2016 at 9:09 PM, Ying Zheng wrote: > Also waiting. Please let us know when it starts. Thank you. > > On 3/22/16, 9:04 PM, "Venkat Ranganathan" > wrote: > > >Are we meeting today? Nobody on the call yet > > > > > > > > > > > > > >On 3/21/16, 11:57 AM, "Balu Vellank

Re: Reminder : Falcon Bi-Weekly meeting Mar 22nd 9PM Pacific Time (Mar23rd, 9:30 AM IST)

Also waiting. Please let us know when it starts. Thank you. On 3/22/16, 9:04 PM, "Venkat Ranganathan" wrote: >Are we meeting today? Nobody on the call yet > > > > > > >On 3/21/16, 11:57 AM, "Balu Vellanki Bala" >wrote: > >>Hi Team, >> >>I following items will be discussed in Mar 22nd's Falcon

Re: Reminder : Falcon Bi-Weekly meeting Mar 22nd 9PM Pacific Time (Mar23rd, 9:30 AM IST)

Are we meeting today? Nobody on the call yet On 3/21/16, 11:57 AM, "Balu Vellanki Bala" wrote: >Hi Team, > >I following items will be discussed in Mar 22nd's Falcon bi-weekly meeting. >Please add to the list > > * Falcon spark integration discussion. > * Falcon server safe mode de

[jira] [Commented] (FALCON-1870) Support Archival to S3 as part of archival lifecycle stage

[ https://issues.apache.org/jira/browse/FALCON-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207808#comment-15207808 ] Venkat Ranganathan commented on FALCON-1870: I think the target of archival s

[jira] [Commented] (FALCON-1869) Support HDFS erasure coding (EC) as a data lifecycle phase

[ https://issues.apache.org/jira/browse/FALCON-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207795#comment-15207795 ] Ajay Yadava commented on FALCON-1869: - Big +1. Thanks for taking this up. This was on

[jira] [Updated] (FALCON-1869) Support HDFS erasure coding (EC) as a data lifecycle phase

[ https://issues.apache.org/jira/browse/FALCON-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated FALCON-1869: Labels: lifecycle (was: ) > Support HDFS erasure coding (EC) as a data lifecycle phase > ---

[jira] [Updated] (FALCON-1869) Support HDFS erasure coding (EC) as a data lifecycle phase

[ https://issues.apache.org/jira/browse/FALCON-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated FALCON-1869: Component/s: (was: feed) feed-lifecycle > Support HDFS erasure coding (EC) as

[jira] [Updated] (FALCON-1870) Support Archival to S3 as part of archival lifecycle stage

[ https://issues.apache.org/jira/browse/FALCON-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated FALCON-1870: Component/s: feed-lifecycle > Support Archival to S3 as part of archival lifecycle stage >

[jira] [Updated] (FALCON-1872) Count Based Retention Policies

[ https://issues.apache.org/jira/browse/FALCON-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated FALCON-1872: Component/s: feed-lifecycle > Count Based Retention Policies > -- > >

[jira] [Updated] (FALCON-1872) Count Based Retention Policies

[ https://issues.apache.org/jira/browse/FALCON-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated FALCON-1872: Labels: lifecycle (was: ) > Count Based Retention Policies > -- > >

[jira] [Updated] (FALCON-1871) REST API Revamp

[ https://issues.apache.org/jira/browse/FALCON-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated FALCON-1871: Fix Version/s: 1.0 > REST API Revamp > --- > > Key: FALCON-1871 >

[jira] [Updated] (FALCON-1870) Support Archival to S3 as part of archival lifecycle stage

[ https://issues.apache.org/jira/browse/FALCON-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated FALCON-1870: Labels: lifecycle (was: ) > Support Archival to S3 as part of archival lifecycle stage > -

[jira] [Updated] (FALCON-1870) Support Archival to S3 as part of archival lifecycle stage

[ https://issues.apache.org/jira/browse/FALCON-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated FALCON-1870: Fix Version/s: 1.0 > Support Archival to S3 as part of archival lifecycle stage > -

[jira] [Created] (FALCON-1872) Count Based Retention Policies

Ajay Yadava created FALCON-1872: --- Summary: Count Based Retention Policies Key: FALCON-1872 URL: https://issues.apache.org/jira/browse/FALCON-1872 Project: Falcon Issue Type: New Feature

[jira] [Updated] (FALCON-1872) Count Based Retention Policies

[ https://issues.apache.org/jira/browse/FALCON-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated FALCON-1872: Fix Version/s: 1.0 > Count Based Retention Policies > -- > >

[jira] [Created] (FALCON-1871) REST API Revamp

Ajay Yadava created FALCON-1871: --- Summary: REST API Revamp Key: FALCON-1871 URL: https://issues.apache.org/jira/browse/FALCON-1871 Project: Falcon Issue Type: New Feature Reporter:

[jira] [Created] (FALCON-1870) Support Archival to S3 as part of archival lifecycle stage

Ajay Yadava created FALCON-1870: --- Summary: Support Archival to S3 as part of archival lifecycle stage Key: FALCON-1870 URL: https://issues.apache.org/jira/browse/FALCON-1870 Project: Falcon Iss

[jira] [Commented] (FALCON-870) Retention support delete files/dirs based on modify time or access time

[ https://issues.apache.org/jira/browse/FALCON-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207751#comment-15207751 ] Ajay Yadava commented on FALCON-870: Yes, this will be another policy using lifecycle.

[jira] [Created] (FALCON-1869) Support HDFS erasure coding (EC) as a data lifecycle phase

Venkatesan Ramachandran created FALCON-1869: --- Summary: Support HDFS erasure coding (EC) as a data lifecycle phase Key: FALCON-1869 URL: https://issues.apache.org/jira/browse/FALCON-1869 Pr

[jira] [Commented] (FALCON-870) Retention support delete files/dirs based on modify time or access time

[ https://issues.apache.org/jira/browse/FALCON-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207713#comment-15207713 ] Venkatesan Ramachandran commented on FALCON-870: [~zhaoyunjiong] If you ar

[jira] [Updated] (FALCON-870) Retention support delete files/dirs based on modify time or access time

[ https://issues.apache.org/jira/browse/FALCON-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatesan Ramachandran updated FALCON-870: --- Assignee: (was: Venkatesan Ramachandran) > Retention support delete files/

[jira] [Assigned] (FALCON-870) Retention support delete files/dirs based on modify time or access time

[ https://issues.apache.org/jira/browse/FALCON-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatesan Ramachandran reassigned FALCON-870: -- Assignee: Venkatesan Ramachandran > Retention support delete files/dirs

[jira] [Commented] (FALCON-870) Retention support delete files/dirs based on modify time or access time

[ https://issues.apache.org/jira/browse/FALCON-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207453#comment-15207453 ] Venkatesan Ramachandran commented on FALCON-870: [~ajayyadava] should this

Build failed in Jenkins: Apache-falcon #955

See Changes: [pallavi.rao] FALCON-1852 Make optional input to a process truly optional -- [...truncated 5152 lines...] [INFO] --- findbugs-maven-plugin:3.0.3:check (findbugs-check) @ falcon-webapp

[jira] [Resolved] (FALCON-1827) Status API and summary API are out of sync for just finished instances

[ https://issues.apache.org/jira/browse/FALCON-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-1827. - Resolution: Fixed Fix Version/s: trunk > Status API and summary API are out of sync for ju

[jira] [Resolved] (FALCON-1852) Optional Input for a process not truly optional

[ https://issues.apache.org/jira/browse/FALCON-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao resolved FALCON-1852. - Resolution: Fixed Fix Version/s: trunk > Optional Input for a process not truly optional >

[jira] [Commented] (FALCON-1852) Optional Input for a process not truly optional

[ https://issues.apache.org/jira/browse/FALCON-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205934#comment-15205934 ] ASF GitHub Bot commented on FALCON-1852: Github user asfgit closed the pull reque

[GitHub] falcon pull request: FALCON-1852 Make optional input to a process ...

Github user asfgit closed the pull request at: https://github.com/apache/falcon/pull/73 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl