-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Phase 1][TABLEGROUP][GIN INDEX] GIN Indexes with NO TABELGROUP fails to read data. #11163
Comments
Here's a small repro: CREATE TABLEGROUP g;
CREATE TABLE t (i int[]) TABLEGROUP g;
CREATE INDEX ON t USING gin (i) NO TABLEGROUP;
SELECT * FROM t WHERE i @> '{1}'; It's working fine with non-tablegroup colocation and opt-out. It's not possible to opt-out only the index in non-tablegroup colocation. Maybe it has to do with the index being opted out but the table not. CREATE DATABASE co colocated true;
\c co
CREATE TABLE t (i int[]) WITH (colocated=false);
CREATE INDEX ON t USING gin (i);
SELECT * FROM t WHERE i @> '{1}'; |
Will be resolved along with #12503 |
We'll restrict indexes to share same topology as base table (per #12503). Moving this to phase 3 in case we want to support this later. |
Such topology support has been removed in #12503, closing as wontfix |
@frozenspider @tverona1 Is this expected to be fixed in 2.14? On 2.14.0.0-b70 I am still seeing:
The FATALs contain:
|
@def- no, this restriction has been implemented on master after 2.14 was cut, and since tablegroups are beta feature we didn't consider backporting it. Also note that while it won't be possible to create index with such weird topology anymore, existing indexes created prior to the restriction would continue to have issues. The solution would be to drop an index and recreate an index (which will be in the same tablegroup). |
Jira Link: [DB-383](https://yugabyte.atlassian.net/browse/DB-383)
DB Version: 2.11.2 and 2.11.3
Steps:
Expected: After Step 5, it should return correct result
Actul: After Step 5, it is throwing below ERROR
If user executes any query immediately it looses its connection.
Found below log in tserver FATAL and ERROR log files
F0121 07:44:02.958986 26754 tablet.cc:3642] Check failed: _s.ok() Bad status: Not found (yb/tablet/tablet_metadata.cc:350): Table <unknown_table_name> (00004000000030008000000000004007) not found in Raft group 1d0fb617fa234fb8a07c449a1f988577
And
Note: Same is working fine with regular indexes.
The text was updated successfully, but these errors were encountered: