Open robertpang opened 5 years ago
Aw, this is the one thing preventing me from committing to yugabyte
Ran into the need for this trying to run promscale with YB (specifically the need for support for gin indexes).
Just want to note another vote for this feature -- would be really amazing, especially when using JSONB fields to get a best-of-both-worlds SQL + NoSQL kind of system going.
Please!
This and (at least) #997 (exclusion constraint) are required for doing temporal tables sanely. For example a table to track the valid state of a user job table where you want to constrain the user to only have one job_id at any given point in time:
create table temporal (
user_id text,
job_id text,
valid_time tstzrange,
exclude using gist (user_id with =, job_id with =, vaild_time with &&)
)
Very much in need of this please. How can we get a feature prioritized here ?
it will be a cannon. Please prioritize the task! Please.
That's the most voted feature and a one of the blockers to use yb in the current project :(
GIN indexes are now in-progress and tracked in: https://github.com/yugabyte/yugabyte-db/issues/7850 Keeping this open since it includes GiST which will be addressed later.
@m-iancu thank you very much for linking the issue! Does it make sense to rename this issue to GIST index only?
need this in stable versions.
Any updates to address GIST Indexes in the foreseeable future?
Any updates to support GIST Indexes in the foreseeable future?
Any updates yugabyte team?
Must have feature.
Jira Link: DB-1851 YugaByte DB currently supports btree and hash index methods only. Consider supporting other index methods: