[jira] [Resolved] (GOBBLIN-191) Make sure cron scheduler works and tune schedule period
[ https://issues.apache.org/jira/browse/GOBBLIN-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hung Tran resolved GOBBLIN-191. --- Resolution: Fixed Issue resolved by pull request #2042 [https://github.com/apache/incubator-gobblin/pull/2042] > Make sure cron scheduler works and tune schedule period > --- > > Key: GOBBLIN-191 > URL: https://issues.apache.org/jira/browse/GOBBLIN-191 > Project: Apache Gobblin > Issue Type: Bug >Reporter: Abhishek Tiwari >Assignee: Abhishek Tiwari > > Make sure cron scheduler works and tune schedule period. Right not it is not > copying over the required property from FlowSpec to the jobConfig in > ServiceScheduler. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GOBBLIN-189) Add additional information in events for gobblintrackingevent_distcp_ng to show published dataset path
[ https://issues.apache.org/jira/browse/GOBBLIN-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Singh Bora updated GOBBLIN-189: - Sprint: Apache Gobblin 170807 > Add additional information in events for gobblintrackingevent_distcp_ng to > show published dataset path > -- > > Key: GOBBLIN-189 > URL: https://issues.apache.org/jira/browse/GOBBLIN-189 > Project: Apache Gobblin > Issue Type: Task >Reporter: Arjun Singh Bora >Assignee: Arjun Singh Bora > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GOBBLIN-56) StateStoreCleaner and StateStoreChecker do not work with the new StateStore implementations.
[ https://issues.apache.org/jira/browse/GOBBLIN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Tiwari updated GOBBLIN-56: --- Sprint: Apache Gobblin 170807 > StateStoreCleaner and StateStoreChecker do not work with the new StateStore > implementations. > > > Key: GOBBLIN-56 > URL: https://issues.apache.org/jira/browse/GOBBLIN-56 > Project: Apache Gobblin > Issue Type: Bug >Reporter: Joel Baranick >Assignee: Issac Buenrostro > > *Github Url* : https://github.com/linkedin/gobblin/issues/1560 > *Github Reporter* : [~jbaranick] > *Github Created At* : 2017-01-18T18:16:21Z > *Github Updated At* : 2017-01-18T18:16:46Z > h3. Comments > > [~jbaranick] wrote on 2017-01-18T18:16:46Z : @htran1 Here is the issue we > discussed. > > *Github Url* : > https://github.com/linkedin/gobblin/issues/1560#issuecomment-273555840 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (GOBBLIN-194) NPE in BaseDataPublisher if writer partitions are enabled and metadata filename is not set
[ https://issues.apache.org/jira/browse/GOBBLIN-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Tiwari reassigned GOBBLIN-194: --- Assignee: Eric Ogren > NPE in BaseDataPublisher if writer partitions are enabled and metadata > filename is not set > -- > > Key: GOBBLIN-194 > URL: https://issues.apache.org/jira/browse/GOBBLIN-194 > Project: Apache Gobblin > Issue Type: Bug >Reporter: Eric Ogren >Assignee: Eric Ogren > > If writer partitions are enabled and metadata filename is not set, there will > be a NullPointerException on BaseDataPublisher:471. The code is trying to > call new Path(directory, null) which blows up. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GOBBLIN-194) NPE in BaseDataPublisher if writer partitions are enabled and metadata filename is not set
Eric Ogren created GOBBLIN-194: -- Summary: NPE in BaseDataPublisher if writer partitions are enabled and metadata filename is not set Key: GOBBLIN-194 URL: https://issues.apache.org/jira/browse/GOBBLIN-194 Project: Apache Gobblin Issue Type: Bug Reporter: Eric Ogren If writer partitions are enabled and metadata filename is not set, there will be a NullPointerException on BaseDataPublisher:471. The code is trying to call new Path(directory, null) which blows up. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Open Source Apache Sprint : Apache Gobblin 170807
Hi all, I have setup a bi-weekly Open Source Sprint process to track our overall progress and who is working on what here: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=196=GOBBLIN=planning.nodetail Current Sprint Start Date: 7th August, 2017 Current Sprint Duration: 2 weeks *Contributors:* 1. Please change the assignee for the JIRAs you are interested in working on this bi-weekly sprint to yourself; and update its status on the Sprint dashboard as you make progress. 2. Please review the backlog and let me know if you think that any JIRA should be of higher / lower priority than it is right now. *Contributors / **Committers / Mentors: * Please let me know if you have any suggestions around the Sprint model? Or if there are any objections? If not, then we can continue to use it for a while to see how it fits our open source / distributed working style. *Notes:* 1. If you have assigned any JIRA to yourself for the Sprint, it is NOT absolutely necessary that you deliver on it. If you at a later date think that you may not be able to spare cycles for it then please change it to un-assigned as soon as possible (so that someone else can pick it up if they are interested). 2. If the JIRA is about any design / complicated code then its worth discussing the notes and idea on the JIRA and / or on this mailing list before writing down the whole code. 3. You are not alone, please feel free to ask questions if you have any doubts. 4. If Sprint model works well for us, we will also try to align future release to it. 5. The intention of this bi-weekly Sprint is to put a light-weight structure to overall development of Gobblin and NOT to add several process layers. Hence, it is okay to add any JIRA to the Sprint in the middle of the sprint if you are willing to work on it. Regards, Abhishek
