vesoft-inc / vesoft-inc/nebula-java
[doc][example] on how to parse typical(path, lookup, expand) resultSet
Open
Nobody has claimed this yet.
doc affected
type/enhancement
- Dominant language
- Java
- Stars
- 199
- Forks
- 125
- Avg merge
- 5h 6m
- Merged PRs (30d)
- 3
Description
as title
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the Java API entry points for typical(path, lookup, expand) and the returned resultSet. Determine what a representative parsed result should look like, then document an example showing how to parse it. Done means the example clearly explains the resultSet structure and parsing steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100