[
https://issues.apache.org/jira/browse/GOBBLIN-1967?focusedWorklogId=892751&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-892751
]
ASF GitHub Bot logged work on GOBBLIN-1967:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Nov/23 20:22
Start Date: 28/Nov/23 20:22
Worklog Time Spent: 10m
Work Description: Will-Lo opened a new pull request, #3838:
URL: https://github.com/apache/gobblin/pull/3838
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-1967
### Description
- [ ] Here are some details about my PR, including screenshots (if
applicable):
GaaS has datanodes for HTTP, SFTP, and HDFS/Table varients. However, in some
scenarios we want a generic identifier for an external ingress/egress flow
running in GaaS. Reason being is that there are some usecases that can be very
generic and we want to avoid adapting these flows to the opinionated setup of
GaaS, while maintaining compatibility.
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
### 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"
Issue Time Tracking
-------------------
Worklog Id: (was: 892751)
Remaining Estimate: 0h
Time Spent: 10m
> Add data node for generic external ingress egress
> -------------------------------------------------
>
> Key: GOBBLIN-1967
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1967
> Project: Apache Gobblin
> Issue Type: Improvement
> Components: gobblin-service
> Reporter: William Lo
> Assignee: Abhishek Tiwari
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> GaaS has datanodes for HTTP, SFTP, and HDFS/Table varients. However, in some
> scenarios we want a generic identifier for an external ingress/egress flow
> running in GaaS. Reason being is that there are some usecases that can be
> very generic and we want to avoid adapting these flows to the opinionated
> setup of GaaS, while maintaining compatibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)