-
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
[YSQL] text search configuration "english" does not exist #1979
Comments
jaki
pushed a commit
to jaki/yugabyte-db
that referenced
this issue
Aug 22, 2019
Previously, all statements could not be uncommented because of issues with `json_populate_record`. Thanks to the RBAC diff that got pushed (e89d75b), these statements can be uncommented without errors. Uncomment several statements up to the next failing statement, `to_tsvector`, which is raised as issue yugabyte#1979.
During initdb, we've disabled setting up dictionary for YB. We should enable that.
|
yifanguan
added a commit
that referenced
this issue
Nov 29, 2021
Summary: This diff supports the PG11 text search configuration feature. Default supported languages are: danish, dutch, english, finnish, french, german, hungarian, italian, norwegian, portuguese, romanian, russian, spanish, swedish, turkish. initdb.c is modifed. Relevant grammar, regression tests, and the corresponding migration script are added. AlterTSDictionaryStmt and AlterTSConfigurationStmt are not enabled in this diff. A text search configuration specifies all options necessary to transform a document into a tsvector: the parser to use to break text into tokens, and the dictionaries to use to transform each token into a lexeme. Every call of to_tsvector or to_tsquery needs a text search configuration to perform its processing. Example: ``` SELECT to_tsvector('english', 'The Fat Rats'); to_tsvector ----------------- 'fat':2 'rat':3 ``` Users can also create custom configurations. Example: ``` CREATE TEXT SEARCH CONFIGURATION public.pg ( COPY = pg_catalog.english ); CREATE TEXT SEARCH DICTIONARY ispell ( Template=ispell, DictFile=ispell_sample, AffFile=ispell_sample ); ``` Test Plan: Modify existing regression tests: ybd debug --java-test 'org.yb.pgsql.TestPgRegressTypesString' ybd debug --java-test 'org.yb.pgsql.TestPgRegressPgMiscIndependent' ybd debug --java-test 'org.yb.pgsql.TestPgRegressFeature' ybd debug --java-test 'org.yb.pgsql.TestPgRegressExtension' Run the following test to test initdb migration: ybd release --java-test 'org.yb.pgsql.TestYsqlUpgrade' Reviewers: mihnea, jason, alex Reviewed By: jason, alex Subscribers: jenkins-bot, bogdan, sanketh, yql Differential Revision: https://phabricator.dev.yugabyte.com/D13212
Feature supported by the following commit -> 509b950 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running some lines in the
json
regress test manually looks like the following:These should not error.
The text was updated successfully, but these errors were encountered: