You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@gobblin.apache.org by GitBox <gi...@apache.org> on 2021/07/14 20:46:23 UTC

[GitHub] [gobblin] autumnust commented on pull request #3329: [GOBBLIN-1484]Make Gobblin metadata writer be able to support schema source DB

autumnust commented on pull request #3329:
URL: https://github.com/apache/gobblin/pull/3329#issuecomment-880197133


   No additional comments beyond what @sv2000  mentioned above. But a broader question to deal with this kind of feature is: What should be the right way to specify "lineage" of schema between different tables? Is setting source.db in GMCE a right approach (which means you need to set this in a specific application's GMCE if you expect the application itself doesn't carry the schema during runtime, for example compaction), or is there something broader missing in the overall picture. 


-- 
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