Elasticsearch Connector Technical Preview feedback

[JasonStoltz]

Thank you for using the Elasticsearch Connector for Search UI.

We have documentation on the connector and a tutorial to follow.

While the connector is in Technical Preview, we would appreciate feedback, suggestions, and bug reports.

Please use this issue to report any of the above.

[vinothdevelop]

Elastic search connector is very useful and I started to use it immediately after available. Only thing I miss is the ability to modify request before sending to elastic search. It will help us implement complex query. Looks like it exist in App search and work place search connector. Having that would be really helpful.

[joemcelroy]

Hey @vinothdevelop

Good to hear. Yes should be a straightforward addition. Created an issue here for this feature. #705

[vinothdevelop]

Hey @vinothdevelop

Good to hear. Yes should be a straightforward addition. Created an issue here for this feature. #705

Thank you @joemcelroy, looks like the elastic connector is broken by latest version. Click events doesn't work due to error in track click action. Probably a change introduced to handle workplace search connector analytics broke it. _meta.id is not available in elastic search result object. I can send a PR but not sure if I can do it anytime soon.

[joemcelroy]

thanks @vinothdevelop - you're correct! a couple of changes within analytics intoduced in the workplace connector caused a regression within the elasticsearch connector. Good news is i've submitted a PR with the fix. Hopefully should be able to release soon #715

Also for 1.11.0 there has been a slight change in the API. We no longer pass in queryFields and we rely on search_fields in the configuration. See documentation https://github.com/elastic/search-ui/blob/master/packages/search-ui-elasticsearch-connector/README.md#usage

[vinothdevelop]

thanks @vinothdevelop - you're correct! a couple of changes within analytics intoduced in the workplace connector caused a regression within the elasticsearch connector. Good news is i've submitted a PR with the fix. Hopefully should be able to release soon #715

Also for 1.11.0 there has been a slight change in the API. We no longer pass in queryFields and we rely on search_fields in the configuration. See documentation https://github.com/elastic/search-ui/blob/master/packages/search-ui-elasticsearch-connector/README.md#usage

Thank you for the quick response. We are upgrading to latest version now additional detail on the search field is really helpful. Looking forward to the #715 release.

[vinothdevelop]

Thank you @joemcelroy, Analytics issue seems to be resolved with latest update. But looks like auto complete is broken. Rawhit is not available in autocomple query response but it is accessed here https://github.com/joemcelroy/search-ui/blob/2dc4c03a2ac3d8586e7250eb13741d825d598aac/packages/search-ui-elasticsearch-connector/src/handlers/common.ts#L25
Looks like autocomplete request doesn't have includeRawHit property. Please correct me if I miss the flow.

[joemcelroy]

thanks @vinothdevelop for the fix! This is now released under v1.11.2

[jennifer122105]

Brand new to ES, but I've found this connector very helpful in getting started! I'm wondering if there is any support for configuring this to use a query string query rather than a multi-match query? Or perhaps that would fall within the scope of #705 ?

[joemcelroy]

hey @jennifer122105, soon you will be able to modify the elasticsearch request query before its dispatched to elasticsearch. Just waiting for a release which will be next week :)

Will feed this also back to the team to think about how we can make this more 1st class.

#754

[llermaly]

Thanks for this nice connector!. I'm trying to run setFilter on a number field (range query) but the underlying query is still being a "term" query.

Is this the way to do it?

    setFilter("price", {
      name: "price",
      from: rangePrices[0],
      to: rangePrices[1],
    });

Request query:

{
  "bool": {
    "must": [
      {
        "bool": {
          "must": [
            {
              "term": {
                "price": {
                  "name": "price",
                  "from": 365,
                  "to": 5000
                }
              }
            }
          ]
        }
      }
    ]
  }
}

Thanks

@joemcelroy

[llermaly]

A suggestion would be to allow including the "track_total_hits" option to the elastic query