How can I download the user docs/documentation/manual for older ElasticSearch for offline usage?
Recently, the online documentation for older versions of ElasticSearch (for example, ElasticSearch 1.3.2) started to show this message:
WARNING: Version 1.3 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
What worries me most is the may be removed part. Right now, we don't have the resources to upgrade our software to support the latest ElasticSearch version, so we will need to keep working with the older versions for a while. How I will be able to give maintenance to our software if the Elastic company decides to remove the documentation for older versions of ElasticSearch? There is any way to download it from https://www.elastic.co/ or build it from some repository?
Thank you very much for your help!
You can clone the official elasticsearch repository to a local machine, change to branch to the version you want, in your cause branch 1.3, then you will have the documentation in the directory docs.
The documentation is in the .asciidoc format, you can try build it following the official instructions, or using other asciidoc to pdf/html converters.
Related
We are running an omnibus version of Gitlab, and need to update to 15.X. However, the instructions state that ElasticSearch must be updated, and that ES is installed separately from GL. From what I am seeing that isn't the case. We did not install ES, instead it appears to have installed with Gitlab as a Ruby gem. Do we still need to update ES manually before the upgrade to GL? Or will it update as a dependency? Any advice here is helpful, we are currently going in circles trying to figure out what needs to happen.
This is only relevant if you have configured the Elasticsearch integration to enable advanced search with Elasticsearch for your GitLab instance. So first check your settings in the admin panel to see if the integration is configured.
If you are not using the integration, then you don't need to worry about updating it and can skip this step for your GitLab upgrade. The ruby elasticsearch gem is just the client library and will be present in any case, so that seems like a red herring for you here.
If you do have the integration configured and are using advanced search, then you must update your ES cluster to 7.x for GitLab 15.0 -- Elasticsearch is NOT bundled with GitLab omnibus or source installations; you must install it (and upgrade it) yourself. From the docs:
Elasticsearch is not included in the Omnibus packages or when you install from source. You must install it separately and ensure you select your version.
I'm trying to update Sonarqube usage to the latest LTS Community version, which at present is version 6.7.5. Prior to the upgrade I have been using sonarqube 5.4 and the Github plugin, and with these when we make Github pull requests the Sonarqube analysis runs in "preview" scan mode and makes comments on the pull request for any issues the scan finds. This setup is largely following this pattern.
However, with the upgrade to 6.7.5 this same flow is no longer working. The Github plugin
"is deprecated, and its functionality more than replaced by the
Developer Edition."
I understand that the Developer version of Sonarqube has pull request commenting built-in, but I have a strong preference to continue using the Community version due to the cost differences. Essentially, something that was once free and part of the open source version seems to have been removed or broken in the latest free and open source version because a similar paid option now exists. So I am trying to find a way to preserve the previous Community version usage with the latest Community Sonarqube version. 6.7.5 Community version runs the Github plugin (even though it the plugin is deprecated), but so far I have been unable to get things to make comments on the Github pull requests.
Is there a combination of parameters/plugins that will allow my 6.7.5 Community version of Sonarqube to analyze and make comments on a Github pull request?
These may be relevant:
https://community.sonarsource.com/t/after-upgrade-to-sq-6-7-5-target-sonar-issues-report-issues-report-light-html-is-not-produced/1921
https://jira.sonarsource.com/browse/SONAR-9770
https://community.sonarsource.com/t/preview-mode-ignored/1234
I believe in my case the issue was that after upgrading the rule sets changed, so the rules I initially thought were being used with 6.7.5 were not in fact being applied. This gave the impression that Sonarqube was not commenting on the pull request and led to my question. But after enabling the rules appropriately I was able to see it comment on GitHub pull requests as expected. So this appears to be a case of user error!
Does all features of Rally work with Elasticsearch 2.3.x or 5.0.0 is the minimum ES version for rally?
I could not find anything related to this in the doc.
Disclaimer: I am the main author of Rally.
The earliest version that works with Rally is Elasticsearch 1.7 (actually, even earlier 1.x versions should work). These features will not work with earlier versions of Elasticsearch:
Benchmarking with plugins works only with 5.x or later: As you might have noted, you can have Rally set up the cluster for you before benchmark or you can use Rally just as a load generator and set up the cluster yourself. In the latter case, you can install plugins on older cluster versions as you see fit and use Rally to generate load. It's just that you cannot use Rally to set up the cluster for you in that case.
Benchmarking source builds works only with 5.x or later: The reason is that Elasticsearch has switched from Maven to Gradle as a build tool with 5.0 and there is no point in supporting two build tools.
In general, there is not much code in Rally that is depending on the version of Elasticsearch. This is rather covered in tracks and cars (see https://github.com/elastic/rally-tracks and https://github.com/elastic/rally-teams respectively) which use dedicated git branches to account for differences between Elasticsearch versions.
Having that said, Elasticsearch 1.x is end of life since January 2017 and in the interest of maintainability, Rally will drop support for older versions of Elasticsearch at some point. However, as long as it is feasible, I want to keep it around.
I am new in elasticsearch and I have by mistake installed 0.90.7 version in my server. Now I want to install shield for this I have to upgrade my elasticsearch version to 1.5 or above. So I need to Upgrade version without loosing existing data. Can anybody help me how to upgrade version to 1.6.1?
You can upgrade your Elasticsearch version from 0.90.x to 1.x in the following way
Cluster restart upgrade process
Before upgrading Elasticsearch, it is a good idea to consult the breaking changes docs.
As per Elasticsearch Documentation before performing an upgrade, it’s a good idea to back up the data on your system.
Is there a stable version of SlickGrid that should be used for deployment or is it recommended practice to take a snapshot of the github repository and use that for deployment? I see a number of tags but none that is very recent (e.g., tag 2.02 is 7 months old and there have been lots of commits since then).
Up to now I have been tracking the SlickGrid github repository for development but I'd like to fix to a version before deploying. It would be nice if there was a recommended stable package download available (maybe there is and I haven't come across it?).
SlickGrid 2.1 is available as a release on github - official mailing list announcement here.