curious, why would you want to do it programmatically?
the discussion have been moved to https://discuss.elastic.co/ , you might
get more response there.
jason
On Tue, May 26, 2015 at 10:07 PM, mooky nick.mi...@gmail.com
javascript: wrote:
I've been using elastic since about 2009
I've been using elastic since about 2009 ... and I've always found myself
embedding elastic into our app - and configuring it programmatically.
I've always found programmatically configuring the mapping for an index to
be very clunky.
But perhaps I just havent paid close attention to the
On Thursday, September 25, 2014 11:08:44 AM UTC+1, mooky wrote:
The _all field is super-convenient for doing a google-style search across
all fields of a document. The mapping makes it easy to include/exclude
fields from _all in a declarative fashion - including boost levels etc
Having checked the analysis - it does not look like it is the suspect...
On Tuesday, 9 September 2014 12:56:28 UTC+1, Nikolas Everett wrote:
I imaging its caused by your analysis configuration. User the analyze api
and check what is output for all those terms.
On Sep 9, 2014 5:15 AM, mooky
The _all field is super-convenient for doing a google-style search across
all fields of a document. The mapping makes it easy to include/exclude
fields from _all in a declarative fashion - including boost levels etc.
It is a pattern I have been using for many years - by hand using lucene
No suggestions at all?
On Friday, 5 September 2014 17:09:15 UTC+1, mooky wrote:
I am getting the following intermittent failure on random different tests
(I presume during the teardown) when the build is running on TeamCity.
I cant seem reproduce it locally. I get a failure about 1 in 10-20
Anyone have any insights?
On Friday, 5 September 2014 17:09:15 UTC+1, mooky wrote:
I am getting the following intermittent failure on random different tests
(I presume during the teardown) when the build is running on TeamCity.
I cant seem reproduce it locally. I get a failure about 1 in 10
Is (2) expected? Is there a buggette?
Anyone familiar with highlighting have any insight?
On Monday, 8 September 2014 10:16:02 UTC+1, mooky wrote:
I have looked at doing highlighting on _all.
I set store: true, and I am getting results.
I expect the contents of _all to be gobbledigook
Not being too sure of the essence of your question let me fire some random
info at you :)
1) If you use a query (rather than filter) then the aggregation will
reflect the totals for that query. ie the query is global.
2) If you want to do an aggregation that is independent of that query, then
search of ya, I get the following highlights:
1: Yammin
2: Yammin 0.
Is (2) expected? Is there a buggette?
Cheers...
On Thursday, 4 September 2014 18:41:37 UTC+1, mooky wrote:
I am indexing some entities that have up to 140 fields in the resultant
document - ie lots.
I am providing
The aggregation takes into account a query - but not a post-filter. I'm not
sure of the rationale behind the difference.
The java api for traversing results is quite painful - but I think a good
part of that is due to Java the fact that there is very little
polymorphic behaviour between
I am getting the following intermittent failure on random different tests
(I presume during the teardown) when the build is running on TeamCity.
I cant seem reproduce it locally. I get a failure about 1 in 10-20 test
runs.
Its not clear to me why I am getting the failure. Anyone have any
I have a bit of an unusual situation - I am running a single embedded node
of elastic. (it will later expand to more nodes, but for now, this is the
picture).
Is there a way I can get a ClusterHealthStatus.GREEN status rather
than ClusterHealthStatus.YELLOW ?
Cheers
--
You received this
/elasticsearchfr
Le 4 septembre 2014 à 11:59:17, mooky (nick.mi...@gmail.com javascript:)
a écrit:
I have a bit of an unusual situation - I am running a single embedded node
of elastic. (it will later expand to more nodes, but for now, this is the
picture).
Is there a way I can get
I am indexing some entities that have up to 140 fields in the resultant
document - ie lots.
I am providing a simple/powerful google-style search of such entities using
the _all field - however, to make the user's life easier, we do prefix
searches.
(e.g. rather than the user having to type
I tend to agree that knowing the total # of buckets would be universally
useful.
Even though you may only want to show 10 buckets to the user, you may
also want to show that there are 15 more... - and then allow the user to
expand on that to see all 25.
On Tuesday, 2 September 2014
Thats super-cool!
We are using the Java API, but the rest api is super-useful for support.
The security people won't be too happy to find it wide-open - and this will
give us a fig-leaf of security that will keep them happy (we can put the
NodeServlet behind our standard security filter)
The
What do you mean by durability?
Its highly likely that elastic has the same storage guarantees that
cassandra does.
That said, some people like to have the flexibility of having the golden
source elsewhere and the ability to blow away the index re-index at a
whim.
There are a number of
bump.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
I have a bit of an odd requirement in so far as analyzer is concerned.
Wondering if anyone has any tips/suggestions.
I have an item I am indexing (grade) that has a property (name) whose value
can be 0# (99.995%).
I am doing a prefix search on _all.
I want users to be able to search using 99
Thanks. That looks interesting!
On Tuesday, 15 July 2014 16:15:23 UTC+1, vineeth mohan wrote:
Hello Mooky ,
You can apply multiple analyzers to a field -
https://github.com/yakaz/elasticsearch-analysis-combo/
So you can add all your analyzer here and apply it.
Thanks
Vineeth
I see. Thanks.
I wasnt expecting to have to check for shard failures.
Would it make sense to have a config or request setting whereby any shard
failures are reported as exceptions (java api).
In the space where we have been using elastic, partial results are bad. We
would end up having to
Am I on my own with this problem? Have I got it all wrong?
On Wednesday, 2 July 2014 13:21:26 UTC+1, mooky wrote:
Having used elastic aggregations for a little bit (and having used Mongo
aggregations previously), I have been finding a couple of things a bit
difficult/awkward.
I am
made more readable if you strip the ID from the
token before display).
Obviously this would add overheads over using a basic ID.
On Wednesday, July 2, 2014 1:21:26 PM UTC+1, mooky wrote:
Having used elastic aggregations for a little bit (and having used Mongo
aggregations previously), I
I ran into a performance issue today with nested Terms aggregations.
Performance took a 1000x dive (aggregation time went from ~10ms to
~10,000ms) when I added a terms aggregation as a sub-aggregation of an
existing term aggregation.
The nature of the data is that the sub-aggregation will only
Ah. Cheers.
I had looked at that page a few times but missed that.
On Tuesday, 1 July 2014 19:04:56 UTC+1, Glen Smith wrote:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-analyzers.html
On Tuesday, July 1, 2014 6:23:54 AM UTC-4, mooky wrote:
Thanks.
So
Having used elastic aggregations for a little bit (and having used Mongo
aggregations previously), I have been finding a couple of things a bit
difficult/awkward.
I am not sure if its because I don't know how to do it properly - or we
missing a feature/enhancement in elastic.
A common thing I
One thing you can consider is calling refresh() after indexing - which has
the effect I think you are looking for.
There are probably some performance considerations others here can comment
on better than I.
In any case, calling refresh() is what we do.
On Thursday, 26 June 2014 10:25:12
I fall on the side of caring less about spam emails (since I have decent
spam filter on my email) and would rate easy access to the group much
higher.
I tend to add/remove myself from groups all the time - so adding a delay to
adding myself to a group with be a big PITA for me.
-M
On
,
filter: [standard, lowercase]
},
default_search: {
tokenizer: standard,
filter: [standard, lowercase, stop]
},
On Monday, June 30, 2014 12:19:55 PM UTC-4, mooky wrote:
Excellent. Thanks
Hi all,
I have a google-style search capability in my app that uses the _all field
with the default (standard) analyzer (I don't configure anything - so its
Elastic's default).
There are a few cases where we don't quite get the behaviour we want, and I
am trying to work out how I tweak the
,
search_analyzer: custom_search
}
}
}
Note that you can (and often should) set up index analysis and search
analysis differently (eg if you use synonyms, only expand search terms).
Hope I haven't missed the point...
On Monday, June 30, 2014 8:47:36 AM UTC-4, mooky wrote:
Hi
Further to (2). Would it be an improvement to have a different kind of
request for a scrolling search - that way the api could exclude items that
don't make sense (e.g. aggregations, facets, etc)
On Wednesday, 18 June 2014 10:28:06 UTC+1, mooky wrote:
Many thanks Jörg.
Further questions
.
Jörg
On Tue, Jun 17, 2014 at 7:46 PM, mooky nick.mi...@gmail.com javascript:
wrote:
Having hit a bunch of issues using scroll, I thought I better improve my
understanding of how scroll is supposed to be used (and how its not
supposed to be used).
1. Does it make sense to execute
If I understand correctly, we can get an OK response from elastic (ie no
error) but if there are shard failures in the response, it potentially
means that results are incomplete/incorrect. From my observation, we can
get failures on all shards - and elastic still returns OK (which was a bit
Hm, Interesting.
I currently make one request that performs multiple aggregations. All my
aggregations have a filter aggregation as the top level item (all are
different).
Do you think it would be better performance executing multiple requests
with a filterQuery instead?
On Wednesday, 18
I have been having some problem with a failing test (using the
ElasticsearchIntegrationTest) that was testing scrolling.
It took quite a while to notice that in my response was an indication I was
getting a shard failure (my search response was OK, but the response
included shard failures).
I
With a bit of cunning use of the debugger, I managed to get the stacktrace
that was lost.
It appears that maybe the ElasticsearchIntegrationTest environment is the
cause...
This looks like a bug?
java.lang.AssertionError
at
Having hit a bunch of issues using scroll, I thought I better improve my
understanding of how scroll is supposed to be used (and how its not
supposed to be used).
1. Does it make sense to execute a search request with scroll, but
SearchType != SCAN?
2. Does it make sense to execute a
of which SearchType you are using
c) not be affected by the search itself returning zero results
Cheers.
On Tuesday, 17 June 2014 18:46:07 UTC+1, mooky wrote:
Having hit a bunch of issues using scroll, I thought I better improve my
understanding of how scroll is supposed to be used (and how its
According to the documentation, you know when you have reached the end of
the scroll results when you receive zero hits in the response.
However, if your SearchType is SCAN, then you receive zero hits in the
*first* result,
The question is how to avoid this ambiguity.
My code that handles the
Oh, I see.
Can we make any assumption about the scrollId not changing when we reach
the end of the results?
On Monday, 16 June 2014 15:58:20 UTC+1, Ralph Meijer wrote:
On Mon, Jun 16, 2014 at 07:45:00AM -0700, mooky wrote:
[..]
That said, I do notice that when the end of the results
Just to confirm:
Is it correct that in order to automatically clean up the resources
associated with a scroll, you must execute it until zero results are
retrieved?
What about the case when all of the hits are returned in the first result
(ie num hits = total hits)
--
You received this
Is there a way of specifying the scope of an aggregation (if there is I
cant seem to find it)?
I want to achieve the equivalent of a Facet global : true.
Do I need to use facets instead of aggregations in this case?
I am just doing term aggregations - to give the user a dropdown list to
at 12:02 PM, mooky nick.mi...@gmail.com
javascript: wrote:
Is there a way of specifying the scope of an aggregation (if there is I
cant seem to find it)?
I want to achieve the equivalent of a Facet global : true.
Do I need to use facets instead of aggregations in this case?
I am just
Ok. I have written a test case that (if run enough) will reproduce it. Its
an intermittent bug.
I have raised an issue:
https://github.com/elasticsearch/elasticsearch/issues/6435
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe
Turns out it was user error. Please ignore.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion
can zip it and upload it to any
file sharing service, that would work for me.
On Tue, Jun 3, 2014 at 6:41 PM, mooky nick.mi...@gmail.com javascript:
wrote:
By the way this test fails with elastic 1.2 also.
How do I go about uploading an index with aggregation request json, etc
I have an aggregation (filter + daterange) that is giving me an incorrect
result (the count for a bucket is 2 when I expect 1) - but when I search
using the same* criteria, I get only the 1 result I expect.
I am wondering what techniques there are for trying to debug the
aggregation - to try
I have a test that indexes some data, does an aggregation + search to
verify the results.
Then my test changes 1 piece of data and re-indexes (everything).
refresh() is called.
Then I do an aggregation + search again to verify my results.
The search results are correct (ie updated to reflect the
Update elastic to 1.2 - still seeing the same issue...
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this
}
}
}
]
}
}
}
On Tuesday, 6 May 2014 10:34:53 UTC+1, mooky wrote:
I am using elastic 1.1.1.
The index isn't huge (600m) - but it contains financially sensitive
data... will be too problematic legally to allow it offsite. I can try
anonymise the data - see if it can be reproduced that way
By the way this test fails with elastic 1.2 also.
How do I go about uploading an index with aggregation request json, etc?
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send
I want elastic to put its data under the target dir ...
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this
/reference/current/query-dsl-function-score-query.html#_script_score
--
*David Pilato* | *Technical Advocate* | *Elasticsearch.com*
@dadoonet https://twitter.com/dadoonet |
@elasticsearchfrhttps://twitter.com/elasticsearchfr
Le 6 mai 2014 à 11:46:51, mooky (nick.mi
There is a more complete pull request
here: https://github.com/elasticsearch/elasticsearch/pull/5683
On Saturday, 22 March 2014 00:31:33 UTC, mooky wrote:
Fixed. Pull request here:
https://github.com/elasticsearch/elasticsearch/pull/5491
--
You received this message because you
2014 14:34:21 UTC+1, Adrien Grand wrote:
What version of Elasticsearch are you using? If it is small enough, I
would also be interested if you could share your index so that I can try to
reproduce the issue locally.
On Fri, May 2, 2014 at 12:07 PM, mooky nick.mi...@gmail.com javascript
+1, Adrien Grand wrote:
This looks wrong indeed. By any chance, would you have a curl recreation
of this issue?
On Tue, Apr 29, 2014 at 7:35 PM, mooky nick.mi...@gmail.com javascript:
wrote:
It looks like a bug to me - but if its user error, then obviously I can
fix it a lot quicker
Trying to submit a pull request. Getting a 403
-Nick
On Monday, 10 March 2014 17:28:24 UTC, mooky wrote:
Righto - I will try add some.
-Nick
On Wednesday, 5 March 2014 13:48:58 UTC, Jörg Prante wrote:
Yes, there are no tests yet.
Jörg
On Wed, Mar 5, 2014 at 2:24 PM, mooky
Fixed. Pull request
here: https://github.com/elasticsearch/elasticsearch/pull/5491
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Is it practical to have an optimised/flexible implementations?
Re-reading, that sentence doesn't make sense.
What I meant to ask is whether it would be practical to have 2
implementations - an optimised one and a flexible one?
-Nick
On Wednesday, 12 March 2014 11:09:44 UTC, mooky wrote
On Tuesday, 11 March 2014 15:19:24 UTC, Clinton Gormley wrote:
On 7 March 2014 12:46, mooky nick.mi...@gmail.com javascript: wrote:
So the previous, current and next period-end dates are:
2014-02-19, 2014-03-19 2014-04-16.
I define the ranges therefore as:
Overdue: date *2014-02-19*
March
Yes? No?
-Nick
On Friday, 7 March 2014 11:46:48 UTC, mooky wrote:
Hi Clinton
I am doing a date-range aggregation - the ranges are defined by
(financial) exchange rules - and they are just dates (LocalDate's) (ie
there is no time component). The *end* of the period is what is defined
Righto - I will try add some.
-Nick
On Wednesday, 5 March 2014 13:48:58 UTC, Jörg Prante wrote:
Yes, there are no tests yet.
Jörg
On Wed, Mar 5, 2014 at 2:24 PM, mooky nick.mi...@gmail.com
javascript:wrote:
I am ready to create a pull request - its actually quite a simple change
I am ready to create a pull request - its actually quite a simple change.
However, I cant find *any *tests for the existing BigDecimal support ...
does that sound right?
-Nick
On Friday, 28 February 2014 12:09:00 UTC, mooky wrote:
XContentBuilder has support for BigDecimal, but:
1
Does anyone think this is a worthwhile change?
On Wednesday, 26 February 2014 12:41:53 UTC, mooky wrote:
I think its necessary to be able to specify an *include_lower*/
*include_upper* option like with filters.
On Tuesday, 25 February 2014 14:54:24 UTC, Binh Ly wrote:
Yes, you are correct
arithmetic operations in the index.
Maybe the toEngineeringString() was not a smart decision and
toPlainString() works better.
So I would welcome improvements, or should I suggest one in a pull request?
Jörg
On Wed, Feb 26, 2014 at 6:05 PM, mooky nick.mi...@gmail.com javascript:
wrote
I think its necessary to be able to specify an *include_lower*/
*include_upper* option like with filters.
On Tuesday, 25 February 2014 14:54:24 UTC, Binh Ly wrote:
Yes, you are correct. The from is inclusive, and the to is exclusive.
--
You received this message because you are subscribed
In financial services space, we almost never use float/double in our domain
- we always use BigDecimal.
In elastic, I would like to be able to index/store BigDecimal in a lossless
manner (ie what I get back from _source has the same precision, etc as what
I put in).
When I have had to
What are the expected semantics of the from/to fields in a DateRange
aggregation?
Are the from/to values included? Should there be an *include_lower*/
*include_upper* option like with filters?
I want the aggregation to include the lower and upper values - but I
discovered today that it doesnt
,
to : 2014-02-17
}, {
key : March,
from : 2014-02-18,
to : 2014-03-17
}, {
key : April,
from : 2014-03-18,
to : 2014-04-15
} ]
}
}
}
On Monday, 24 February 2014 18:16:07 UTC, mooky wrote:
What are the expected semantics
Excellent. Thanks!
On Tuesday, 18 February 2014 15:28:32 UTC, Binh Ly wrote:
Yes, the correct way would be to index intentLocationDescription as a
multi-field. You don't have to introduce it as multiple fields in your
source document. All you need to do is on the ES mapping, you set that
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-facets-range-facet.html
--Alex
On Tue, Feb 11, 2014 at 2:36 PM, mooky nick.mi...@gmail.com javascript:
wrote:
Bump?
On Monday, 3 February 2014 16:33:02 UTC, mooky wrote:
Hi All,
I need a facet that does
I am using aggregation to give me some reports of items (count) aggregated
by various properties (location or market (or both)).
I am using a term aggregator.
A simplified example of my data looks like this:
{
intentLocationCode: SHANG,
intentLocationDescription: Shanghai area,
What's the general opinion about running elasticsearch on VMWare ESX VM's?
Are many people running elasticsearch reliably in this kind of env?
Assuming the VM is set up with dedicated/guaranteed mem/cpu, are there any
things to be concerned/worried about?
Disc IO Performance? SAN vs local HDD
, February 5, 2014 7:22:08 AM UTC-8, mooky wrote:
What's the general opinion about running elasticsearch on VMWare ESX VM's?
Are many people running elasticsearch reliably in this kind of env?
Assuming the VM is set up with dedicated/guaranteed mem/cpu, are there
any things to be concerned/worried
Hi All,
I need a facet that does exactly what Date Histogram Facet does, but I need
a different (complicated) monthly bucketing.
Rather than the start/end of every month, I need a monthly period that
begins/ends on the friday before the 2nd wednesday of every month
Its been a little while
77 matches
Mail list logo
