node-red / node-red/node-red-nodes
No access to iterator for queries?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
I'm not sure if I'm missing something, but the only read access to the leveldb node I can find is just a simple key in msg.topic. If we don't know the exact key and want to sort/filter the data, is there any further API access to access? I have timestamped data and need to pull out ranges, etc.
Is this possible with the current functions?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the current LevelDB node API and how reads are exposed through msg.topic. Determine whether range and filtering access is supported; done means documenting the supported behavior or defining the needed iterator or range API and its usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100