You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you supply --force-idsegments with a segment ID that is not meant for auto-archiving the segment will not be archived. Even though to me the force part of the parameter suggests, that the individual setting of the segment would be ignored.
I know you probably don't want to change the naming of command line parameters, since that would be a breaking change.
Therefor i would suggest to at least:
Explain that behaviour in console help core:archive
or
Log segments in the command line that are given to --force-idsegments but skipped because of their individual settings
The text was updated successfully, but these errors were encountered:
The archiving process will only archive segments that have been created with the auto-archiving flag. If you want to see what exactly the archiver is archiving you can provide the debug flag --verbose.
We will consider improving the documentation so it's more clear what will be archived and not.
If you supply
--force-idsegments
with a segment ID that is not meant for auto-archiving the segment will not be archived. Even though to me theforce
part of the parameter suggests, that the individual setting of the segment would be ignored.I know you probably don't want to change the naming of command line parameters, since that would be a breaking change.
Therefor i would suggest to at least:
console help core:archive
or
--force-idsegments
but skipped because of their individual settingsThe text was updated successfully, but these errors were encountered: