jasontedor

5 ms·

1.
by jasontedor 3y ago
Let’s say we do that, use UTC everywhere. You live in London. It’s 3 PM. For you, that’s mid-afternoon. It’s your brother’s birthday. You want to phone him and wish him a happy birthday. He lives in Sydney. In a world without timezones, it’
2.
by jasontedor 4y ago
I think James Gleick had a much better write up about this: http://www.maths.mic.ul.ie/posullivan/A%20Bug%20and%20a%20Cr...
3.
by jasontedor 6y ago
Jason from Elastic here. I want to clarify one aspect here. Elasticsearch and Kibana will be dual licensed under the Elastic License or the SSPL license, not only SSPL. The distributions that we provide will be licensed under the Elastic
4.
by jasontedor 6y ago
Jason from Elastic here. I want to clarify this. Building a SaaS product with Elasticsearch or Kibana on the backend is okay and not prohibited, as long the service is not “managed” Elasticsearch nor Kibana. For example, a music service tha
5.
by jasontedor 6y ago
Jason from Elastic here. >To give the story a bit more context, I always felt that Elastic built on Lucene without giving much back. I would love to understand why you have this perspective? Investing in and contributing to Lucene is a c
6.
by jasontedor 6y ago
I think that the full context of the sentence you quoted will help: > In this case, if you base your number of threads off grepping lscpu you take another dependency (on the util-linux package), which isn’t needed. You also get the wrong
7.
by jasontedor 7y ago
Jason from Elastic here. A shard can handle concurrent writes from clients, there are multiple write threads scaling to the number of logical processors exposed to Elasticsearch, and we have invested in making Lucene accommodate this concur
8.
by jasontedor 7y ago
Jason from Elastic here. It is indeed good reading, but as you say, old. Since then, we have invested tremendously in the [data replication][0] and [cluster coordination][1] subsystems, to the point that we have closed the issues that Kyle
9.
by jasontedor 8y ago
I think this is addressed by the use of k-anonymity which is described in the section of the article titled “Enabling Anonymous Searches with k-Anonymity”.
10.
by jasontedor 9y ago
Jason from Elastic here. We are actively developing cross datacenter replication (internally we are calling it "cross cluster replication" so you will likely see it referred to this in the future but of course this is subject to c
11.
by jasontedor 9y ago
Elastic | Software Engineer (Elasticsearch core/infrastructure team) | Distributed | https://elastic.co/ Elastic is the company behind the Elastic Stack (fka the ELK Stack). The Elasticsearch core/infrastructure t
12.
by jasontedor 9y ago
I'm sorry that you're frustrated. Maybe the following will help? There is such a flag for your use case[1]. Start the node in the Docker container with discovery.type: single-node This allows the node to bind HTTP and trans
13.
by jasontedor 10y ago
Thank you for noticing this, it is not considered experimental anymore. I integrated a change[1] to update the docs; it should percolate through to the site within thirty minutes. [1]: https://github.com/elastic/elastic
14.
by jasontedor 11y ago
Jason from Elastic here. It wasn't the same release as there were critical changes[1] between the RC and the GA, and the RC release will receive no support. [1] https://www.elastic.co/downloads/past-releases/e