my scenario is as follows:
I am an SE doing a demo for the prospect and telling them our universal index indexes all elements and content
I show them a json document in the database (QC), show them the structure and explain that, as soon as the document is ingested, I can immediately search for content in a specific element, like ‘id_str’
Then I'll switch to my slush-based demo and type in the search bar:
id_str: 753206617181597696
I press enter the document is found.
This can be functionality that's configurable through a toggle (current default behaviour of the search bar vs. the new one). This toggle can be hidden by default.
We could have something like this below the search bar: (x) search string ( ) element word query ( ) element value query, and that would cause the search string to be handled differently.
my scenario is as follows: I am an SE doing a demo for the prospect and telling them our universal index indexes all elements and content I show them a json document in the database (QC), show them the structure and explain that, as soon as the document is ingested, I can immediately search for content in a specific element, like ‘id_str’ Then I'll switch to my slush-based demo and type in the search bar: id_str: 753206617181597696 I press enter the document is found.
This can be functionality that's configurable through a toggle (current default behaviour of the search bar vs. the new one). This toggle can be hidden by default.