[
https://issues.apache.org/jira/browse/HBASE-29519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014718#comment-18014718
]
Andor Molnar commented on HBASE-29519:
--------------------------------------
{quote}Do you mean that the user would have a separate copy of the generated
HFiles stored somewhere, which can then be used during restore?
{quote}
Yes. The option is disabled which, to my understand, means that bulkload files
are handled and stored outside of HBase. Meaning it has been created somewhere
else and still has a copy somewhere which is properly backed up already, etc,
etc.
{quote}is this okay or acceptable?
{quote}
Yes, I think it's acceptable. Change of a parameter is effective at and from
the date when it was set. We don't need to go back in time and collect the
missing bulkload files.
Are they supposed to be still available for copy at all? They might have been
compacted away.
> Copy Bulkloaded Files in Continuous Backup
> ------------------------------------------
>
> Key: HBASE-29519
> URL: https://issues.apache.org/jira/browse/HBASE-29519
> Project: HBase
> Issue Type: Sub-task
> Components: backup&restore
> Reporter: Vinayak Hegde
> Assignee: Vinayak Hegde
> Priority: Major
> Labels: pull-request-available
>
> Enhance the continuous backup replication endpoint to detect bulkload
> operations and copy their HFiles to the backup location (e.g., S3).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
