A first party module to integrate Elastic App Search in Magento 2.

Received the following errors this morning on my staging 2.3.2 environment and my development 2.3.3 environment: Exception #0 (Magento\Framework\Exception\LocalizedException): Unable to find field sku_value.

Staging: This event happened when trying to search or navigate into the Magento catalog. https://c9.saderra.com/catalog/category/view/s/boat-covers/id/12/

Development: Same condition to reproduce: https://classic.saderra.com/patio/shop-by-collection/storigami

We are seeing the following error generated by this plugin: "query_params":[]},"error":"Rate limit exceeded"} []

How do we manage this?

Another issue has arisen when your module is installed on 2.3.2, without the other aforementioned extension:

Compare this site on our live production site: https://classicaccessories.com/patio-furniture-cushions/lounge-chair-cushions

This site is a direct backup of that site, with the finder module disabled and your extension enabled: https://c1.saderra.com/patio-furniture-cushions/lounge-chair-cushions

The error is: [2019-10-16 01:57:55] main.INFO: Reference to undeclared plugin with name 'stockedProductsFilterPlugin'. This seems to be discussed here:

https://github.com/magento/inventory/blob/d956bd063d2d35f75c58c0e48cdfa31db28b4efd/app/code/Magento/InventoryElasticsearch/etc/di.xml#L10

Hello guys,

i know your work is good, but in the real world we need to work with a multiple installation types.

Please Add php7.0 support.

Thank you so much

Vanilla install. 2.3.3 on EC2/Nginx.

Condition: Attempt to navigate to any category page: https://classicstaging.net/patio https://classicstaging.net/bbq-grill etc...

The following error loads:

1 exception(s): Exception #0 (Exception): Warning: array_chunk(): Size parameter expected to be greater than 0 in /var/www/html/vendor/elastic/app-search-magento/src/module-catalog-search/Model/Product/SearchAdapter/RequestExecutor/Rescorer/CategoryPositionRescorer.php on line 112

Additional error information viewable on the above link.

@afoucret - some small updates to the dev env setup doc - mostly for clarity, and moved the "configure env variable" section before the build to avoid confusion.

This PR contains everythings indexer will need to manipulate and update schemas:

• [X] Create schema model
• [X] SchemaResolverInteface allows to locate the schema of a particular engine (e.g. getSchema('catalogsearch_fulltext'))
• [X] Dummy SchemaProvider for product
• [x] Add updateSchema operation in EngineManagerInterface
• [x] Use it all in IndexStructure

The product schema contains only one field (test with the type text).

You can test the schema is correctly updated by running the fulltext indexing command:

bin/magento indexer:reindex catalogsearch_fulltext

Note: Clean all caches before doing it bin/magento cache:clean

A coming PR will implement the actual product schema instead of this dummy one.

Installation on a fresh magento 2.3.3 install, LAMP, multi-store configuration results in the following when attempting to search:

1 exception(s): Exception #0 (DomainException): Undefined factory elastic_appsearch

I opened the PR https://github.com/elastic/app-search-magento/pull/52

adding xml tag closing in app-search-magento / src / framework-app-search / etc / app_search_fields.xsd file

Improve the sync manager to:

• tag search requests used to wait for indexed documents to be searchable
• tag search requests used by document purge
• add a max number of attempts when waiting for the documents to be searchable

A breaking change has been introduced in Magento 2.3.2.

This BC makes mandatory to declare new factories for the search module (magento/magento2#23615).

This patch solves a regression caused by this change if using the module with Magento >= 2.3.2.

Hi,

Is there a way to use this module using a js popup to show results in the frontend? I mean, without using the backend. Launching queries directly to the external service in "autocomplete mode" from javascript.

Thank you.

Customer is reporting that when they switch from MySQL to the App Search Magento plugin, the pagination on their site fails to load correctly. For instance, a search that brings 300 results will show 3 results on the first page, 5 on the second page, 4 on the third page, etc although 24 results per page is selected. Pagination settings in Magento are default. API activity in App Search looks normal. When the customer switches back to using the MySQL database, pagination goes back to normal.

While we try to search it produce error https://prnt.sc/ulkfxy

1 exception(s): Exception #0 (Magento\Framework\Exception\LocalizedException): Query can contains only one match query with name search

Exception #0 (Magento\Framework\Exception\LocalizedException): Query can contains only one match query with name search

#1 Elastic\AppSearch\Framework\AppSearch\SearchAdapter\RequestExecutor\Filter\QueryFilterBuilder->getFilter()



		                                  
		                                    
	                                    

I install the module app-search-magento in my magento 2.4 version. While i'm trying to save Search Engine it will show error like Could not check engine exists: Unauthorized action.

Swift Credentials: https://cloud.elastic.co/ Host Identifier: host-1c8k8y API Endpoint: https://host-1c8k8y.api.swiftype.com Public Search Key: search-jcjrvztgzm8w7xh8k8ce63v6 Private API Key: private-g76w12caf1y3s4c17e9kgg6m username: elastic password: IWNJ12JdcpmsR22fiK3bbEnW