Talk:Elasticsearch

Kibana

Can someone please add something like "ElasticSearch can be used in conjunction with Kibana and Logstash to provide for analysis and visualization of logging data." with a link to https://wiki.riteme.site/wiki/Kibana ? Please feel free to remove this paragraph afterwards. Thanks. 128.131.35.164 (talk) 17:07, 27 May 2015 (UTC)

I agree, this was a major omission, and I've added in the intro (next time, be bold and add it yourself!). :) - IMSoP (talk) 15:55, 16 December 2016 (UTC)

Project doesn't capitalize the 'S'

From the page titles and text on http://www.elasticsearch.org/ , the project does not capitalize the 'S' in Elasticsearch. -- S Page (WMF) (talk) 04:09, 29 August 2013 (UTC)

Requested move

The following discussion is an archived discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section.

The result of the move request was: Page moved - no opposes after a full listing, and reasoning seems valid. Note: Page not yet moved due to the target having a nontrivial edit history. Posting db-move. Any competent admin could also complete this move. (non-admin closure)  — Amakuru (talk) 10:28, 13 November 2013 (UTC)

---

ElasticSearch → Elasticsearch – The 'S' in Elasticsearch is not capitalized per the project page: http://elasticsearch.org Rianjs (talk) 15:45, 5 November 2013 (UTC)

• Support not CamelCase in most reliable sources. In the meanwhile you can change the text in the article body and infobox. W Nowicki (talk) 17:55, 8 November 2013 (UTC)

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.

Rename page to Elastic

Since Elasticsearch changed its name to Elastic, should this page be renamed (and a redirect set up) too?

James Earl Douglas 18:33, 20 May 2015 (UTC) — Preceding unsigned comment added by Earldouglas (talk • contribs)

The article is primarily about the software package, which is still called Elasticsearch. If there were enough to say, a separate article could be created for Elastic, the company. - IMSoP (talk) 15:51, 16 December 2016 (UTC)

Creating Elastic company page

My name is Daniel and I'm an employee at Elastic. One of the previous discussions suggested renaming this page to Elastic, with the response being that this was a page dedicated to the software, and not the company — however, if there were enough information a page could be created. I read that I shouldn't edit this page directly, or try to write new pages myself, but could make suggestions in the discussion. I would like to propose creating a new page for the brand, which I can provide some copy and verifiable references for. Can someone help me with this? — Preceding unsigned comment added by Daniel at Elastic (talk • contribs)

First off, welcome to Wikipedia! Due to your status as an employee of Elastic, you should read our conflict of interest policy before starting on an article for them. If you still wish to do so, I recommend you create a draft first, and have other editors review and contribute to it before publishing. I've left further info on your talk page. Feel free to ask if you have any questions. — AfroThundr ^(talk) 14:21, 7 May 2018 (UTC)

Version history table

I took it out - it was huge and didn't contribute anything useful to this article for the general reader. The project's own website should be consulted for that kind of information.  — Scott • talk 11:18, 1 June 2018 (UTC)

I think we should keep a shorter version that only shows the major versions and currently supported, instead of all of them, like Splunk does. — AfroThundr ^{(u · t · c)} 11:26, 1 June 2018 (UTC)

Yeah, that looks pretty reasonable. Since DoctorCaligari seems keen on keeping them in the article, perhaps they should do the work of reducing it to useful size.  — Scott • talk 19:07, 9 June 2018 (UTC)

Scott I see your point; the table occupied a pretty large proportion of the vertical scroll, so while the identical format (including all out-of-date versions) is used on numerous other OSS pages (Apache HTTP server, Debian Linux release history page, Maria DB, etc.) those pages either have substantially more other content or are pages dedicated to that version history. I'll have a go at creating an abbreviated table as you and AfroThundr3007730 describe.DoctorCaligari (talk) 09:33, 13 June 2018 (UTC)

DoctorCaligari, did you ever get around to making an abbreviated version table? If not, we can just put the highlights in prose. — AfroThundr ^{(u · t · c)} 13:56, 11 July 2018 (UTC)

WP:NOTDIRECTORY removed

Extensive lists of customers, partners, providers and products should be hosted on the company's official website - Wikipedia is not a directory for such detailed self-sourced information (see WP:NOTDIRECTORY for more info). Information about noteworthy customers, partners, providers and products can be briefly added of course, but should be covered in prose with some context, and these details must be based on independent reliable sources to establish relevance. GermanJoe (talk) 19:15, 21 August 2018 (UTC)

License change

Elasticsearch is no longer in whole released under the Apache 2 license. Some functionality is released under the Elastic License. Here's the commit that replaces the Apache license file. Can someone please update this?

109.243.241.80 (talk) 20:36, 1 January 2019 (UTC)

As of Jan 2021, starting with the next Elasticsearch release, it is no longer distributed under an OSI approved license. See . Should it be removed from the Wikipedia maintained lists of free software, such as "Free software programmed in Java (programming language)" and "Free search engine software"? 100.17.21.75 (talk) 22:20, 25 January 2021 (UTC)

Source-available software seems more appropriate category after the license change, in line with other software that is licensed under Server Side Public License, e.g. MongoDB. Tunkki-1970 (talk) 11:49, 26 January 2021 (UTC)

References

What the heck is it?

I came here hoping to get an overview of what Elasticsearch is, and all I get is that it's a search engine (I already guessed that from the name) with certain properties (I'd have to follow every link to understand what those are) and certain licenses. (Ok, maybe some people need to know the license, and maybe I will some day, but in the lede?!) I gather it's document search, and I suppose it must be faster than grep, or else why? But it doesn't say that. How does it achieve its speed, indexing? What does it index, individual words (tokens)? Words in context? Word pieces? And what is the use case, as opposed to searching docs with grep etc.? Does it only become more useful than grep when the size is > X? Under what circumstances would I use it, and under what circumstances would a relational db, or some other kind of db, be better? And so forth. Mcswell (talk) 00:54, 25 October 2019 (UTC)

Fair points, perhaps the features listed in the source code README could be included to answer those questions - Phorque (talk) 13:01, 9 June 2020 (UTC)

103.42.216.223 (talk) 20:20, 4 August 2020 (UTC)

Reported Elasticsearch data breaches Section

This section seems quite out of place as these do not seem to be data breaches related to security issues with Elasticsearch. They are just general data breaches where servers have been accessed through other means, be that backdoors or misconfigured server. No other database page has similar, see MySQL, Microsoft_SQL_Server, MongoDB etc. Recommend remove this section. Entirety (talk) 15:18, 20 January 2021 (UTC)

I agree, there should be consistency with the database pages. I'm also of the opinion that third-party data breaches ought to be documented elsewhere. Jamie.mansfield (talk) 00:21, 21 January 2021 (UTC)

Agreed. Done. Note this was done twice before and reverted without engaging in discussion here. ★NealMcB★ (talk) 02:31, 23 January 2021 (UTC)