Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Discuss][Core]Support Cache between source and sink #3871

Closed
Tracked by #2729
liugddx opened this issue Jan 5, 2023 · 4 comments
Closed
Tracked by #2729

[Discuss][Core]Support Cache between source and sink #3871

liugddx opened this issue Jan 5, 2023 · 4 comments
Labels
discuss feature New feature stale

Comments

@liugddx
Copy link
Member

liugddx commented Jan 5, 2023 •
edited
Loading

Caching is a very important capability in a data integration platform. But in general, it can be realized with the help of third-party storage. I think this is a very meaningful issue, so we should discuss possible solutions here.

Three-party storage platform：

  • Hdfs/Oss/S3
  • Kafka/Pulsar
  • ...
@liugddx liugddx mentioned this issue Jan 5, 2023
Open
23 tasks
@liugddx liugddx changed the title Support Cache between source and sink [Discuss][Core]Support Cache between source and sink Jan 5, 2023
@liugddx liugddx added discuss feature New feature labels Jan 5, 2023
@2000liux
Copy link

@liugddx Caching needs to consider the cache duration. It seems that hdfs, S3, and Oss are not good choices.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Feb 17, 2023
@github-actions
Copy link

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.

@hailin0 hailin0 reopened this Mar 30, 2023
@github-actions
Copy link

github-actions bot commented Apr 7, 2023

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.

@github-actions github-actions bot closed this as completed Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discuss feature New feature stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hailin0 @2000liux @liugddx