Skip to content

Add folder/wiki-metadata catalog operations, one-tag-per-branch releases, and a floating alias tag - #32

Merged
oskaresparza merged 4 commits into
developmentfrom
debug_library
Aug 14, 2026
Merged

Add folder/wiki-metadata catalog operations, one-tag-per-branch releases, and a floating alias tag#32
oskaresparza merged 4 commits into
developmentfrom
debug_library

Conversation

@oskaresparza

Copy link
Copy Markdown
Collaborator

Summary
Rename assignwikito/assigntagsto/writemeta2wiki → setwikito/settagsto/setmeta2wiki for naming consistency across the catalog operations API.
Add deletewiki (idempotent wiki removal) and gate gettagsfrom/settagsto to table/view paths only, since folders now use the wiki-embedded metadata scheme (setmeta2wiki/getmetafromwiki) instead of Dremio's native tags.
Add a floating main/staging alias tag in the release workflow that always points at each branch's latest release, so pip install ...@main/...@staging never needs a version lookup (git resolves the branch/tag name collision deterministically in the tag's favor).
Update debugger/debug_run.py to exercise setmeta2wiki and adjust createfolder's sample path.
Test plan
Full test suite passing (227 tests) as of the rename/gating changes
release.yml YAML validated
Confirm the main/staging alias tag behaves as expected once merged and a real release runs

oskaresparza and others added 4 commits August 14, 2026 12:32
… tables/views

- Rename assignwikito/assigntagsto/writemeta2wiki to setwikito/settagsto/
  setmeta2wiki, and readmetafromwiki to getmetafromwiki, for a consistent
  get/set/delete naming scheme across the catalog operations.
- Add deletewiki(path): clears the wiki text on path if it has one.
  Idempotent (missing path or no wiki at all is a no-op), same convention
  as deleteview's DROP VIEW IF EXISTS. Dremio's collaboration API has no
  dedicated delete-wiki endpoint, so this sets the text to empty (same
  workaround deletetags already uses for tags).
- gettagsfrom/settagsto now require path to be a table/view, raising
  CatalogOperationError on a folder — the mirror image of setmeta2wiki/
  getmetafromwiki's folder-only gate, via a new
  CatalogRestClient.is_table_or_view() (checks entityType == "dataset",
  same best-effort semantics as is_folder).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…t release

release.yml: after the real vX.Y.Z[-staging] release is created, force-move
a tag literally named after the branch (main/staging) to that commit and
force-push it — deliberately sharing the branch's own name, since git
resolves that ambiguity in the tag's favor (documented ref-disambiguation
behavior, not a workaround), so `pip install ...@main`/`...@staging` always
means "latest release" going forward.

README: restructure Install / Install in JupyterLab to lead with
@main/@staging (no lookup needed) and offer the exact versioned tag as a
secondary, pin-for-reproducibility option; document the mechanism and its
"refname is ambiguous" warning under Releasing a new version.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Enable run_createfolder() in the call list, point its test folder_path at
an existing parent instead of a nested new_folder/level1 path, and comment
out the unused argparse/device-auth block at the bottom of __main__.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Update run_setmeta2wiki's sample tags, set overwrite=True, and swap the
call list to enable run_setmeta2wiki() instead of run_createfolder().

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@oskaresparza
oskaresparza merged commit f240199 into development Aug 14, 2026
6 checks passed
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.

1 participant