lbryio / lbryio/hub

Using param `limit_claims_per_channel` doesn't return always all claims that would excpected

Open
#114 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
15
Forks
16
PR merge metrics
No merged PRs in 30d

Description

I think currently on claim_search hub looks up to 1000 items for specific params.
And if I do claim_search with following params:
```
"limit_claims_per_channel":1,
"channel_ids": <43-channel_ids>,
"page_size": 36
```
I may only get 31 items in total(even though there are more claims that could be returned), since there are only claims from 31 different channels in those 1000 items.
If using smaller `page_size` there are more items that get returned in total. Since it's able to fill more pages, I guess.

This can currently be seen easily on spooky category on Odysee, when ordering by effective amount https://odysee.com/$/spooky?order=top with `release_time` removed
(44 channel_ids, but only 31 claims returned in total)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the claim_search entry point and reproduce the issue with limit_claims_per_channel, channel_ids, and page_size, using the spooky category example. Trace how the 1000-item lookup interacts with pagination and channel limits; done means all eligible claims can be returned consistently regardless of page_size.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend-api-design, blockchain, 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.