-
Notifications
You must be signed in to change notification settings - Fork 112
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
Extend update docs to mention possible data fragmentation #2164
base: master
Are you sure you want to change the base?
Conversation
@@ -966,9 +966,9 @@ def append( | |||
metadata | |||
Optional metadata to persist along with the new symbol version. Note that the metadata is | |||
not combined in any way with the metadata stored in the previous version. | |||
prune_previous_versions, default=False |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This and validate_index
were causing mkdocs serve -s -a 0.0.0.0:8000
to fail in strict mode with
WARNING - griffe: /home/vasil/Documents/source/ArcticDB/python/arcticdb/version_store/library.py:973: Parameter 'default' does not appear in the function signature
mkdocs parses the function signature and can show the default without mentioning it in the docstring.
581a1ab
to
72fd0f1
Compare
@@ -1099,6 +1099,9 @@ def update( | |||
If dynamic schema is used then data will override everything in storage for the entire index of ``data``. Update | |||
will not keep columns from storage which are not in ``data``. | |||
The update will split the first and last segments in the storage that intersect with 'data'. Therefore, frequent |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
calls to the update
should be calls to update
@@ -1151,6 +1154,25 @@ def update( | |||
2018-01-01 400 | |||
2018-01-03 40 | |||
2018-01-04 4 | |||
Update will split the first and the last segment intersecting with ``data`` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps better to put this as a guide in our docs with more context rather than in the docstring? I don't think most users will have the context about what a segment
is, what read_index
does etc etc and it will all get too long to explain in the docstring
Reference Issues/PRs
What does this implement or fix?
Any other comments?
Checklist
Checklist for code changes...