Skip to content

Enhance entrylinks export and import with human-readable format - #155

Draft
ramadarsan-ramd wants to merge 8 commits into
GoogleCloudPlatform:mainfrom
ramadarsan-ramd:feature/human-readable-entrylinks-format
Draft

Enhance entrylinks export and import with human-readable format#155
ramadarsan-ramd wants to merge 8 commits into
GoogleCloudPlatform:mainfrom
ramadarsan-ramd:feature/human-readable-entrylinks-format

Conversation

@ramadarsan-ramd

Copy link
Copy Markdown
  • Standardize Google Sheet schema to 4 columns: [Entry link type, Source, Column, Target]
  • Format term references as human-readable 4-part strings: ...
  • Format data asset references using Fully Qualified Names (e.g. bigquery:project.dataset.table) and column names
  • Implement direct API resolution and in-memory caching to eliminate eventual consistency lag and honor 500 QPM rate limits
  • Maintain full backward compatibility for legacy full-entry-name sheets
  • Add unit test coverage (198 tests passing) and update export/import documentation

Bug: b/535068769

…man-readable format

- Standardize Google Sheet schema to 4 columns: [Entry link type, Source, Column, Target]
- Format term references as human-readable 4-part strings: <project>.<location>.<glossaryDisplayName>.<termDisplayName>
- Format data asset references using Fully Qualified Names (e.g. bigquery:project.dataset.table) and column names
- Implement direct API resolution and in-memory caching to eliminate eventual consistency lag and honor 500 QPM rate limits
- Maintain full backward compatibility for legacy full-entry-name sheets
- Add unit test coverage (198 tests passing) and update export/import documentation

Bug: b/535068769
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