-
Notifications
You must be signed in to change notification settings - Fork 1
feat: sitemapextractor #14
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…min and extractor APIs
… timeout handling
…ance documentation
…c with optional key-value store removal
Co-authored-by: Copilot <[email protected]>
…eter alias in upload_source function
…-library into onapitorulethemall
…ns in upload_source function
…-library into onapitorulethemall
…e unused managed_page_summary_enhancer module
…r DefaultSourceUploader to use it refactor: update JSON serialization in ExtractionParameters, ExtractionRequest, InformationPiece, and KeyValuePair models refactor: remove unused test files for confluence and thread management integration
…load_source function
…tionPiece classes
…ece classes to support sitemap extraction
…andle JSON header templates
…mprove parameter handling
…rsing and meta functions
…ustom parsing functions
…ved configurability
…oved changelog generation
MirUlr
approved these changes
Jun 11, 2025
extractor-api-lib/src/extractor_api_lib/impl/extractors/sitemap_extractor.py
Show resolved
Hide resolved
extractor-api-lib/src/extractor_api_lib/impl/utils/sitemap_extractor_utils.py
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces significant updates to the
admin-api-lib
andextractor-api-lib
documentation and OpenAPI specification. The changes include renaming endpoints and classes for improved clarity, expanding functionality to support non-file sources, and updating the OpenAPI specification to version 3.1.0. Below is a categorized summary of the most important changes:Endpoint and Class Renaming
/upload_documents
to/upload_file
for file uploads and/load_confluence
to/upload_source
for non-file source uploads. Updated descriptions to reflect the changes. [1] [2]README.md
to align with the new endpoint names, e.g.,document_uploader
tofile_uploader
andconfluence_loader
tosource_uploader
.Support for Non-File Sources
/extract_from_confluence
with/extract_from_source
to generalize data extraction for non-file sources. Updated descriptions to clarify the types of sources and data supported. [1] [2]general_source_extractor
class to handle various non-file sources, including Confluence, with appropriate extractor selection logic.OpenAPI Specification Update
DocumentStatus
,KeyValuePair
, andValidationError
objects./upload_file
,/upload_source
,/delete_document
, and/document_reference
. Enhanced error handling with additional response codes (e.g., 422 for validation errors).These changes improve the API's clarity, flexibility, and compliance with modern OpenAPI standards.