Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

vasil-pashov
Copy link
Collaborator

Reference Issues/PRs

What does this implement or fix?

Any other comments?

Checklist

Checklist for code changes...
  • Have you updated the relevant docstrings, documentation and copyright notice?
  • Is this contribution tested against all ArcticDB's features?
  • Do all exceptions introduced raise appropriate error messages?
  • Are API changes highlighted in the PR description?
  • Is the PR labelled as enhancement or bug so it appears in autogenerated release notes?

@@ -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
Copy link
Collaborator Author

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.

@vasil-pashov vasil-pashov force-pushed the vasil.pashov/extend-update-docs branch from 581a1ab to 72fd0f1 Compare February 3, 2025 16:42
@@ -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
Copy link
Collaborator

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``
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants