Skip to content
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

fulltext index get failed #4880

Closed
son2408 opened this issue Nov 16, 2022 · 12 comments
Closed

fulltext index get failed #4880

son2408 opened this issue Nov 16, 2022 · 12 comments

Comments

@son2408
Copy link

son2408 commented Nov 16, 2022

how to create fulltext index tag ?

(root@nebula) [HCMLIS]> show text search clients;
+-----------------+---------------+------+
| Type            | Host          | Port |
+-----------------+---------------+------+
| "ELASTICSEARCH" | "10.225.0.32" | 9669 |
+-----------------+---------------+------+
Got 1 rows (time spent 1898/4419 us)

Tue, 15 Nov 2022 21:59:05 +07

(root@nebula) [HCMLIS]> ^C
(root@nebula) [HCMLIS]> CREATE FULLTEXT TAG INDEX nebula_index_1 ON thongtinhoso(rootId);
[ERROR (-1005)]: fulltext index get failed : nebula_index_1
@son2408
Copy link
Author

son2408 commented Nov 16, 2022

cc @wey-gu Could you let me, plz?

@wey-gu
Copy link
Contributor

wey-gu commented Nov 16, 2022

Dear @son2408 ,

Have you created a native index on thongtinhoso(rootId) before creating full-text index nebula_index_1, plz?

@son2408
Copy link
Author

son2408 commented Nov 16, 2022

yes, I created native index before creating full-text index.

(root@nebula) [HCMLIS]> describe tag index nebula_index_1
+----------+---------------------+
| Field    | Type                |
+----------+---------------------+
| "rootId" | "fixed_string(100)" |
+----------+---------------------+
Got 1 rows (time spent 1125/4097 us)

@wey-gu
Copy link
Contributor

wey-gu commented Nov 16, 2022

But they are in same index name, maybe you could do this instead?

CREATE FULLTEXT TAG INDEX nebula_index_1_es ON thongtinhoso(rootId);

@son2408
Copy link
Author

son2408 commented Nov 16, 2022

I tried, but it doesn't work.

(root@nebula) [HCMLIS]> CREATE FULLTEXT TAG INDEX nebula_index_1_es ON thongtinhoso(rootId);
[ERROR (-1005)]: fulltext index get failed : nebula_index_1_es

@wey-gu
Copy link
Contributor

wey-gu commented Nov 16, 2022

Were the listener and elastic search all deployed properly as the documentation guided?

@son2408
Copy link
Author

son2408 commented Nov 16, 2022

yes, the best way to check deloying elastic search properly ? @wey-gu

@wey-gu
Copy link
Contributor

wey-gu commented Nov 16, 2022

@Sophie-Xie could anyone help with this? I am not yet familiar with this.

@Sophie-Xie
Copy link
Contributor

But they are in same index name, maybe you could do this instead?

CREATE FULLTEXT TAG INDEX nebula_index_1_es ON thongtinhoso(rootId);

@cangfengzhs pls take a look, thanks.

@son2408
Copy link
Author

son2408 commented Nov 17, 2022

LISTENER offline, could you let me know probable cause of it,plz ? cc @wey-gu, @Sophie-Xie
(root@nebula) [HCMLIS]> show LISTENER;

+--------+-----------------+----------------------+-----------+
| PartId | Type            | Host                 | Status    |
+--------+-----------------+----------------------+-----------+
| 1      | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 2      | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 3      | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 4      | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 5      | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 6      | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 7      | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 8      | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 9      | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 10     | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 11     | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 12     | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 13     | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 14     | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 15     | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 16     | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 17     | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 18     | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 19     | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |
| 20     | "ELASTICSEARCH" | ""10.225.0.32":9669" | "OFFLINE" |

@cangfengzhs
Copy link
Contributor

Maybe you can check whether Elasticsearch is working and whether the correct address of Elasticsearch is signed In in NebulaGraph.

@Sophie-Xie
Copy link
Contributor

I will close it. If you have any new info, pls reopen it. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants