Re: copy_to and boost factor
Thanks Jörg.
On Tuesday, December 30, 2014 2:43:20 PM UTC+5:30, Jörg Prante wrote:
> Boosting is not supported in copy_to, see
>
> https://github.com/elasticsearch/elasticsearch/pull/4972
>
> Alternative, as quoted from the commit message
>
> "Instead, users should either (1) query the common field AND the field
> that requires boosting, or (2) the multi_match query will soon be able to
> perform term-centric cross-field matching that will allow per-field
> boosting at query time (coming in 1.1)."
>
> See my multi_match gist for an example
>
> https://gist.github.com/jprante/85126685973311603c8a
>
> Jörg
>
> On Tue, Dec 30, 2014 at 9:36 AM, Preeti Jain > wrote:
>
>> Hi,
>>
>> Does the individual boost factor get honoured for fields getting copied
>> into a custom _all field via copy_to option?
>> I am facing issues with the behavior. Have a look at the example below
>>
>> PUT localhost:9200/investigations/TestCustom/_mapping
>> {
>> "TestCustom": {
>> "properties": {
>> "custom_all":{
>> "type": "string"
>> },
>> "name":{
>> "type": "string",
>> "copy_to":"custom_all",
>> "boost":2.0
>> },
>> "surName":{
>> "type": "string",
>> "copy_to":"custom_all"
>> },
>> "dateRecorded":{
>> "type": "date",
>> "copy_to":"custom_all"
>> },
>> "Id":{
>> "type": "long",
>> "copy_to":"custom_all"
>> }
>> }
>> }
>> }
>>
>> Fiels "name" has been given a boost factor of 2.0
>>
>> I post 2 documents now
>>
>> POST localhost:9200/investigations/TestCustom/5
>> {
>> "surName":"Preeti"
>> }
>> POST localhost:9200/investigations/TestCustom/6
>> {
>> "name":"Preeti"
>> }
>>
>> and then search the custom_all field
>>
>> GET localhost:9200/investigations/TestCustom/_search
>> {
>> "query":{
>>"query_string": {
>>"default_field": "custom_all",
>>"query": "Preeti"
>> }
>> }
>> }
>>
>> I expected document with id 6 to be the top result but the results were
>>
>> {
>>"took": 40,
>>"timed_out": false,
>>"_shards": {
>> "total": 5,
>> "successful": 5,
>> "failed": 0
>>},
>>"hits": {
>> "total": 2,
>> "max_score": 1,
>> "hits": [
>> {
>> "_index": "investigations",
>> "_type": "TestCustom",
>> "_id": "5",
>> "_score": 1,
>> "_source": {
>>"surName": "Preeti"
>> }
>> },
>> {
>> "_index": "investigations",
>> "_type": "TestCustom",
>> "_id": "6",
>> "_score": 1,
>> "_source": {
>>"name": "Preeti"
>> }
>> }
>> ]
>>}
>> }
>>
>> Is this expected behavior?
>>
>> --
>> 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 elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/79af9adb-5dce-4a7a-897b-16cd962c8a40%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/elasticsearch/79af9adb-5dce-4a7a-897b-16cd962c8a40%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
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
https://groups.google.com/d/msgid/elasticsearch/54ed8625-a8bc-4be4-b48a-18b364d51a66%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
copy_to and boost factor
Hi,
Does the individual boost factor get honoured for fields getting copied
into a custom _all field via copy_to option?
I am facing issues with the behavior. Have a look at the example below
PUT localhost:9200/investigations/TestCustom/_mapping
{
"TestCustom": {
"properties": {
"custom_all":{
"type": "string"
},
"name":{
"type": "string",
"copy_to":"custom_all",
"boost":2.0
},
"surName":{
"type": "string",
"copy_to":"custom_all"
},
"dateRecorded":{
"type": "date",
"copy_to":"custom_all"
},
"Id":{
"type": "long",
"copy_to":"custom_all"
}
}
}
}
Fiels "name" has been given a boost factor of 2.0
I post 2 documents now
POST localhost:9200/investigations/TestCustom/5
{
"surName":"Preeti"
}
POST localhost:9200/investigations/TestCustom/6
{
"name":"Preeti"
}
and then search the custom_all field
GET localhost:9200/investigations/TestCustom/_search
{
"query":{
"query_string": {
"default_field": "custom_all",
"query": "Preeti"
}
}
}
I expected document with id 6 to be the top result but the results were
{
"took": 40,
"timed_out": false,
"_shards": {
"total": 5,
"successful": 5,
"failed": 0
},
"hits": {
"total": 2,
"max_score": 1,
"hits": [
{
"_index": "investigations",
"_type": "TestCustom",
"_id": "5",
"_score": 1,
"_source": {
"surName": "Preeti"
}
},
{
"_index": "investigations",
"_type": "TestCustom",
"_id": "6",
"_score": 1,
"_source": {
"name": "Preeti"
}
}
]
}
}
Is this expected behavior?
--
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
https://groups.google.com/d/msgid/elasticsearch/79af9adb-5dce-4a7a-897b-16cd962c8a40%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
fs river - Error while reading content
Hi,
I'm using elasticsearch version 1.0.1 that is installed on linux machine.
I have created fs river to index content from file system. The river
definition is
curl -XPUT 'http://localhost:9200/_river/riverTest/_meta' -d '{
"type": "fs",
"fs": {
"url": " /data01/test/NewVehicleFiles1/",
"json_support" : true
},
"index": {
"index": "investigations",
"type": "Vehicle"
}
}'
The river gets started, however, the indexing fails due the error mentioned
below
[fr.pilato.elasticsearch.river.fs.river.FsRiver] [North] [fs][riverTest]
Error while indexing content from /data01/test/NewVehicleFiles1
ES user has full access to the content directory(
/data01/test/NewVehicleFiles1).
What could be the issue?
Regards,
Preeti
--
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
https://groups.google.com/d/msgid/elasticsearch/835a870f-a29f-4c33-b260-afc92d13b8c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Aalyzer issue - terms not getting tokenized on whitespace
Hi,
We are using elasticsearch versionb 1.01.1. I did the following test for
analyzer
PUT /test
{
"settings":{
"analysis": {
"analyzer": {
"whitespace":{
"type": "pattern",
"pattern":"s+"
}
}
}
}
}
GET /testallnext/_analyze?analyzer=whitespace&pretty=1&text='Preeti,Jain
test'
I expected that the text will be broken into 2 token Preeti,Jain and test.
However, the result that I got was
{
"tokens": [
{
"token": "'preeti,jain test'",
"start_offset": 0,
"end_offset": 18,
"type": "word",
"position": 1
}
]
}
What is going wrong?
Our usecase requires special character to be indexed and searchable. For eg
if I index 2 documents ,one containing text "A+B" in one of the fields and
another one containing "A B" in the same field and then query ES for term
"A+B", I should get only one result.
What kind of tokenizer should be used for my purpose? I can't use
not_analyzed option on fields as they need to be anlyzed for phonetics and
synonyms.
Thanks,
Preeti
--
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
https://groups.google.com/d/msgid/elasticsearch/381fc76a-d480-4cd0-ba97-01102071518b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Illegal unicode escape sequence error
Hi Brian, Could you please share your java code? Did you update the entire document or just one field? Our requirement is update specific fields as well so just wondering how setSource would work there? Regards, Preeti On Wednesday, April 9, 2014 3:43:00 AM UTC+5:30, InquiringMind wrote: > > Preeti, > > I just updated my Java update command to allow the source JSON to be > specified (it typically created the source from one or more name=value > pairs). It reads the JSON from a file so that there is no Bash nor non-ES > Java interpretation of the \u sequences. > > I updated the same record several times in a row without any failures or > exceptions of any kind. Queries always return the most recently updated > version of the document and the responses reflect all changes that were > made as well as the expected version number. > > So, I am sure that using the *setScript* method is incorrect, and you > should be using the *setSource* method for your use case. > > Regards, > Brian > -- 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 https://groups.google.com/d/msgid/elasticsearch/93e2f65e-84c9-490c-b7c9-cfa356d81b98%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Illegal unicode escape sequence error
Thank you so much Brian for all your efforts.
The first time indexing of data containing unicode characters work
perfectly fine for us.
We are able to index data and query it without any issues.
The issue occurs when we are trying to update data. Strange thing is we are
using the same routine to convert our data in JSON, both, for first time
indexing and for update.
You seem to be right in saying that issue is with setScript method.
For now we have added one more step to convert unicode to characters(like \u003
to <) and then pass it on to setScript for update
The updated content gets posted without any issue.
Thanks,
Preeti
On Thursday, April 3, 2014 6:13:51 PM UTC+5:30, Preeti Jain wrote:
>
> Hi,
>
> We are using elasticsearch version 1.0.1
> For updating one of the ES docs, following script is being passed to
> updaterequestbuilder via setScript method.
>
> ctx._source.operation= {
> "operationID": 290,
> "opsThreatLevel": "Low",
> "opsName": "OPERATION_SIN",
> "opsStartDate": "2014-04-01T00:00:00",
> "opsRefNumber": "10245678",
> "opsEndDate": "2014-04-23T00:00:00",
> "opsDescription": "\u003cp\u003eFake Operation\u003c/p\u003e",
> "opsComments": "\u003cp\u003efake clues\u003c/p\u003e",
> "dateCreated": "2014-04-02T00:00:00"
> }
>
> When the update request gets executed we get following exception
>
> Exception in thread "main"
> org.elasticsearch.ElasticsearchIllegalArgumentException: failed to execute
> script
> at
> org.elasticsearch.action.update.UpdateHelper.prepare(UpdateHelper.java:153)
> at
> org.elasticsearch.action.update.UpdateHelper.prepare(UpdateHelper.java:80)
> at
> org.elasticsearch.action.update.TransportUpdateAction.shardOperation(TransportUpdateAction.java:189)
> at
> org.elasticsearch.action.update.TransportUpdateAction.shardOperation(TransportUpdateAction.java:185)
> at
> org.elasticsearch.action.update.TransportUpdateAction.shardOperation(TransportUpdateAction.java:64)
> at
> org.elasticsearch.action.support.single.instance.TransportInstanceSingleOperationAction$AsyncSingleAction$1.run(TransportInstanceSingleOperationAction.java:192)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: [Error: illegal unicode escape sequence]
> [Near : {... Description": "\u003cp\u003eFake Operation\u003c/p }]
>
> The unicode characters are not getting recognized. How to resolve this??
>
> Regards,
>
> Preeti
>
>
>
--
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
https://groups.google.com/d/msgid/elasticsearch/4cd5fc57-3dee-4e98-ba4b-a6a1dc884c01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Illegal unicode escape sequence error
Hi,
We are using elasticsearch version 1.0.1
For updating one of the ES docs, following script is being passed to
updaterequestbuilder via setScript method.
ctx._source.operation= {
"operationID": 290,
"opsThreatLevel": "Low",
"opsName": "OPERATION_SIN",
"opsStartDate": "2014-04-01T00:00:00",
"opsRefNumber": "10245678",
"opsEndDate": "2014-04-23T00:00:00",
"opsDescription": "\u003cp\u003eFake Operation\u003c/p\u003e",
"opsComments": "\u003cp\u003efake clues\u003c/p\u003e",
"dateCreated": "2014-04-02T00:00:00"
}
When the update request gets executed we get following exception
Exception in thread "main"
org.elasticsearch.ElasticsearchIllegalArgumentException: failed to execute
script
at
org.elasticsearch.action.update.UpdateHelper.prepare(UpdateHelper.java:153)
at
org.elasticsearch.action.update.UpdateHelper.prepare(UpdateHelper.java:80)
at
org.elasticsearch.action.update.TransportUpdateAction.shardOperation(TransportUpdateAction.java:189)
at
org.elasticsearch.action.update.TransportUpdateAction.shardOperation(TransportUpdateAction.java:185)
at
org.elasticsearch.action.update.TransportUpdateAction.shardOperation(TransportUpdateAction.java:64)
at
org.elasticsearch.action.support.single.instance.TransportInstanceSingleOperationAction$AsyncSingleAction$1.run(TransportInstanceSingleOperationAction.java:192)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: [Error: illegal unicode escape sequence]
[Near : {... Description": "\u003cp\u003eFake Operation\u003c/p }]
The unicode characters are not getting recognized. How to resolve this??
Regards,
Preeti
--
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
https://groups.google.com/d/msgid/elasticsearch/341a0af5-3df9-46bd-bd43-bb18aec8aafb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Error in bulk indexing - this IndexWriter is closed
Getting the same error with replica level set to 0. Regards, Preeti On Monday, March 24, 2014 2:33:52 PM UTC+5:30, Jörg Prante wrote: > Check if error still pertains with replica level 0. On single node, there > is not much sense in replica level 1. > > Jörg > > > On Mon, Mar 24, 2014 at 9:59 AM, Preeti Jain > > wrote: > >> ES version is 1.0.1. >> We have a single node cluster with shard and replica settings set to >> default values(5 and 1 respectively) >> >> Regards, >> Preeti >> >> >> On Monday, March 24, 2014 1:57:49 PM UTC+5:30, Jörg Prante wrote: >> >>> What ES version do you use? >>> How many nodes do you have in the cluster? >>> What is the replica level? >>> >>> You are not required to use replica level in bulk action, you can add >>> replica afterwards. >>> >>> Jörg >>> >>> >>> >>> On Mon, Mar 24, 2014 at 6:10 AM, Preeti Jain wrote: >>> >>>> Hi, >>>> >>>> We are indexing documents into elasticsearch from a java application. >>>> We are unable to index all the required docs as indexing fails for some >>>> of them due to following exception(found from log) >>>> >>>> org.elasticsearch.index.engine.CreateFailedEngineException: >>>> [investigations][0] Create failed for [Event#jEbSeiQASEemf6xTHSaUZw] >>>> at org.elasticsearch.index.engine.internal. >>>> InternalEngine.create(InternalEngine.java:397) >>>> at org.elasticsearch.index.shard.service.InternalIndexShard. >>>> create(InternalIndexShard.java:382) >>>> at org.elasticsearch.action.bulk.TransportShardBulkAction. >>>> shardIndexOperation(TransportShardBulkAction.java:401) >>>> at org.elasticsearch.action.bulk.TransportShardBulkAction. >>>> shardOperationOnPrimary(TransportShardBulkAction.java:153) >>>> at org.elasticsearch.action.support.replication. >>>> TransportShardReplicationOperationAction$AsyncShardOperationAction. >>>> performOnPrimary(TransportShardReplicationOperationAction.java:556) >>>> at org.elasticsearch.action.support.replication. >>>> TransportShardReplicationOperationAction$AsyncShardOperationAction$1. >>>> run(TransportShardReplicationOperationAction.java:426) >>>> at java.util.concurrent.ThreadPoolExecutor$Worker. >>>> runTask(ThreadPoolExecutor.java:886) >>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run( >>>> ThreadPoolExecutor.java:908) >>>> at java.lang.Thread.run(Thread.java:619) >>>> Caused by: org.apache.lucene.store.AlreadyClosedException: this >>>> IndexWriter is closed >>>> at org.apache.lucene.index.IndexWriter.ensureOpen( >>>> IndexWriter.java:645) >>>> at org.apache.lucene.index.IndexWriter.ensureOpen( >>>> IndexWriter.java:659) >>>> at org.apache.lucene.index.IndexWriter.updateDocument( >>>> IndexWriter.java:1525) >>>> at org.apache.lucene.index.IndexWriter.addDocument( >>>> IndexWriter.java:1199) >>>> at org.elasticsearch.index.engine.internal. >>>> InternalEngine.innerCreate(InternalEngine.java:462) >>>> at org.elasticsearch.index.engine.internal. >>>> InternalEngine.create(InternalEngine.java:384) >>>> >>>> What could be the issue? This happens even if the number of documents >>>> being indexed is as low as 28 and none of them is too big in size. >>>> >>>> Regards, >>>> Preeti >>>> >>>> -- >>>> 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 elasticsearc...@googlegroups.com. >>>> >>>> To view this discussion on the web visit https://groups.google.com/d/ >>>> msgid/elasticsearch/3276bee9-d94e-42a5-9df4-6c895f293dc7% >>>> 40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/3276bee9-d94e-42a5-9df4-6c895f293dc7%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> 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 elasticsearc...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/7b8b4691-e5b0-46d0-b660-54a110ffb14e%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/7b8b4691-e5b0-46d0-b660-54a110ffb14e%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 https://groups.google.com/d/msgid/elasticsearch/8c62bb94-2aad-4419-bfc8-4e05657ff2c6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Error in bulk indexing - this IndexWriter is closed
ES version is 1.0.1. We have a single node cluster with shard and replica settings set to default values(5 and 1 respectively) Regards, Preeti On Monday, March 24, 2014 1:57:49 PM UTC+5:30, Jörg Prante wrote: > > What ES version do you use? > How many nodes do you have in the cluster? > What is the replica level? > > You are not required to use replica level in bulk action, you can add > replica afterwards. > > Jörg > > > > On Mon, Mar 24, 2014 at 6:10 AM, Preeti Jain > > wrote: > >> Hi, >> >> We are indexing documents into elasticsearch from a java application. >> We are unable to index all the required docs as indexing fails for some >> of them due to following exception(found from log) >> >> org.elasticsearch.index.engine.CreateFailedEngineException: >> [investigations][0] Create failed for [Event#jEbSeiQASEemf6xTHSaUZw] >> at >> org.elasticsearch.index.engine.internal.InternalEngine.create(InternalEngine.java:397) >> at >> org.elasticsearch.index.shard.service.InternalIndexShard.create(InternalIndexShard.java:382) >> at >> org.elasticsearch.action.bulk.TransportShardBulkAction.shardIndexOperation(TransportShardBulkAction.java:401) >> at >> org.elasticsearch.action.bulk.TransportShardBulkAction.shardOperationOnPrimary(TransportShardBulkAction.java:153) >> at >> org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.performOnPrimary(TransportShardReplicationOperationAction.java:556) >> at >> org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$1.run(TransportShardReplicationOperationAction.java:426) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >> at java.lang.Thread.run(Thread.java:619) >> Caused by: org.apache.lucene.store.AlreadyClosedException: this >> IndexWriter is closed >> at >> org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:645) >> at >> org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:659) >> at >> org.apache.lucene.index.IndexWriter.updateDocument(IndexWriter.java:1525) >> at >> org.apache.lucene.index.IndexWriter.addDocument(IndexWriter.java:1199) >> at >> org.elasticsearch.index.engine.internal.InternalEngine.innerCreate(InternalEngine.java:462) >> at >> org.elasticsearch.index.engine.internal.InternalEngine.create(InternalEngine.java:384) >> >> What could be the issue? This happens even if the number of documents >> being indexed is as low as 28 and none of them is too big in size. >> >> Regards, >> Preeti >> >> -- >> 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 elasticsearc...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/3276bee9-d94e-42a5-9df4-6c895f293dc7%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/3276bee9-d94e-42a5-9df4-6c895f293dc7%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 https://groups.google.com/d/msgid/elasticsearch/7b8b4691-e5b0-46d0-b660-54a110ffb14e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Error in bulk indexing - this IndexWriter is closed
Hi, We are indexing documents into elasticsearch from a java application. We are unable to index all the required docs as indexing fails for some of them due to following exception(found from log) org.elasticsearch.index.engine.CreateFailedEngineException: [investigations][0] Create failed for [Event#jEbSeiQASEemf6xTHSaUZw] at org.elasticsearch.index.engine.internal.InternalEngine.create(InternalEngine.java:397) at org.elasticsearch.index.shard.service.InternalIndexShard.create(InternalIndexShard.java:382) at org.elasticsearch.action.bulk.TransportShardBulkAction.shardIndexOperation(TransportShardBulkAction.java:401) at org.elasticsearch.action.bulk.TransportShardBulkAction.shardOperationOnPrimary(TransportShardBulkAction.java:153) at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.performOnPrimary(TransportShardReplicationOperationAction.java:556) at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$1.run(TransportShardReplicationOperationAction.java:426) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:645) at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:659) at org.apache.lucene.index.IndexWriter.updateDocument(IndexWriter.java:1525) at org.apache.lucene.index.IndexWriter.addDocument(IndexWriter.java:1199) at org.elasticsearch.index.engine.internal.InternalEngine.innerCreate(InternalEngine.java:462) at org.elasticsearch.index.engine.internal.InternalEngine.create(InternalEngine.java:384) What could be the issue? This happens even if the number of documents being indexed is as low as 28 and none of them is too big in size. Regards, Preeti -- 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 https://groups.google.com/d/msgid/elasticsearch/3276bee9-d94e-42a5-9df4-6c895f293dc7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Error in Elasticsearch NullPointerException at org.elasticsearch.plugins.PluginsService.loadSitePlugins
Finally got this working. Our Java application that communicates with elasticsearch is hosted in JBoss server. While creating the transport client we were not passing elasticsearch home dir, plugin dir path explicitly. The default path that was picked up had some wrong reference. We managed to resolve the issue after passing the correct value to path.home. Regards, Preeti On Thursday, March 20, 2014 12:54:33 PM UTC+5:30, David Pilato wrote: > No. I have no idea. > I think something is wrong with your installation. > > Could you just > > download elasticsearch 1.0.1 (zip or tar.gz file) > unzip it > Run bin/plugin -install x (your plugin) > Run bin/elasticsearch > > Only those commands please. > > If it works, then something went wrong when you installed your > elasticsearch version. > Could you describe how you installed elasticsearch? > > -- > David ;-) > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > > Le 20 mars 2014 à 05:09, Preeti Jain > a > écrit : > > Hi David > > I have only one subdir inside plugins and it has following permissions > > drwxrwxrwx 2 root root 4096 Mar 11 10:06 analysis-phonetic > > Any more thoughts? > > Regards, > Preeti > On Wednesday, March 19, 2014 2:44:01 PM UTC+5:30, David Pilato wrote: >> >> I see. This fix has not been added in 1.0 branch but in 1.x: >> https://github.com/elasticsearch/elasticsearch/issues/5195 >> >> Could you check subdirs? >> I think you have an issue with your directories. >> >> >> -- >> *David Pilato* | *Technical Advocate* | *Elasticsearch.com >> <http://Elasticsearch.com>* >> @dadoonet <https://twitter.com/dadoonet> | >> @elasticsearchfr<https://twitter.com/elasticsearchfr> >> >> >> Le 19 mars 2014 à 10:03:55, Preeti Jain (itsp...@gmail.com) a écrit: >> >> Hi David, >> >> We are using version 1.0.1. We have following permission on plugins >> directory :rwxr-xr-x >> >> Regards, >> Preeti >> >> On Wednesday, March 19, 2014 2:23:47 PM UTC+5:30, David Pilato wrote: >>> >>> Which elasticsearch version are you using? >>> >>> This could happen if you don't have privileges on plugins dir. >>> Often, you have installed elasticsearch with a given account but you >>> installed plugin using sudo which ends up creating a plugin dir not >>> readable by elasticsearch user. >>> >>> This NPE has been fixed in recent version. Wondering if it was not >>> correctly fixed or if you are running an old version or if it's something >>> else. >>> >>> -- >>> *David Pilato* | *Technical Advocate* | *Elasticsearch.com >>> <http://Elasticsearch.com>* >>> @dadoonet <https://twitter.com/dadoonet> | >>> @elasticsearchfr<https://twitter.com/elasticsearchfr> >>> >>> >>> Le 19 mars 2014 à 09:44:58, Preeti Jain (itsp...@gmail.com) a écrit: >>> >>> Hi , >>> >>> We suddenly started getting this error in Elasticsearch log >>> >>> [2014-03-19 09:40:57,419][DEBUG][action.admin.cluster.node.info] >>> [North] failed to execute on node [B5a2wTMvQpGHOpO5oIjnug] >>> java.lang.NullPointerException >>> at >>> org.elasticsearch.plugins.PluginsService.loadSitePlugins(PluginsService.java:441) >>> at org.elasticsearch.plugins.PluginsService.info >>> (PluginsService.java:308) >>> at org.elasticsearch.node.service.NodeService.info >>> (NodeService.java:122) >>> at >>> org.elasticsearch.action.admin.cluster.node.info.TransportNodesInfoAction.nodeOperation(TransportNodesInfoAction.java:100) >>> at >>> org.elasticsearch.action.admin.cluster.node.info.TransportNodesInfoAction.nodeOperation(TransportNodesInfoAction.java:43) >>> at >>> org.elasticsearch.action.support.nodes.TransportNodesOperationAction$AsyncAction$2.run(TransportNodesOperationAction.java:146) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >>> at java.lang.Thread.run(Thread.java:619) >>> >>> We are unable to perform any action on elasticsearch. >>> >>> Any idea what could be the issue? >>> >>> Regards, >>> Preeti >>> -- >>> You received this message because you are subscri
Re: Error in Elasticsearch NullPointerException at org.elasticsearch.plugins.PluginsService.loadSitePlugins
Hi David I have only one subdir inside plugins and it has following permissions drwxrwxrwx 2 root root 4096 Mar 11 10:06 analysis-phonetic Any more thoughts? Regards, Preeti On Wednesday, March 19, 2014 2:44:01 PM UTC+5:30, David Pilato wrote: > > I see. This fix has not been added in 1.0 branch but in 1.x: > https://github.com/elasticsearch/elasticsearch/issues/5195 > > Could you check subdirs? > I think you have an issue with your directories. > > > -- > *David Pilato* | *Technical Advocate* | *Elasticsearch.com* > @dadoonet <https://twitter.com/dadoonet> | > @elasticsearchfr<https://twitter.com/elasticsearchfr> > > > Le 19 mars 2014 à 10:03:55, Preeti Jain (itsp...@gmail.com ) > a écrit: > > Hi David, > > We are using version 1.0.1. We have following permission on plugins > directory :rwxr-xr-x > > Regards, > Preeti > > On Wednesday, March 19, 2014 2:23:47 PM UTC+5:30, David Pilato wrote: >> >> Which elasticsearch version are you using? >> >> This could happen if you don't have privileges on plugins dir. >> Often, you have installed elasticsearch with a given account but you >> installed plugin using sudo which ends up creating a plugin dir not >> readable by elasticsearch user. >> >> This NPE has been fixed in recent version. Wondering if it was not >> correctly fixed or if you are running an old version or if it's something >> else. >> >> -- >> *David Pilato* | *Technical Advocate* | *Elasticsearch.com* >> @dadoonet <https://twitter.com/dadoonet> | >> @elasticsearchfr<https://twitter.com/elasticsearchfr> >> >> >> Le 19 mars 2014 à 09:44:58, Preeti Jain (itsp...@gmail.com) a écrit: >> >> Hi , >> >> We suddenly started getting this error in Elasticsearch log >> >> [2014-03-19 09:40:57,419][DEBUG][action.admin.cluster.node.info] >> [North] failed to execute on node [B5a2wTMvQpGHOpO5oIjnug] >> java.lang.NullPointerException >> at >> org.elasticsearch.plugins.PluginsService.loadSitePlugins(PluginsService.java:441) >> at org.elasticsearch.plugins.PluginsService.info >> (PluginsService.java:308) >> at org.elasticsearch.node.service.NodeService.info >> (NodeService.java:122) >> at >> org.elasticsearch.action.admin.cluster.node.info.TransportNodesInfoAction.nodeOperation(TransportNodesInfoAction.java:100) >> at >> org.elasticsearch.action.admin.cluster.node.info.TransportNodesInfoAction.nodeOperation(TransportNodesInfoAction.java:43) >> at >> org.elasticsearch.action.support.nodes.TransportNodesOperationAction$AsyncAction$2.run(TransportNodesOperationAction.java:146) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >> at java.lang.Thread.run(Thread.java:619) >> >> We are unable to perform any action on elasticsearch. >> >> Any idea what could be the issue? >> >> Regards, >> Preeti >> -- >> 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 elasticsearc...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/9134e001-f459-463f-82d4-930dc3769893%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/9134e001-f459-463f-82d4-930dc3769893%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> -- > 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 elasticsearc...@googlegroups.com . > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/90440ccf-66b5-4fc8-bbf0-c710d51fcf9f%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/90440ccf-66b5-4fc8-bbf0-c710d51fcf9f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- 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 https://groups.google.com/d/msgid/elasticsearch/6a01e302-edc6-483d-862d-5d2ffc2d40da%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Error in Elasticsearch NullPointerException at org.elasticsearch.plugins.PluginsService.loadSitePlugins
Also, this issue suddenly started coming up. We did installation yesterday, indexed some data and were able to search it until this morning. Regards, Preeti On Wednesday, March 19, 2014 2:23:47 PM UTC+5:30, David Pilato wrote: > > Which elasticsearch version are you using? > > This could happen if you don't have privileges on plugins dir. > > Often, you have installed elasticsearch with a given account but you > installed plugin using sudo which ends up creating a plugin dir not > readable by elasticsearch user. > > This NPE has been fixed in recent version. Wondering if it was not > correctly fixed or if you are running an old version or if it's something > else. > > -- > *David Pilato* | *Technical Advocate* | *Elasticsearch.com* > @dadoonet <https://twitter.com/dadoonet> | > @elasticsearchfr<https://twitter.com/elasticsearchfr> > > > Le 19 mars 2014 à 09:44:58, Preeti Jain (itsp...@gmail.com ) > a écrit: > > Hi , > > We suddenly started getting this error in Elasticsearch log > > [2014-03-19 09:40:57,419][DEBUG][action.admin.cluster.node.info] [North] > failed to execute on node [B5a2wTMvQpGHOpO5oIjnug] > java.lang.NullPointerException > at > org.elasticsearch.plugins.PluginsService.loadSitePlugins(PluginsService.java:441) > at org.elasticsearch.plugins.PluginsService.info > (PluginsService.java:308) > at org.elasticsearch.node.service.NodeService.info > (NodeService.java:122) > at > org.elasticsearch.action.admin.cluster.node.info.TransportNodesInfoAction.nodeOperation(TransportNodesInfoAction.java:100) > at > org.elasticsearch.action.admin.cluster.node.info.TransportNodesInfoAction.nodeOperation(TransportNodesInfoAction.java:43) > at > org.elasticsearch.action.support.nodes.TransportNodesOperationAction$AsyncAction$2.run(TransportNodesOperationAction.java:146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > > We are unable to perform any action on elasticsearch. > > Any idea what could be the issue? > > Regards, > Preeti > -- > 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 elasticsearc...@googlegroups.com . > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/9134e001-f459-463f-82d4-930dc3769893%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/9134e001-f459-463f-82d4-930dc3769893%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- 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 https://groups.google.com/d/msgid/elasticsearch/29beb3d3-2357-4e25-ac2f-954a2f933daf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Error in Elasticsearch NullPointerException at org.elasticsearch.plugins.PluginsService.loadSitePlugins
Hi David, We are using version 1.0.1. We have following permission on plugins directory :rwxr-xr-x Regards, Preeti On Wednesday, March 19, 2014 2:23:47 PM UTC+5:30, David Pilato wrote: > > Which elasticsearch version are you using? > > This could happen if you don't have privileges on plugins dir. > Often, you have installed elasticsearch with a given account but you > installed plugin using sudo which ends up creating a plugin dir not > readable by elasticsearch user. > > This NPE has been fixed in recent version. Wondering if it was not > correctly fixed or if you are running an old version or if it's something > else. > > -- > *David Pilato* | *Technical Advocate* | *Elasticsearch.com* > @dadoonet <https://twitter.com/dadoonet> | > @elasticsearchfr<https://twitter.com/elasticsearchfr> > > > Le 19 mars 2014 à 09:44:58, Preeti Jain (itsp...@gmail.com ) > a écrit: > > Hi , > > We suddenly started getting this error in Elasticsearch log > > [2014-03-19 09:40:57,419][DEBUG][action.admin.cluster.node.info] [North] > failed to execute on node [B5a2wTMvQpGHOpO5oIjnug] > java.lang.NullPointerException > at > org.elasticsearch.plugins.PluginsService.loadSitePlugins(PluginsService.java:441) > at org.elasticsearch.plugins.PluginsService.info > (PluginsService.java:308) > at org.elasticsearch.node.service.NodeService.info > (NodeService.java:122) > at > org.elasticsearch.action.admin.cluster.node.info.TransportNodesInfoAction.nodeOperation(TransportNodesInfoAction.java:100) > at > org.elasticsearch.action.admin.cluster.node.info.TransportNodesInfoAction.nodeOperation(TransportNodesInfoAction.java:43) > at > org.elasticsearch.action.support.nodes.TransportNodesOperationAction$AsyncAction$2.run(TransportNodesOperationAction.java:146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > > We are unable to perform any action on elasticsearch. > > Any idea what could be the issue? > > Regards, > Preeti > -- > 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 elasticsearc...@googlegroups.com . > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/9134e001-f459-463f-82d4-930dc3769893%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/9134e001-f459-463f-82d4-930dc3769893%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- 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 https://groups.google.com/d/msgid/elasticsearch/90440ccf-66b5-4fc8-bbf0-c710d51fcf9f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Error in Elasticsearch NullPointerException at org.elasticsearch.plugins.PluginsService.loadSitePlugins
Hi , We suddenly started getting this error in Elasticsearch log [2014-03-19 09:40:57,419][DEBUG][action.admin.cluster.node.info] [North] failed to execute on node [B5a2wTMvQpGHOpO5oIjnug] java.lang.NullPointerException at org.elasticsearch.plugins.PluginsService.loadSitePlugins(PluginsService.java:441) at org.elasticsearch.plugins.PluginsService.info(PluginsService.java:308) at org.elasticsearch.node.service.NodeService.info(NodeService.java:122) at org.elasticsearch.action.admin.cluster.node.info.TransportNodesInfoAction.nodeOperation(TransportNodesInfoAction.java:100) at org.elasticsearch.action.admin.cluster.node.info.TransportNodesInfoAction.nodeOperation(TransportNodesInfoAction.java:43) at org.elasticsearch.action.support.nodes.TransportNodesOperationAction$AsyncAction$2.run(TransportNodesOperationAction.java:146) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) We are unable to perform any action on elasticsearch. Any idea what could be the issue? Regards, Preeti -- 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 https://groups.google.com/d/msgid/elasticsearch/9134e001-f459-463f-82d4-930dc3769893%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Installing elasticsearch on red hat linux - error command not found
I downloaded it properly from the website. Regards, Preeti On Wednesday, March 12, 2014 12:45:40 AM UTC+5:30, Ivan Brusic wrote: > > How did you install Elasticsearch? Did you use a download [1] or some > other binary distribution such as RPM? > > If by chance, you simply cloned the Github repository, that is not the > correct way to install Elasticsearch. Use a downloadable version instead. > > [1] http://www.elasticsearch.org/download > > -- > Ivan > > > On Tue, Mar 11, 2014 at 6:30 AM, Preeti Jain > > wrote: > >> Hi all, >> >> I'm installing elasticsearch version 1.0.1 on red hat linux. >> I have placed elastic search in directory /opt so the path till bin looks >> like /opt/elasticsearch-1.0.1/bin >> when I'm trying to start elasticsearch as >> $ bin/elasticsearch -f >> I get error message elasticsearch: command not found >> Tried changing the permission on elasticsearch file, after that the error >> changed to bin/elasticsearch: line 116: syntax error: unexpected end of >> file >> I also tried using the service wrapper but facing the same issue >> >> JAVA_HOME and ES_HOME env variables are properly set >> >> could anyone help? >> >> -- >> 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 elasticsearc...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/b2291df5-c407-4e4a-ac61-a2aba7795dc4%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/b2291df5-c407-4e4a-ac61-a2aba7795dc4%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 https://groups.google.com/d/msgid/elasticsearch/15186ffd-f35e-41ed-ae2c-445c6efc3572%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Installing elasticsearch on red hat linux - error command not found
Hi all, I'm installing elasticsearch version 1.0.1 on red hat linux. I have placed elastic search in directory /opt so the path till bin looks like /opt/elasticsearch-1.0.1/bin when I'm trying to start elasticsearch as $ bin/elasticsearch -f I get error message elasticsearch: command not found Tried changing the permission on elasticsearch file, after that the error changed to bin/elasticsearch: line 116: syntax error: unexpected end of file I also tried using the service wrapper but facing the same issue JAVA_HOME and ES_HOME env variables are properly set could anyone help? -- 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 https://groups.google.com/d/msgid/elasticsearch/b2291df5-c407-4e4a-ac61-a2aba7795dc4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Highlighting doesn't work on numeric and date fields
Thanks for your response. I have to use numeric and date fields in range queries so the string field of mutli-field will not work. Any other thought? On Friday, February 21, 2014 6:44:09 PM UTC+5:30, Binh Ly wrote: > > You can do a multi-field on numeric fields with a string/not_analyzed > field and then highlight on that. > -- 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 https://groups.google.com/d/msgid/elasticsearch/349bc1ca-12bf-4f1c-a95f-785e0b245217%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Highlighting doesn't work on numeric and date fields
Hi All, We are using elasticsearch version .90.03. We observed that highlighting doesn't work on numeric and date fields. Has someone else faced the same issue? What is the solution to this problem. Thanks, Preeti -- 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 https://groups.google.com/d/msgid/elasticsearch/4d28d763-dde6-4440-a929-dca6a7541bd0%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
