Content for search elastic v2 #4155
Conversation
|
I think it would be good to add a table with the supported querystring operators and their usage, see: |
I think we should keep it simple and link to the Elasticsearch docs that have all this information. |
I have taken a look on how the referenced ES page presents and I am not convinced to use it. This is the user docs not a docs for persons with in depth knowledge. There is too much information like backend request details ect where users are definitely the wrong audience. Users are looking to "what can I enter to refine my results" and not how a top-level parameters or get is defined. I propose therefore to create a short table with the simple-query-string syntax which clearly describes the details and limits the info to the neccessary content. Having the link for further details would be ok. |
This comment has been minimized.
This comment has been minimized.
|
Wait, please. We have decided against directly using Simple Query String. Instead we build the query strings in the backend and make it easier for the user by not providing so much flexibility. More information to follow soon. |
|
@EParzefall @mmattel We need to change a bit here I had an approval meeting with Product management today. They were not happy to expose any query language to the end user. Outcome: |
|
ACK, we'll wait for more info on how the search will actually work. |
There's not that much more to say, I guess. We don't expose the query language to the user, so
|
…ncloud/docs into content-for-search_elastic-v2
…ncloud/docs into content-for-search_elastic-v2
|
Minimal update for now to reflect the changes described in |
|
There is no limitation to core (10.9) Backport to 10.9, 10.8 and 10.7 |
| Things get tricky when you don't remember what the file you're looking for was called and guess work doesn't help. A key word search within text documents is only possible if the Full Text Search app is installed. Contact your admin if you need it and it's not installed. With this app enabled, you can search in files of the most common formats. | ||
| Things get tricky when you don't remember what the file you're looking for was called and guess work doesn't help. A key word search within text documents is only possible if the Full Text Search app is installed. Contact your admin if you need it and it's not installed. With this app enabled, you can search within files of the most common formats. Like with the regular search, you can enter only the first part of a string and it matches all occurances of words starting with the search string. | ||
|
|
||
| If you are looking for all terms containing a specific string like in the above example "pain", wildcards can be used, e.g. an asterisk: *pain gives you results like braine, Spain and painful. Using a question mark instead of the asterisk limits the preceeding characters to exactly one. In this example, only Spain would show up if you entered the search string "?pain". |
There was a problem hiding this comment.
@EParzefall @mmattel why does *pain match braine ?
Adding information on version 2 of the Full Text Search app coming soon. Text is awaiting approval by engineering and product management. Do not merge before the release.
This will fix issue #3996 and issue #3929.