llamaIndex - 💡(How to fix) Fix [Question]: Clarification on new integration rules [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
run-llama/llama_index#21396Fetched 2026-04-17 08:26:56
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
Participants
Timeline (top)
labeled ×1
RAW_BUFFERClick to expand / collapse

Question Validation

  • I have searched both the documentation and discord for an answer.

Question

Just seeking some clarification on #21139. I'm from Isaacus and we already have an integration for our embedding model at llama-index-integrations/embeddings/llama-index-embeddings-isaacus.

I am wondering how we would go about integrating our new reranker model, Kanon 2 Reranker. Do you guys still accept PRs for additions to docs/api_reference/api_reference/postprocessor and docs/examples/node_postprocessor?

Thanks.

extent analysis

TL;DR

To integrate the new Kanon 2 Reranker model, submit a PR with updates to the relevant documentation and example directories.

Guidance

  • Review the existing integration for the embedding model at llama-index-integrations/embeddings/llama-index-embeddings-isaacus to understand the required structure and content.
  • Check the contribution guidelines for specific requirements and formatting for PRs to docs/api_reference/api_reference/postprocessor and docs/examples/node_postprocessor.
  • Ensure the PR includes clear documentation and examples for the Kanon 2 Reranker model to facilitate easy integration and usage.
  • Verify that the PR follows the existing coding standards and conventions used in the project.

Notes

The feasibility of this approach assumes that the project maintainers still accept PRs for the mentioned directories, as implied in the issue.

Recommendation

Apply workaround: Submit a PR with the necessary updates and await feedback from the project maintainers, as this allows for integration of the new model while following the project's contribution process.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING