Skip to content
This repository was archived by the owner on May 28, 2023. It is now read-only.

Conversation

@KevinGimbel
Copy link
Contributor

This commit removes the user and password from config/default.json.
This allows to not set a username and password when connecting to
Elasticsearch; Previously the default values were used if username and
password were omitted from config/local.json

Fixes #358

adityasharma7 and others added 8 commits August 26, 2019 12:58
…ated vuestorefront#334

As of 5.0 value not_analyzed is no longer applicable.
Reference: https://www.elastic.co/guide/en/elasticsearch/reference/5.0/breaking_50_mapping_changes.html#_literal_index_literal_property
Citation: On all field datatypes (except for the deprecated string field), the index property now only accepts true/false instead of not_analyzed/no. The string field still accepts analyzed/not_analyzed/no.
As per https://www.elastic.co/guide/en/elasticsearch/reference/1.4/mapping-core-types.html, not_analyzed means that its still searchable, but does not go through any analysis process or broken down into tokens.
As per https://www.elastic.co/guide/en/elasticsearch/reference/current/text.html, index means Should the field be searchable? Accepts true (default) or false.

So, changing index value not_analyzed to true. We can also remove index key as default value is true, but as I am unsure how it works when migrating to new release with schema changes. Setting it true as it may cause no harm and produces desired results
Update README.md – Node 10.x is now required
Done: Remove index value not_analyzed for some fields as it is deprecated vuestorefront#334
This commit removes the user and password from `config/default.json`.
This allows to not set a username and password when connecting to
Elasticsearch; Previously the default values were used if username and
password were omitted from `config/local.json`

Fixes vuestorefront#358
Signed-off-by: Kevin Gimbel <hallo@kevingimbel.com>
@andrzejewsky
Copy link
Contributor

@KevinGimbel thanks for PR, good point! Please change base to release/v1.11-rc1, we'd like to release this in 1.11

@KevinGimbel KevinGimbel changed the base branch from master to release/v1.11-rc1 November 6, 2019 10:32
@KevinGimbel
Copy link
Contributor Author

@andrzejewsky I've changed the base to release/v1.11-rc1.

Copy link
Contributor

@andrzejewsky andrzejewsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

@andrzejewsky andrzejewsky merged commit abc618c into vuestorefront:release/v1.11-rc1 Nov 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants