New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for highlighting of phrase prefix queries #1065
Commits on Jun 22, 2012
-
Rest API: Add
HEAD
support for/{index}/{type}/{id}
to quickly ch……eck if doc exists or not, closes elastic#2047.
Commits on Jun 23, 2012
-
-
-
River name re-use not possible between node shutdowns, closes elastic…
…#1921. This effectively happens because we don't flush before deleting a mapping, which causes it to still reply the changes happening for it on the transaction log, meaning the mapping are still around on the index level.
-
Commits on Jun 24, 2012
Commits on Jun 25, 2012
-
-
-
don't double set settings with es.default. or elasticseearch.default.
though harmless, since we don't have any "default" component, and effectively has not effect on the settings used, it still puts settings that we don't really need
-
deb package fails to start elasticsearch
The ability to use es.default prefix broke the deb package that uses it now.
-
-
Stored Compression: failure to fetch document in certain cases (read …
…failure, index compression works), closes elastic#2055.
Commits on Jun 26, 2012
Commits on Jun 27, 2012
-
-
Setting index to no ends up using by default the "keyword" analyzer o…
…n it, which means one can't highlight on it when searching on _all, closes elastic#2062.
-
Allow the use of "doc" as the update source when a script is not specified. New fields are added, existing fields are overwritten, and maps are merged recursively.
-
Commits on Jun 28, 2012
-
Have rest request also allow to get the content as a streamable
(note, this will break plugins that implement a rest handler..., like wares, thrift, and memcached, until they are upgraded)
-
dangling index handling might still remove the state files for the da…
…ngling index, closes elastic#2065.
-
Commits on Jun 29, 2012
Commits on Jun 30, 2012
Commits on Jul 1, 2012
-
better failure message when failing to detect compressor on compresse…
…d transport stream
-
ElasticSearchIllegalStateException: stream marked as compressed, but …
…no compressor found on transport layer, closes elastic#2076.
-
don't delete shards state in the state handle, but let the indices st…
…ore eventually delete it based on its logic of when to delete a shard
-
Commits on Jul 2, 2012
-
improve dangling index support to not detect explicit deleted index a…
…s dangling, harden when we delete the _state of an index
-
Commits on Jul 4, 2012
Commits on Jul 5, 2012
-
-
when needing to copy over the bytes from the netty content channel, z…
…ero it out so ti can be GC'ed
-
Commits on Jul 6, 2012
-
Thread Pool: Allow to configure the query_type for fixed thread pool …
…(linked/array), defaults to array, closes elastic#2086.
-
First phase at improving buffer management and reducing even further buffer copies. Introduce a BytesReference abstraction, allowing to more easily slice and "read/write references" from streams. This is the foundation for later using it to create smarter buffers on top of composite netty channels for example (which http now produces) as well as reducing buffer copies when sending transport/rest responses.
Commits on Jul 7, 2012
-
-
move rest request to provide content as BytesReference
this allows for better buffer usage, specifically when forwarding requests to other nodes
-
with the new bytes reference abstraction, and the new composite buffer handling in frame decoder, it makes more sense to move back and use netty frame decoder again, since we can easily slice refernces acorss composite buffers, and reduce copies when using compression
-
Commits on Jul 8, 2012
Commits on Jul 9, 2012
-
-
Stored binary fields to change internal representation (break Java AP…
…I if used), closes elastic#2092.
-
yuck!, hack around snappy printing to System.err the failure to load …
…its library if its not found
-
Introduce Text abstraction, allowing for improved representation of s…
…trings, apply to HighlightedField (breaks backward for Java API from String to Text), closes elastic#2093. By introducing the Text abstraction, we can keep (long) text fields in their UTF8 bytes format, and no need to convert them to a string when serializing it back to Json for example. The first place we can apply this is to highlighted text, which can be long.. . This does breaks backward comp. for people using the Java API where the HighlightField now has a Text as its content, and not String.
Commits on Jul 10, 2012
-
-
propagate cluster event to shard and meta states in local gateway eve…
…n when state persistence is disabled, so they can act on it if needed
-
-
Commits on Jul 11, 2012
Commits on Jul 12, 2012
Commits on Jul 14, 2012
Commits on Jul 19, 2012
Commits on Jul 21, 2012
-
*:* query string query should resolve to match_all query, since the w…
…ildcard field support, it no longer does
-
Commits on Jul 22, 2012
Commits on Jul 27, 2012
Commits on Jul 28, 2012
Commits on Jul 29, 2012
-
bytes reference to know how to convert to channel buffer, so it can b…
…e used directly when sending it over with netty
Commits on Jul 30, 2012
-
Transport/Http: Remove explicit setting of send/receive buffer, and i…
…mprove netty receive buffer predictor, closes elastic#2124.
-
-
-
try harder to load the default mapping from the class load, and if we…
… fail, just use the default value (which people really never change).
Commits on Jul 31, 2012
-
-
-
expose the max direct memory allowed in jvm info, and guess better th…
…en receive buffer size predictor size based on it
-
upgrade to latest testng, improve console output when running test, a…
…dd more options as env vars when using maven
-
-
-
Commits on Aug 1, 2012
-
rename Test to Tests, so it will be executed as part of the mvn tests…
… as well, reformat a bit
Commits on Aug 2, 2012
-
-
-
add to the keep alive thread name the version number, so it will be s…
…impler to know from stack traces the es version
-
-
Commits on Aug 3, 2012
Commits on Aug 4, 2012
-
better percent calc for hot threads, including more details on top th…
…reads (time out of interval)
Commits on Aug 6, 2012
-
-
create a unique recovery id when recovering from a peer shard instead…
… of using shard id this allows to handle better cases where we need to cancel an existing recovery
Commits on Aug 7, 2012
-
Allow custom type_table to be passed to Lucene's WordDelimiterFilter(…
…) constructor, instead of just the default
Commits on Aug 8, 2012
Commits on Aug 9, 2012
-
-
handle null query returning from query parsers properly
now that we support "null" queries, for example, when parsing a query and its lenient, make sure to handle it where applicable
-
Update API: Update through an alias with routing configured on it fai…
…l to use the routing, closes elastic#2155.
Commits on Aug 13, 2012
-
-
-
-
-
-
Remove / deprecated omit_term_freq_and_positions in favor of IndexOpt…
…ions exposed via mapping API
-
-
more improvements for handling of large / many mappings by batching t…
…he removal of mappings
-
Commits on Aug 16, 2012
Commits on Aug 18, 2012
Commits on Aug 19, 2012
Commits on Aug 20, 2012
-
-
change mappersAdded flag to mappingsModified to better reflect any po…
…ssible change in mappings, not just additions
-
All Field: Automatically detect when field level boosting is used, an…
…d optimize when its not, closes elastic#2189.
-
-
Commits on Aug 21, 2012
-
-
-
-
small optimization for global facet with facet filter, by removing th…
…e double check on the facet filter
-
when using wildcard notation delete all indices might kick in even th…
…ough its disabled
-
Enabled the option of configuring plugin types in the settings. This …
…will also help in tests when testing plugin related functionality
Commits on Aug 22, 2012
-
no need to optimize on the bool query parser, we already do that in t…
…he optimizeQuery method
-
MinimumNumberShouldMatch inconcistency, closes elastic#2194
Streamline the use of minimum should match to all relevant queries to accept `minimum_should_match`, and allow all relevant queries to accept the advanced "string" based config
-
Commits on Aug 23, 2012
-
Reduce index.shard.recovery.concurrent_streams from 5 to 3 to reduce …
…the load when doing recovery, closes elastic#2199. the index.shard.recovery.concurrent_streams controls how many streams are opened from a recovery source to a recovery target to transfer index files. Reduce it from 5 to 3 to reduce the load when doing recovery (for example, due to relocation). Note, recent changes in network buffering will mean that recovery will progress considerably faster, so this change will not affect recovery times.
-
-
-
A Bulk UDP service is a service listening over UDP for bulk format requests. The idea is to provide a low latency UDP service that allows to easily index data that is not of critical nature. The Bulk UDP service is disabled by default, but can be enabled by setting `bulk.udp.enabled` to `true`. The bulk UDP service performs intenral bulk aggregation of the data and then flushes it based on several parametres: * `bulk.udp.bulk_actions`: The number of actions to flush a bulk after, defaults to `1000`. * `bulk.udp.bulk_size`: The size of the current bulk request to flush the request once exceeded, defaults to `5mb`. * `bulk.udp.flush_interval`: An interval after which the current request is flushed, regarldess of the above limits. Defaults to `5s`. * `bulk.udp.concurrent_requests`: The number on max in flight bulk requests allowed. Defaults to `4`. The network settings allowed are: * `bulk.udp.host`: The host to bind to, defualts to `network.host` which defaults to any. * `bulk.udp.port`: The port to use, defaults to `9700-9800`. Here is an example of how it can be used: > cat bulk.txt { "index" : { "_index" : "test", "_type" : "type1" } } { "field1" : "value1" } { "index" : { "_index" : "test", "_type" : "type1" } } { "field1" : "value1" } > cat bulk.txt | nc -w 0 -u localhost 9700
-
Commits on Aug 24, 2012
-
* Fixed an issue where dynamic update to minimum_master_nodes settings would not take immediate effect * Added LocalNodeMasterListener support to the ClusterService. Enables listening to when the local node becomes/stopped being a master
-
Commits on Aug 25, 2012
Commits on Aug 27, 2012
Commits on Aug 31, 2012
-
Added a global ignore_malformed index setting. elastic#2220 Also exte…
…nded the ignore_malformed support to TTL, Ip and timestamp field types.
-
-
-
move spatial4j and jts to be optional dependencies
allowing data and client nodes to work without them, disabling shapes if needed
Commits on Sep 1, 2012
-
use java to when no JAVA_HOME defined
remove using "which java", which will give a better error message when java is not available
Commits on Sep 2, 2012
-
Update Settings API: Allow body request to be wrapped with
settings
…… element to conform with other APIs, closes elastic#2227.
-
-
Commits on Sep 3, 2012
-
Shard Allocation:
index.routing.allocation....
settings do not "rem……ove" the setting on empty string, closes elastic#2229.
-
-
-
Nodes level API: Allow to specify
data:true
to only execute the API……s on data nodes, closes elastic#2232
Commits on Sep 4, 2012
Commits on Sep 5, 2012
Commits on Sep 6, 2012
-
-
Added proper headers for cross-origin resource sharing (CORS) with Ajax
Previously, when responding to Ajax requests, elasticsearch did not send proper headers for cross-origin resource sharing (CORS) -- see issues elastic#828, elastic#2186. With this commit, Ajax requests should be working. Example: jQuery.ajax({ url: "http://localhost:9200/_search", type: "POST", contentType: 'application/json; charset=UTF-8', success: function(data) { console.log(data) } }); See: * http://www.nczonline.net/blog/2010/05/25/cross-domain-ajax-with-cross-origin-resource-sharing/ * http://www.w3.org/TR/cors/#access-control-allow-headers-response-header Closes elastic#2186, fixes elastic#828
-
allow to configure cors on http
Allow to configure cors on http, if its enabled or not, and what it should output
-
Commits on Sep 7, 2012
Commits on Sep 12, 2012
-
-
internal custom allocation commands
add support for internal custom allocation commands, including allocation, move, and cancel (shard). also, fix elastic#2242, which causes the cluster state to be in inconsistent state when a shard being the source of relocation is failed
Commits on Sep 13, 2012
-
Added
has_parent
filter (elastic#2243)The `has_parent` filter accepts a query and a parent type. The query is executed in the parent document space, which is specified by the parent type. This filter return child documents which associated parents have matched. For the rest `has_parent` filter has the same options and works in the same manner as the `has_child` filter. This is an experimental filter. Filter example ################### ``` { "has_parent" : { "parent_type" : "blog" "query" : { "term" : { "tag" : "something" } } } } ``` The `parent_type` field name can also be abbreviated to `type`. Memory considerations ############### With the current implementation, all _id values are loaded to memory (heap) in order to support fast lookups, so make sure there is enough mem for it. This issue originates from issue elastic#792
Commits on Sep 14, 2012
-
-
Improve
has_child
filter / query performance (elastic#2251) Added a…… new has_child filter implementation, that works _uid based instead of bitset based. This implementation is about ~2 till ~6 times (depending on the query) faster than the already existing bitset based implementation.
-
fix cleanup of of has child/parent
check if the collected uids were processed before trying to push them back to the cache
-
Added has_parent query The
has_parent
query works the same as the `……has_parent` filter, by automatically wrapping the filter with a constant_score. It has the same syntax as the `has_parent` filter. Closes elastic#2254
-
Clean up has_parent query code Renamed some exception messages and re…
…moved method from builder
Commits on Sep 15, 2012
-
-
The reroute command allows to explcitiyly execute a cluster reroute a…
…llocation command including specific commands. For example, a shard can be moved from one node to another explicitly, an allocation can be canceled, or an unassigned shard can be explicitly allocated on a specific node. Here is a short example of how a simple reroute API call: curl -XPOST 'localhost:9200/_cluster/reroute' -d '{ "commands" : [ {"move" : {"index" : "test", "shard" : 0, "from_node" : "node1", "to_node" : "node2"}}, {"allocate" : {"index" : "test", "shard" : 1, "node" : "node3"}} ] }' An importnat aspect to remember is the fact that once when an allocation occurs, the cluster will aim at rebalancing its state back to an even state. For example, if the allocation includes moving a shard from `node1` to `node2`, in an "even" state, then another shard will be moved from `node2` to `node1` to even things out. The cluster can be set to disable allocations, which means that only the explicitl allocations will be performed. Obviously, only once all commands has been applied, the cluster will aim to be rebalance its state. Anohter option is to run the commands in "dry_run" (as a URI flag, or in the request body). This will cause the commands to apply to the current cluster state, and reutrn the resulting cluster after the comamnds (and rebalancing) has been applied. The commands supporterd are: * `move`: Move a started shard from one node to anotehr node. Accepts `index` and `shard` for index name and shard number, `from_node` for the node to move the shard "from", and `to_node` for the node to move the shard to. * `cancel`: Cancel allocation of a shard (or recovery). Accepts `index` and `shard` for index name and shar number, and `node` for the node to cancel the shard allocation on. * `allocate`: Allocate an unassigned shard to a node. Accepts the `index` and `shard` for index name and shard number, and `node` to allocate the shard to. It also accepts `allow_primary` flag to explciitly specify that it is allowed to explciitly allocate a primary shard (might result in data loss). closes elastic#2256
Commits on Sep 17, 2012
-
-
-
Disable allocation: New indices allocation not to be disabled by default
When setting cluster.routing.allocation.disable_allocation, it causes new indices primary shards to not be allocated. By default, new indices created should allow to, at the very least, allocate primary shards so they become operations. A new setting, cluster.routing.allocation.disable_new_allocation, allows to also disable "new" allocations. closes elastic#2258.
-
Commits on Sep 18, 2012
-
Added better error handling for has_child, has_parent and top_children.
If has_parent, has_child or top_children are executed incorrectly then a better exception is thrown. This gives a better error description when one of these queries or filters is being used in count api. Closes elastic#2261
Commits on Sep 19, 2012
-
-
Added id cache size to nodes stats api
Also added bloom cache size the node *rest* api Closes elastic#2264
-
-
don't serialize ignore_unmapped to mapping on default value
fix ignore_unmapped being serialized as part of the mappings even though it has a default value and not explicitly set
Commits on Sep 20, 2012
Commits on Sep 21, 2012
-
The types exists api checks whether one or more types exists in one or more indices. ## Example usage curl -XHEAD 'localhost:9200/twitter/tweet' ## Options * `index` - One or more indices. Either specified as query string parameter or in the uri path. * `type` - One or more types. Either specified as query string parameter or in the uri path. * `ignore_missing` - Determines what type of indices to exclude from a request. The option can have the following values: `none` or `missing`. Closes elastic#2273
-
-
Norms field is ignored when doing a match_all query
we shouldn't optimize a match all query if it has norms associated with it, fixes elastic#2277
-
This allows to more easily identify when illegal content is being sent to the transport port closes elastic#2280
Commits on Sep 22, 2012
-
add node version to each request/response transport message
a version associated with each request, and having it associated with the stream when (de)serializing, can allow us in the future to better support cross version communication
-
-
Commits on Sep 23, 2012
Commits on Sep 24, 2012
-
Fixed score explain is for
custom_filters_score
query.Only the explain of the filter was included. This fix adds an explain for the inner query and wraps it in a top-level explanation.
-
Bulk Delete item when broadcast to all shard (lack of routing) might …
…not be applied correctly closes elastic#2285.
Commits on Sep 26, 2012
-
introduce TransportRequest (with optional headers)
introduce a new class, TransportRequest, which includes headers. This class can be used when sending requests over the transport layer, and ActionRequest also extends it now. This is the first phase of the refactoring part in the transport layer and action layer to allow for simpler implementations of those as well as simpler "filtering" capabilities in the future
-
Commits on Sep 27, 2012
-
a class that needs to be used when sending a response over the transport layer, with an option to have headers
Commits on Sep 28, 2012
-
-
make sure to pass the updated settings from the plugins to the module…
…s with transport client
-
-
Fixed NPE when using
has_parent
orhas_child
filter/query.The NPE occurred when for an arbitrary segment no parent documents exist for a has_parent filter/query and no child documents exist for a has_child filter/query. Closes elastic#2297
-
return null instead of empty doc set
null can more easily be optimized in other filters
-
Commits on Sep 29, 2012
-
-
move cleaning filter cache on closed readers to separate thread
improve cleaning the global weighted cache when a reader closes, move it to a separate thread, so iterating over the cache entries will nto happen on each segment closed, but instead be "bulked"