apache / apache/maven-indexer

[MINDEXER-206] Search Backend SMO and RR handle different Artifact.extension

Open
#678 2 comments 0 reactions 0 assignees View on GitHub
enhancement priority:major
Dominant language
Java
Stars
74
Forks
69
Avg merge
14h 8m
Merged PRs (30d)
6

Description

**[Tamas Cservenak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cstamas)** opened **[MINDEXER-206](https://issues.apache.org/jira/browse/MINDEXER-206?redirect=false)** and commented

The two backends should not force caller to construct Query differently, but handle their own implementation specifics silently.

---
No further details from [MINDEXER-206](https://issues.apache.org/jira/browse/MINDEXER-206?redirect=false)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by comparing the SMO and RR search backend implementations, focusing on how each handles Artifact.extension and constructs or interprets Query. Confirm the expected behavior from the MINDEXER-206 description; done means callers can use the same Query shape while each backend handles its extension differences internally.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.