2.3.2 Enterprise Compatibility #2
Comments
|
Hi @jefflenz! Thanks for submitting your issue here. Can you tell us more about your settings? What version of Elastic Search is your Search Engine configured to? Can you also provide the stacktrace for this issue so that we can pinpoint where this is thrown? Thank you for your assistance! |
|
|
I have "make a request to backend" set to yes, instant search is disabled. There's a lot of settings, are there specific ones you'd like to know of? |
|
Hey @jefflenz! After briefly looking at your stacktrace, it seems that your Search Engine might still be set to Mysql. Can you confirm what this setting is set to: Stores > Configuration > Catalog > Catalog > Catalog Search > Search Engine This external module overrides the Elastic Search adapters to replace the product collection to be queried from Algolia. Additionally, searching through your stacktrace, I did not find anything associated to our Algolia extensions. I might be that you just need to reindex the catalogsearch_fulltext indexer. Can you confirm your Search Engine settings? |
|
Strange, it was set to "Elasticsearch 6+", however, after swapping it to "Elasticsearch" I'm getting a new error: |
|
Thanks for following up. What version of elasticsearch is installed in your environment? I would match your Search Engine to the version you are utilizing. If it is elasticsearch v6, then you should configure it to Elastic Search 6 +. If and when you switch the search engines, I would clear your cache to update the configuration and run the catalogsearch_fulltext indexer. Let me know if this error clears up for you as this one might be related to a mismatched version. |
|
Yes I'm using ES 6.1.4. Not sure why it's not using it when I select it from the Magento admin. When I select the option for just "Elasticsearch" it starts using it. I will debug further and followup, thanks for the help so far! |
|
So it is indeed using Elasticsearch, I confirmed by turning off ES and seeing no results, turning it back on and then seeing results. I can also confirm disabling the algolia es compatibility extension makes the error go away and the page loads as normal. I'm currently not available to spend a lot of time debugging why. Has the extension been tested on a clean Enterprise 2.3.2? |
|
I have tested this on Commerce 2.3.2 and on the cloud environment that is using elasticsearch v 6 with Elasticsearch 6+ configure as Magento's Search Engine. Would it be possible to get the version of the elasticsearch php client installed in composer? The package name is: You can read more about how to configure Elasticsearch in this doc: I'll take a deeper look at the error further but your version of elasticsearch should be Elasticsearch 6+. |
|
It's using ElasticSearch 6 with 6+ configured in admin. I also deployed to our cloud environment which is also using ES and same error. Perhaps our Algolia settings are different. I also disabled all 3rd-party extensions/reindexed to rule that out |
|
Some search terms work, where others produce the error. I'm not quite sure why. Would you be able to take a look at our setup if I provided you credentials? |
|
Hey @jefflenz! Yes, that would be great. You can send your information over to [email protected] and mention me in your request so that it is dispatched to the Magento team. If you can also send over the search terms that are throwing errors and links to these results. Thanks! |
|
Apologies, our staging server is undergoing maintenance- however, I did notice a correlation: If the product count exceeds a few hundred it seems to error out. Will be in touch with credentials to staging site. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Haven't tested on open source, but this extension does not work on commerce/enterprise 2.3.2. There's an SQL syntax error on the ORDER BY clause:
Currently, it's trying to do (Note the backticks):
This should instead be:
The text was updated successfully, but these errors were encountered: