tarantool / tarantool/doc

[5pt] Indexes: Community review

Open
#1,943 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

index rewrite user_guide
Dominant language
CSS
Stars
15
Forks
49
Avg merge
1d 13h
Merged PRs (30d)
3

Description

Indexes: Community review

Product: Tarantool
Since: latest
Audience/target: all Tarantool users
Root document: https://www.tarantool.io/en/doc/latest/book/box/indexes/
https://www.tarantool.io/en/doc/latest/reference/reference_lua/box_space/create_index/
SME:
Peer reviewer: @NickVolynkin

Details

This is the forth step in revising our documentation about indexes. (See #1691, #1820 and #1871.)
Here we want to understand whether the revised documents became more informative and clear or not and what is left to write.
We have some concerns about the structure and the completeness of the provided information.

We suggest answering the following questions:

  1. Can you easily find any information about indexes you need via this page?
  2. Do you think the current structure of the document is appropriate?
  3. Should we write a special section about index features (such as, functional, multikey indexes, partial search, etc.)?
  4. What features did we lost?
  5. How can we improve the page about index creation?

Please, leave your feedback here in comments.

Definition of done

  • collect feedback from developers and users
  • rewrite dubious places

To be done with: #1782 #1737

Contributor guide

Open the contributing guide

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 by reviewing the indexes guide and the box_space/create_index reference page linked in the issue, then compare their structure and completeness against the five review questions. Gather feedback from developers and users, identify dubious or missing information, and update the documented pages. Done means feedback has been collected and the agreed unclear sections have been rewritten.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.