Mark Harwood
@elasticmark.bsky.social
Ex elasticsearch core search team.
4,000 now? 😮
Exciting step for you, all the best.
Exciting step for you, all the best.
October 25, 2025 at 7:47 AM
4,000 now? 😮
Exciting step for you, all the best.
Exciting step for you, all the best.
True that a lot of apps don’t need distributed but the other big consideration is opening up Lucene to non-Java apps with client libs for Python, JavaScript, ruby etc etc.
December 5, 2024 at 4:59 PM
True that a lot of apps don’t need distributed but the other big consideration is opening up Lucene to non-Java apps with client libs for Python, JavaScript, ruby etc etc.
It follows a principle of mine - plain text syntaxes like regex or Lucene query string are confusing for end users. Use them for quick input by all means, but a graphical editor for a more structured data format can help remove the problems inherent with plain text syntax.
December 1, 2024 at 10:46 AM
It follows a principle of mine - plain text syntaxes like regex or Lucene query string are confusing for end users. Use them for quick input by all means, but a graphical editor for a more structured data format can help remove the problems inherent with plain text syntax.
Nice. I proposed a new feature for elasticsearch relating to help solve some regex pain some time ago github.com/elastic/elas...
New API to debug and test Regex query expressions. · Issue #57033 · elastic/elasticsearch
Regular expression queries are likely to become much more popular with the forthcoming introduction of the wildcard field. In Lucene we opened up access to some of the internals to get detailed par...
github.com
December 1, 2024 at 10:31 AM
Nice. I proposed a new feature for elasticsearch relating to help solve some regex pain some time ago github.com/elastic/elas...
How about indexing a fields token count using the “token_count” field type?
You’d need to run a query past the _analyze api to get the number of query tokens first but your phrase query could then sit alongside another mandatory clause with the token count
You’d need to run a query past the _analyze api to get the number of query tokens first but your phrase query could then sit alongside another mandatory clause with the token count
November 18, 2024 at 9:22 PM
How about indexing a fields token count using the “token_count” field type?
You’d need to run a query past the _analyze api to get the number of query tokens first but your phrase query could then sit alongside another mandatory clause with the token count
You’d need to run a query past the _analyze api to get the number of query tokens first but your phrase query could then sit alongside another mandatory clause with the token count
When the content being searched isn’t human-generated eg log files there is no consensus on where words begin and end. Regex type searches need to match *anywhere* in this content. See use of ngrams here: www.elastic.co/blog/find-st...
Find strings within strings faster with the Elasticsearch wildcard field
Introducing the new Elasticsearch “wildcard” field type for searching for patterns within strings. With this new field type, we've wrapped up the best practices for efficiently indexing and searching ...
www.elastic.co
November 13, 2024 at 1:52 PM
When the content being searched isn’t human-generated eg log files there is no consensus on where words begin and end. Regex type searches need to match *anywhere* in this content. See use of ngrams here: www.elastic.co/blog/find-st...