Magento 2.4: ElasticSearch Bypass? - elasticsearch

I've been reading the documentation for 2.4 and can see that ElasticSearch is a required module to upgrade - we'd been using a third party search module which we will continue to use for 2.4 too however you can't physically upgrade to 2.4 unless you have an active connection to ElasticSearch.
My question is: is there a way to upgrade to 2.4 without installing ElasticSearch on the server? I find it hard to believe that Adobe have decided to scrap the MYSQL search and replace it with one you have to pay and subscribe to.
Any advice is greatly appreciated!

Related

Is it possible to install only the profiling feature of Elasticsearch 6.8 X-Pack?

My installation of Elasticsearch 6.8.22 does not include an installation of X-Pack because so far we have not needed any of its features.
I am generating profiling data on queries, using the Profile API, but I want to use the Search Profiler UI capabilities available in Kibana. The documentation says that this is part of X-Pack.
My questions are:
Do I have to install all of X-Pack in order to use the Search
Profiler UI, or is it possible to install only certain features?
Do
I have to install X-Pack on the entire Elasticsearch cluster where I
am running the query in order to profile it?
Can I isolate the
X-Pack installation by creating a new separate Kibana installation
on its own server and connecting to my cluster, or does the X-Pack
installation need to be on one or more Elasticsearch servers in my
cluster?
the answer to 1 is it need to be installed as an entire package
the answer to 2 is yes, the entire cluster
the answer to 3 is no, see question 2

Is there a way to connect Elasticsearch 5.6.4 to Power BI

my company is running an old version of Elasticsearh (v.5.6.4). Im not overly familiar with the Elastic Stack suite but I have been asked to start pulling data from it to Power Bi for analysis (PBI).
I have seen articles that allow for connection to Elasticsearch using an ODBC driver but I'm not sure if this applies to older versions.
Does anyone know if its possible to connect PBI to Elasticsearch v.5.6.4?
Alternatively, my company has Kibana, so perhaps there is a way to dynamically extract data from that without doing manual extracts?
According to the Elastic Guide,
the driver version cannot be newer than the Elasticsearch server version. For example, A 7.10.0 server is not compatible with 8.2.3 drivers.
In your case, you can try installing ODBC Client 6.5.0 as it is the oldest version available.
But unfortunately it probably won't work.
ODBC Cliente - Past Releases
On the other hand, Kibana is part of the Elastic Stack. That's why it has an easy connection with Elasticsearch, which has a connection with Logstash. This way there is no need for manual data collection to use Kibana in your company's Elasticsearch version.

Does Heroku with Bonsai support anything higher than 7.10 of elasticsearch?

I am getting security warnings because client 7.13.0 has issues. However, I use Bonsai with Heroku which is server 7.10.2 and that is incompatible with the 7.15.0 client.
I tried the following
heroku addons:create bonsai -a <app> --version=7.14.2
But it is still showing 7.10.2
Can I get Heroku to support the newer version of elastic search server?
Bonsai support here. The current list of our supported Elasticsearch versions is here. This list is the same whether you have a cluster with us directly or through Heroku. Trying to provision a version of Elasticsearch that's not on this list will get you the closest available version to what was requested.
To shade in some context about why we're still running 7.10.2, it's important to know that in January 2021, Elastic announced that version 7.11 and on would be licensed under the Server Side Public License (SSPL) and not Apache 2.0.
This change has pretty severe implications for hosted Elasticsearch providers like Bonsai, and has limited our ability to release new versions. We're working on some long term solutions, but the process has been slower than we'd like.
In any case, Elasticsearch 7.10.2 is the latest Elasticsearch version we offer as of December 2021 (check the first link for updates). We also support OpenSearch, which is an Apache 2-licensed fork of Elasticsearch, maintained by AWS.
As always, please don't hesitate to reach out to us at support#bonsai.io with questions or issues.
Not at the moment, at least via Bonsai:
Protip: Bonsai supports a command line flag for specifying which version of Elasticsearch you want to use. Note that we only support specific versions of Elasticsearch, so you can’t provision an arbitrary one. We have a list of available versions documented here.
That link leads to a page that lists support for 5.6.16, 6.5.4, and 7.10.2 for multi-tenant classes and 1.7.5 to 7.10.2 for single-tenant.
Note that this page is on the docs.bonsai.io domain, so it is Bonsai-specific, not Heroku-specific.
The official Elasticsearch addon appears to support newer versions, but it costs a minimum of $67 USD per month:
We support the two most recent major versions at all times
Searchbox might do what you want, and it has a free tier:
For specific version of Elasticsearch please use CLI command with version information as;
heroku addons:add searchbox:starter --es_version=2
Available versions are 0,1,2,5,6 and 7
It isn't clear what minor versions are used.

Elasticsearch 5.6 authentication

I am usig elasticsearch 5.6 version.
Is there a way to add password to elassticsearch without an x-pack plugin and gold license?
I saw that x-pack supports security with basic license, but only from 6.8 version.
Currently, I can't upgrade elasticsearch and look for another way to add authentication (RBAC) to elasticsearch 5.6.
AFAIK Unfortunately, before 6.8 as you already mentioned basic X-pack security is not available and if you need RBAC at field and document level then it's not even available in Gold license and for that, you need to buy platinum or enterprise license.
I would suggest you go through the Elastic stack security section under Elastic subscription to see what is included and what is not included.
Apart from the other answer, you can look at [this shield] (https://www.elastic.co/guide/en/shield/current/index.html)
You can refer this post
This is the way with 5.6 ES and kibana.

Ritiring old logs without using Elasticsearch-curator

I'm running an ELK stack and would like a strategy for automatically retiring logs older than a certain age... I have tried using elasticsearch-curator but it requires python 2.7 and I have python 2.6.6, and am anxious to upgrade python in case I break other packages.
Is there a similar product or does the elasticsearch api cater for such a requirement?
The older versions of curator will work with older versions of ElasticSearch ( I'm using curator version 3.1.0 with a 1.7.1 ES cluster.)
We started out using the Elasticsearch S3 archiving plugin but soon discovered certain limitations when wanting to restore data. We also experienced performance issues with the plugin, which tended to slow down the entire cluster. Since then, we have migrated to a new system in which we archive the data for us and our customers using our own code before indexing the data to Elasticsearch in a clear text format. This gives us all the flexibility we and our customers require.
You may be mistaking the dependency on a given version of the elasticsearch-py module for a version of Elasticsearch. Curator version 3.5.1 requires es-py 2.3, but works with any version of elasticsearch greater than 1.0.

Resources