[jira] [Work logged] (GOBBLIN-1490) Make metadata pipeline to support consume GMCE emitted from different cluster

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GOBBLIN-1490?focusedWorklogId=622818&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-622818 ]

ASF GitHub Bot logged work on GOBBLIN-1490:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 15/Jul/21 01:22
            Start Date: 15/Jul/21 01:22
    Worklog Time Spent: 10m 
      Work Description: ZihanLi58 opened a new pull request #3331:
URL: https://github.com/apache/gobblin/pull/3331


   
   
   Dear Gobblin maintainers,
   
   Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
   
   
   ### JIRA
   - [ ] My PR addresses the following [Gobblin JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-1490
   
   
   ### Description
   - [ ] Here are some details about my PR, including screenshots (if applicable):
   In some use case, we may run data pipeline on different clusters but those clusters share the same file system. And in those case, we will want the metadata pipeline to be able to consume all the records even they are running on different clusters. Also make the cluster name for GMCE be configurable so that we don't need to change the accepted cluster names when cluster name itself changes 
   
   ### Tests
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   unit test
   
   ### Commits
   - [ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
       1. Subject is separated from body by a blank line
       2. Subject is limited to 50 characters
       3. Subject does not end with a period
       4. Subject uses the imperative mood ("add", not "adding")
       5. Body wraps at 72 characters
       6. Body explains "what" and "why", not "how"
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@gobblin.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 622818)
    Remaining Estimate: 0h
            Time Spent: 10m

> Make metadata pipeline to support consume GMCE emitted from different cluster
> -----------------------------------------------------------------------------
>
>                 Key: GOBBLIN-1490
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1490
>             Project: Apache Gobblin
>          Issue Type: New Feature
>            Reporter: Zihan Li
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In some use case, we may run data pipeline on different clusters but those clusters share the same file system. And in those case, we will want the metadata pipeline to be able to consume all the records even they are running on different clusters.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)