Releases: moqui/moqui-elasticsearch
Moqui ElasticSearch Tool Component 1.2.2
Moqui ElasticSearch 1.2.2 is a patch level new feature and bug fix release.
There are only minor changes and fixes in this release. For a complete list of changes see:
This will be the last release of the moqui-elasticsearch tool component. It will no longer be supported by moqui-framework after this release. It is being replaced by the new ElasticFacade in moqui-framework which uses a pure HTTP REST API client with no library dependencies to interact with one or more ElasticSearch clusters. With the new approach there will be no support for an embedded ElasticSearch server, but it may be installed in the runtime/elasticsearch directory and started/stopped automatically in a separate process by the MoquiStart class.
Moqui ElasticSearch Tool Component 1.2.1
Moqui ElasticSearch 1.2.1 is a patch level new feature and bug fix release.
There are only minor changes and fixes in this release. For a complete list of changes see:
Moqui ElasticSearch Tool Component 1.2.0
Moqui ElasticSearch 1.2.0 is a minor new feature and bug fix release.
This integration now uses ElasticSearch 6.3.2. There were significant changes in ElasticSearch in version 6 that are handled in this updated integration. Code that uses ElasticSearch directly may need to be updated, whereas code only using the index, search, and other services from this component should work fine without changes.
By setting elasticsearch_mode to 'rest' and specifying at least elasticsearch_host1 the integration can now run without an embedded node and against a remote cluster via the ElasticSearch REST API. Before this the recommended production approach when an external cluster was used was to have a processing only (no persistence) node running embedded in Moqui that joins the cluster. That can still be done and is more efficient but increases load on app servers. The main reason for using the REST API mode is for deployments such as on AWS ElasticSearch where joining a cluster is not possible.
On startup if a DataFeed has indexOnStartEmpty=Y and ES indexes for the feed do not exist the full feed will be indexed so that indexes are populated based on relational database data for expected system operation.
Moqui ElasticSearch Tool Component 1.1.0
Moqui ElasticSearch 1.1.0 is a minor new feature and bug fix release.
ElasticSearch is now available to other tools on port 9200 bound to site local addresses, ie only localhost and other servers on the local internal network such as other docker containers on the same network.
ElasticSearch is available remotely through the main Moqui web server with a transparent proxy servlet on /elastic that requires authentication and the 'ElasticRemote' permission. This can be done with HTTP Basic authentication per request or in an authenticated session.
Similarly if Kibana is deployed on the same server, network, or docker host as the Moqui server it can be proxied through /kibana. The default setup uses Kibana running on localhost and the Kibana host can be specified using an environment property or by modifying the MoquiConf.xml file in this component. The best way to authenticate is login to the Moqui with a user that has the'KibanaRemote' permission to establish a session and then go to /kibana.
Moqui ElasticSearch Tool Component 1.0.0
This is the first release of the Moqui ElasticSearch integration separate from Moqui Framework.
Moqui ElasticSearch Tool Component 1.0.0 RC1
This is a release candidate for public review.