feat(search-pipeline): add searchIndexerPipeline convenience#647
Open
ddeboer wants to merge 1 commit into
Open
feat(search-pipeline): add searchIndexerPipeline convenience#647ddeboer wants to merge 1 commit into
ddeboer wants to merge 1 commit into
Conversation
- Wire the common object-grain indexer into a ready-to-run Pipeline: one stage per root type in the schema, roots selected by class, extraction generated from the schema, one engine writer per type, with optional provenance and reporting passed through. - Exclude blank-node subjects in selectByClass via FILTER(!isBlank(...)): a blank node has no stable document key, so it can never become a search document and would crash framing. - Document the role-to-package mapping in the search-pipeline README and point the stub READMEs of sparql-server and sparql-importer at sparql-qlever as the concrete adapter.
ddeboer
force-pushed
the
feat/search-indexer-pipeline
branch
from
July 23, 2026 18:32
8d81448 to
6feedfe
Compare
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
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.
Fix #640
What
searchIndexerPipelinein@lde/search-pipelinewires the common object-grain search indexer and returns the ready-to-runPipeline<TypedSearchDocument>:RootTypein the schema, each selecting the type’s non-blank roots by class (selectByClass, blank-node-safe since Blank-node roots crash framing; selectByClass selects them #641 landed) and extracting with the schema-generated CONSTRUCT;searchIndexWriterterminal, one engine writer per type viawriterFor;datasetsas a plainDataset[](wrapped inManualDatasetSelection) or anyDatasetSelector;distributionResolver(e.g.ImportResolver+@lde/sparql-qlever),provenanceStore+pipelineVersion, andreporter.Consumers now supply only the domain (schema, datasets) and the deployment shell (engine writer, SPARQL/import adapter), instead of repeating the wiring that surfaced #633/#638 downstream. Anything beyond the object grain – bespoke selectors, per-stage tuning, non-SPARQL readers, plugins – still composes
searchStages/searchIndexWriter/Pipelinedirectly; the convenience owns no capability of its own.Supporting docs (the issue’s original scope)
@lde/search-pipelineREADME: a Quick start for the convenience plus the role → package mapping table (selection, resolution/import via@lde/sparql-qlever, stages, engine writer via@lde/search-typesense, provenance, reporting).@lde/sparql-serverand@lde/sparql-importernow say they are interface-only and point at@lde/sparql-qleveras the concrete adapter.Tests
Dataset[]andDatasetSelectorforms,pipelineVersionrequired with a provenance store).searchIndexerPipeline(...).run()against a local SPARQL endpoint over the Drapo fixture – both types indexed into their own committed collections, and the fixture’s blank-nodeCreativeWorkexcluded by the baked-in blank-node-safe selection.