-
Notifications
You must be signed in to change notification settings - Fork 21
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.
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
Remove file move ops from FlowETL #946
Labels
Comments
What if you have an ssd and a normal disk? You want to do the read into the
dB from the ssd and the long term storage on the normal disk. Need to at
least move once.
…On Tue, 18 Jun 2019, 13:06 Jonathan Gray ***@***.*** wrote:
At the moment, flowetl spends quite a lot of time moving files around.
There's no great benefit to doing this, given their ingested or not state
is tracked anyway.
Files should stay put.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#946?email_source=notifications&email_token=ACDP2SY3G6IUPIJ45FGWWU3P3C6RRA5CNFSM4HY63X52YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G2DOUKQ>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACDP2S5NIIFD5SMD4GQOCPLP3C6RRANCNFSM4HY63X5Q>
.
|
danwilliams
added a commit
that referenced
this issue
Jun 21, 2019
danwilliams
added a commit
that referenced
this issue
Jun 21, 2019
danwilliams
added a commit
that referenced
this issue
Jun 21, 2019
danwilliams
added a commit
that referenced
this issue
Jun 21, 2019
danwilliams
added a commit
that referenced
this issue
Jun 21, 2019
Linting issues due to previously not having the black pre-commit hook.
danwilliams
added a commit
that referenced
this issue
Jun 21, 2019
danwilliams
added a commit
that referenced
this issue
Jun 21, 2019
danwilliams
added a commit
that referenced
this issue
Jun 21, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment, flowetl spends quite a lot of time moving files around. There's no great benefit to doing this, given their ingested or not state is tracked anyway.
Files should stay put.
The text was updated successfully, but these errors were encountered: