You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2018/07/26 21:51:04 UTC
[GitHub] pdeva edited a comment on issue #6046: allow 'secondary' deep
storage to easily allow deep storage migration
pdeva edited a comment on issue #6046: allow 'secondary' deep storage to easily allow deep storage migration
URL: https://github.com/apache/incubator-druid/issues/6046#issuecomment-408246182
i am a little confused.
>Old segments continue to be fetched from S3 when necessary.
How will druid know about S3 in the first place, now that you have specified GC as the deep storage?
>Update metadata store payloads for the old segments to use GC loadSpecs
I assume 'metadata store payloads' refers to data in the metadata storage.
Assuming that, it seems this requires manually modifying the data in metadata storage.
Not only is this undocumented, this could lead to corruption of the metadata if done incorrectly.
There should be some tooling for this.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org