pingcap/tidb

Support for SPATIAL functions, data types and indexes

Open

#6,347 opened on Apr 23, 2018

View on GitHub
 (8 comments) (15 reactions) (0 assignees)Go (40,090 stars) (6,186 forks)batch import
feature/acceptedhelp wantedtype/feature-request

Description

We may reconsider the feature later. But it will be no early than the end of this year.

pingcap do not have plan for geo index https://github.com/pingcap/tidb/issues/673#issuecomment-251132927, I am interested in adding this feature to tidb, so Is there anyone else interested or working on this?

Contributor guide

Tech stack
gosql
Domain
databasebackend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Go proficiencydatabase internals knowledgespatial data structures
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Consult the referenced issue pingcap/tidb#673 for historical context. Study TiDB's SQL parser and planner to understand how new function types and data types are added. Examine MySQL's spatial extensions for guidance. Since there is no detailed specification, propose a design document outlining the scope, implementation plan, and backward compatibility considerations. Seek maintainer feedback on the proposal before proceeding.
Support for SPATIAL functions, data types and indexes · pingcap/tidb#6347 | Good First Issue