[jira] [Resolved] (GOBBLIN-634) Gobblin as a Service needs to know who sends the request
[ https://issues.apache.org/jira/browse/GOBBLIN-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hung Tran resolved GOBBLIN-634. --- Resolution: Fixed Fix Version/s: 0.14.0 Issue resolved by pull request #2504 [https://github.com/apache/incubator-gobblin/pull/2504] > Gobblin as a Service needs to know who sends the request > > > Key: GOBBLIN-634 > URL: https://issues.apache.org/jira/browse/GOBBLIN-634 > Project: Apache Gobblin > Issue Type: New Feature >Reporter: Kuai Yu >Assignee: Kuai Yu >Priority: Major > Fix For: 0.14.0 > > > Today GaaS doesn't know who sends the request. The aim of this ticket is to > provide a basic abstraction which can be extended by LinkedIn internal > authentication / authorization framework. Those abstractions includes > 1) How to obtain a requester and > 2) How to describe a service a requester > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [DISCUSS] Apache Gobblin 0.14.0 release
+1. Sounds good. Hung. From: Abhishek Tiwari Sent: Monday, November 26, 2018 4:35:56 PM To: dev@gobblin.incubator.apache.org Subject: [DISCUSS] Apache Gobblin 0.14.0 release Hi all, We had a release 2 months back, and since it takes a couple of weeks to vote and release, I propose that we should start a release to maintain our (implicit) quarterly cadence of releases. Also, I volunteer to be the release manager for it. What do you think? The full list of changes (76 resolved Jiras for features, bug fix and improvements) since last release are here: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fissues%2F%3Ffilter%3D12345278data=02%7C01%7Chutran%40linkedin.com%7Ca089c3250fff4867d29b08d654005995%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636788757817849675sdata=7ESLQBZlD0vsfeOKZaM94n1jvCAnMj6vVGWOZC8KN7Q%3Dreserved=0 Regards, Abhishek
[jira] [Created] (GOBBLIN-638) Submit more timing events from GaaS to accurately track flow/job status
Sudarshan Vasudevan created GOBBLIN-638: --- Summary: Submit more timing events from GaaS to accurately track flow/job status Key: GOBBLIN-638 URL: https://issues.apache.org/jira/browse/GOBBLIN-638 Project: Apache Gobblin Issue Type: Improvement Components: gobblin-service Affects Versions: 0.14.0 Reporter: Sudarshan Vasudevan Assignee: Sudarshan Vasudevan Fix For: 0.14.0 We need to emit additional timing events from GaaS (e.g. JOB_ORCHESTRATED, FLOW_COMPILE_FAILED) to accurately track flow and job status. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[DISCUSS] Apache Gobblin 0.14.0 release
Hi all, We had a release 2 months back, and since it takes a couple of weeks to vote and release, I propose that we should start a release to maintain our (implicit) quarterly cadence of releases. Also, I volunteer to be the release manager for it. What do you think? The full list of changes (76 resolved Jiras for features, bug fix and improvements) since last release are here: https://issues.apache.org/jira/issues/?filter=12345278 Regards, Abhishek
[jira] [Resolved] (GOBBLIN-635) Add metadata tags to Gobblin Tracking Event for Azkaban jobs triggered using Gobblin-as-a-Service (GaaS)
[ https://issues.apache.org/jira/browse/GOBBLIN-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hung Tran resolved GOBBLIN-635. --- Resolution: Fixed Issue resolved by pull request #2505 [https://github.com/apache/incubator-gobblin/pull/2505] > Add metadata tags to Gobblin Tracking Event for Azkaban jobs triggered using > Gobblin-as-a-Service (GaaS) > > > Key: GOBBLIN-635 > URL: https://issues.apache.org/jira/browse/GOBBLIN-635 > Project: Apache Gobblin > Issue Type: Improvement > Components: gobblin-service >Affects Versions: 0.14.0 >Reporter: Sudarshan Vasudevan >Assignee: Sudarshan Vasudevan >Priority: Major > Fix For: 0.14.0 > > > Add metadata tags to tracking events for Azkaban jobs triggered using GaaS. > This is needed to accurately track the execution status of GaaS triggered > jobs. The additional tags include information such as: Flow Name, Flow Group, > Flow Execution Id, Job Group, Job Name, Job Execution Id, Job Execution URL > etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GOBBLIN-637) Create dag checkpoint dir on initialization to avoid NPE
[ https://issues.apache.org/jira/browse/GOBBLIN-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hung Tran resolved GOBBLIN-637. --- Resolution: Fixed Issue resolved by pull request #2507 [https://github.com/apache/incubator-gobblin/pull/2507] > Create dag checkpoint dir on initialization to avoid NPE > > > Key: GOBBLIN-637 > URL: https://issues.apache.org/jira/browse/GOBBLIN-637 > Project: Apache Gobblin > Issue Type: Bug > Components: gobblin-service >Affects Versions: 0.14.0 >Reporter: Sudarshan Vasudevan >Assignee: Sudarshan Vasudevan >Priority: Major > Fix For: 0.14.0 > > > FSDagStateStore#getDags() throws a NPE if the dag checkpoint directory does > not exist, since File#listFiles() returns null when the directory does not > exist. The fix eagerly creates the checkpoint directory on instantiation of > FSDagStateStore. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
