date:20150202

If only each nodes(VMs) use its own sub dir, that's fine. Thanks.

On Tue, Feb 3, 2015 at 12:00 AM, David Pilato da...@pilato.fr wrote:

No each node will use its own subdir. This also applies to data nodes BTW.

--
*David Pilato* | *Technical Advocate* | *Elasticsearch.com
http://Elasticsearch.com*
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr
https://twitter.com/elasticsearchfr | @scrutmydocs
https://twitter.com/scrutmydocs

Le 2 févr. 2015 à 16:30, Daniel Woo daniel.y@gmail.com a écrit :

Using a transport client would be slightly slower due to the two-hops,
that's why I prefer a client node. I guess a pure client node just need
some cluster info in memory, I don't see a reason why client need to save
cluster info to disk.
Now I have a interesting question, if I start multiple client nodes
(multiple VMs with the same working directory), they will write to the same
temporary data directory, will the data directory be messed up?

On Monday, February 2, 2015 at 10:31:34 PM UTC+8, David Pilato wrote:

As it's a node, it's storing some cluster info in it.
You could use a Transport Client which will act as a pure Client without
joining the cluster.

--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 2 févr. 2015 à 15:08, Daniel Woo daniel...@gmail.com a écrit :

Hi guys, I start a client node with the parameter node.data turned off,
why is the data directory automatically created in my working directory?
Can I avoid creating the data directory since it's a pure client node?

--
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/37534520-ec4d-4076-b6c6-d6c65b2f9207%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/37534520-ec4d-4076-b6c6-d6c65b2f9207%40googlegroups.com?utm_medium=emailutm_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/74ad7956-564c-46dd-abaf-5cd7475eacb4%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/74ad7956-564c-46dd-abaf-5cd7475eacb4%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the
Google Groups elasticsearch group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/eLIw9LmhFhU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/A462087C-2E39-4949-A61D-8BFA46A46475%40pilato.fr
https://groups.google.com/d/msgid/elasticsearch/A462087C-2E39-4949-A61D-8BFA46A46475%40pilato.fr?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
Thanks Regards,
Daniel

--
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/CAF-kt2ur5MnpLdtrbzLJ13mhYM81hBvST0k02Nz%2BfgVUhWs2Ng%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Java client node creates data directory

Yes, I guess the extra hop is not a big deal compared to the disk IO ops on
the data node. I kind of prefer transport client now, the data directory
really drives me crazy :-)

On Tue, Feb 3, 2015 at 3:07 AM, joergpra...@gmail.com joergpra...@gmail.com
wrote:

Cluster state must be persisted, that is the reason why NodeClient needs
to write data to files.

It is a myth that TransportClient is slower because of two-hop. You will
not notice the difference in reality because the total time of an ES
operation takes usually longer than the extra hop. And, for the overhead of
managing cluster state, TransportClient does not need to care about that.

Jörg

On Mon, Feb 2, 2015 at 4:30 PM, Daniel Woo daniel.y@gmail.com wrote:

On Monday, February 2, 2015 at 10:31:34 PM UTC+8, David Pilato wrote:

As it's a node, it's storing some cluster info in it.
You could use a Transport Client which will act as a pure Client without
joining the cluster.

--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 2 févr. 2015 à 15:08, Daniel Woo daniel...@gmail.com a écrit :

Hi guys, I start a client node with the parameter node.data turned
off, why is the data directory automatically created in my working
directory? Can I avoid creating the data directory since it's a pure
client node?

--
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/37534520-ec4d-4076-b6c6-d6c65b2f9207%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/37534520-ec4d-4076-b6c6-d6c65b2f9207%40googlegroups.com?utm_medium=emailutm_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/74ad7956-564c-46dd-abaf-5cd7475eacb4%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/74ad7956-564c-46dd-abaf-5cd7475eacb4%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the
Google Groups elasticsearch group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/eLIw9LmhFhU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGFWS6rWFxbq_zwUh%3DZDtbapQgsqaFZ7Tt6F%2BiiJTqR9g%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGFWS6rWFxbq_zwUh%3DZDtbapQgsqaFZ7Tt6F%2BiiJTqR9g%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
Thanks Regards,
Daniel

--
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/CAF-kt2vpUjqAm%3DWPShbOfRhWU3qjbEUpA04c5O3cP-z51su5fg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Kibana4 Beta3: Battling with wildcard search on not_analyzed fields

2015-02-02 Thread Ali Kheyrollahi

This *works* (exact value)

{term:{CounterName:\\Windows Azure Caching:Client(w3wp_5412)\\Failure 
Exceptions}}


But NOT this:
{term:{CounterName:Caching}}
Nor
{term:{CounterName:\\Windows Azure Caching:Client(w3wp_.*)\\Failure 
Exceptions}}
Or this
{term:{CounterName:\\Windows Azure Caching:Client(w3wp_*)\\Failure 
Exceptions}}

And *not even* this
{regexp:{CounterName:\\Windows Azure Caching:Client(w3wp_.*)\\Failure 
Exceptions}}
or
{regexp:{CounterName:\\Windows Azure Caching:Client(w3wp_.+)\\Failure 
Exceptions}}
or
{regexp:{CounterName:\\Windows Azure Caching:Client(w3wp_*)\\Failure 
Exceptions}}

-- 
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/327ba38a-9caf-41c1-8a45-f93be1532bf2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Kibana4 Beta3: Battling with wildcard search on not_analyzed fields

2015-02-02 Thread Ali Kheyrollahi

Any help please??

On Saturday, 31 January 2015 09:56:38 UTC, Ali Kheyrollahi wrote:

 Hi,

 I really haven't found a consistent way to use query window in Discover or 
 Visualize tabs. My results become hit and miss and inconsistent.

 So I am searching for types of my_type  and I have a field called 
 CounterName and I am looking for \Windows Azure 
 Caching:Client(w3wp_2392)\Total Local Cache Hits

 Funny thing is searching for verbatim value does not work:
 CounterName\Windows Azure Caching:Client(w3wp_2392)\Total Local Cache 
 Hits
 And I have to escape only backslashes (well I am using double quotes so it 
 is literal, no?) and not brackets or colon:
 CounterName\\Windows Azure Caching:Client(w3wp_2392)\\Total Local Cache 
 Hits

 Now, the 2392 number here is variable (pid on the box) so I am trying to 
 look for \Windows Azure Caching:Client(w3wp_*)\Total Local Cache Hits and 
 I have tried all these to no avail:

 CounterName:\\Windows Azure Caching:Client(w3wp_*)\\Total Local Cache 
 Hits
 CounterName:\\Windows Azure Caching:Client(w3wp_\*)\\Total Local Cache 
 Hits
 CounterName:\Windows Azure Caching:Client(w3wp_*\Total Local Cache 
 Hits (nothing comes back)

 And also tried regex:

 CounterName:/\Windows Azure Caching:Client(w3wp_*)\\Total Local Cache Hits/
 CounterName:/\Windows Azure Caching:Client(w3wp_.*)\\Total Local Cache 
 Hits/
 ...

 With many different combinations of replacing reserved chars with ?. 

 What am I doing wrong?

 Thanks





-- 
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/54e8264f-00ee-4327-b4fc-ae074152669e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: elasticsearch-hadoop for spark, index documents from a RDD in different index by day: myindex-2014-01-01 for example

2015-02-02 Thread Abhishek Patel

Hi Julien,

I am trying to achieve something similar. In my case, my JSON contains a
field time in Unix time. And i want to partition my indexes by this
field. That is, if one JSON1 contains 1422904680 in time and JSON2
contains 1422991080 in time, then i want to create indexes which are
partitioned by time (24 hours) like

index_1422835200_1422921599 - which will contain JSON1 because value of
time = 1422904680 falls in its range.
index_1422921600_1423007999 - which will contain JSON2 because value of
time = 1422991080 falls in its range.

Now I want to create my indexes dynamically. There is also possibility of
receiving a JSON which contain a value of time before current date.

To achieve this, I need to create index name dynamically by calculating it
at the time of creation then and there itself. Programmatically, I want to
achieve something like this

JavaEsSpark.saveJsonToEs(jrd, index_{time} - {time} % 86400}_{ {time} +
86400 - {date} % 86400 }/type);

Is it possible to achieve dynamic index name creation as described above?
If no, is there any work around to achieve my use case.

Thanks
Abhishek

--
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/2326fa57-63d9-4b9c-8b71-b1c8b2b0e061%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ES default - async or sync

2015-02-02 Thread 'Cindy' via elasticsearch

Hi Clinton,

Is using async NOT recommonded? The Definitive Guild says, This option is
mentioned specifically to *advise against using it*. The default sync
replication
allows Elasticsearch to exert back pressure on whatever system is feeding
it with data. With async replication, it is possible to *overload
Elasticsearch* by sending too many requests without waiting for their
completion.

Also, if the indexes has *not* being updated in the replica, could the
query only be sent to the replica and elasticsearch return not found?

On Sunday, 7 September 2014 04:31:30 UTC-4, Clinton Gormley wrote:

Hiya

OK I see where the confusion is coming in. I used the word asynchronously
in slightly different contexts there. I will try to reword in the
Definitive Guide.

Replication is sync by default, in other words: the primary waits for
indexing to happen on the replica before it returns to the user. That
said, lots of these processes happen at the same time, so sending the
document to the replica is asynchronous. It doesn't send a change then
wait for the response before sending the next one. This all happens in
parallel.

Does that make it clearer?

On 7 September 2014 03:38, daa qqu daa...@gmail.com javascript: wrote:

What is the default replication policy in Elasticsearch? Does it push
changes to replicas asynchronously or synchronously? Or does it use
different mode with different operations.
asynchronous replication
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/docs-index_.html#index-replication

By default, the index operation only returns after all shards within the
replication group have indexed the document (sync replication).
optimistic concurrency control
http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/optimistic-concurrency-control.html#optimistic-concurrency-control
Elasticsearch is distributed. When documents are created, updated or
deleted, the new version of the document has to be replicated to other
nodes in the cluster. Elasticsearch is also asynchronous and concurrent

This book Ealsticsearch Definitive Guide, states under 'Creating,
indexing and deleting' that ...default value for replication is
synchronous. When discussing 'update' API it is stated that ...these
changes are forwarded to the replica shards asynchronously

https://github.com/elasticsearch/elasticsearch-definitive-guide/blob/master/040_Distributed_CRUD/15_Create_index_delete.asciidoc
replication

*** The default value for replication is sync. This causes the primary
shard to wait for successful responses from the replica shards before
returning.

https://github.com/elasticsearch/elasticsearch-definitive-guide/blob/master/040_Distributed_CRUD/25_Partial_updates.asciidoc

Document based replication

When a primary shard forwards changes to its replica shards, it doesn’t
forward the update request. Instead it forwards the new version of the full
document. ***Remember that these changes are forwarded to the replica
shards asynchronously and there is no guarantee that they will arrive in
the same order that they were sent.

https://groups.google.com/d/msgid/elasticsearch/CAO4Z2jCOfD8Mp8YL9WbPmf9aODX4D6fORZ-pSjhxFx1qweQsXA%40mail.gmail.com?utm_medium=emailutm_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/890150aa-3ccd-48f1-8cc0-8115f756fcb6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Elastic Search API : heavy coupling design

This should work AFAIK.

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr
https://twitter.com/elasticsearchfr | @scrutmydocs
https://twitter.com/scrutmydocs

Le 2 févr. 2015 à 10:04, Amaury Fages afages...@gmail.com a écrit :

I have more information :
Version A is 1.1.2 as said before and target of B is 1.4 or 1.5.

Can you confirm the compatibility ?

2015-01-30 17:32 GMT+01:00 Amaury Fages afages...@gmail.com
mailto:afages...@gmail.com:
Thank you for answering.

Version A is 1.1.2 and B should be above soon or late. The integration team
had a problem with A already upgrading the server but if from the 1.0 there
should not be any dependency problem, I should maybe dig the problems they
had exactly.

2015-01-30 17:18 GMT+01:00 David Pilato da...@pilato.fr
mailto:da...@pilato.fr:
What is your version A?
And version B?

Asking that because having different elasticsearch versions should work
starting elasticsearch 1.0.
This does not apply to Java versions that need to be consistent.

--
David Pilato | Technical Advocate | Elasticsearch.com
http://elasticsearch.com/
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr
https://twitter.com/elasticsearchfr | @scrutmydocs
https://twitter.com/scrutmydocs

Le 30 janv. 2015 à 15:42, Amaury Fages afages...@gmail.com
mailto:afages...@gmail.com a écrit :

Hello everyone,

My customer is currently facing a versioning problem. We have an application
'A' that depends (Maven) of ElasticSearch API, which communicates by
TransportClient with centralized ElasticSearch Server 'B'.

The problem is : when we upgrades 'B', we need to upgrade the Maven
dependency in application 'A', which is not a desired coupling design in the
long term. I guess this is a common problem for many companies that you
should be aware of already.

I saw some topics that said ES promised to leverage this design by avoiding
being version dependant in a future API version. Right now, we are aiming
either to :

1) Wait for a solution from ES (in a reasonable time)
2) Migrate completely to a full REST architecture bypassing the API

I hope you can address the 1) before thinking about the 2). What can you say
about this problem and how could/would you solution it ?

Best regards,

Amaury FAGES.

--
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
mailto:elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/b2e13fe4-1da4-4a76-8b03-4c0e553cd887%40googlegroups.com

https://groups.google.com/d/msgid/elasticsearch/b2e13fe4-1da4-4a76-8b03-4c0e553cd887%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout
https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google
Groups elasticsearch group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/hiOsFiPaZnY/unsubscribe
https://groups.google.com/d/topic/elasticsearch/hiOsFiPaZnY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscr...@googlegroups.com
mailto:elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/764D4229-6F7B-4435-92F3-3930F02601D9%40pilato.fr

https://groups.google.com/d/msgid/elasticsearch/764D4229-6F7B-4435-92F3-3930F02601D9%40pilato.fr?utm_medium=emailutm_source=footer.

For more options, visit https://groups.google.com/d/optout
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
mailto:elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAL2m5Fdf7h6aS5wuadXk_4epoK4yVSqB3107iY7oj6b49tkpJA%40mail.gmail.com

https://groups.google.com/d/msgid/elasticsearch/CAL2m5Fdf7h6aS5wuadXk_4epoK4yVSqB3107iY7oj6b49tkpJA%40mail.gmail.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout
https://groups.google.com/d/optout.

Re: Kibana4 Beta3: Battling with wildcard search on not_analyzed fields

2015-02-02 Thread Itamar Syn-Hershko

It looks like your field is analyzed and you are trying to query it
assuming its not_analyzed (e.g. one string). Hard to say without seeing
your index mapping.

Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer Consultant
Lucene.NET committer and PMC member

On Mon, Feb 2, 2015 at 3:08 PM, Ali Kheyrollahi alios...@gmail.com wrote:

Any help please??

On Saturday, 31 January 2015 09:56:38 UTC, Ali Kheyrollahi wrote:

Hi,

I really haven't found a consistent way to use query window in Discover
or Visualize tabs. My results become hit and miss and inconsistent.

So I am searching for types of my_type and I have a field called
CounterName and I am looking for \Windows Azure
Caching:Client(w3wp_2392)\Total Local Cache Hits

Funny thing is searching for verbatim value does not work:
CounterName\Windows Azure Caching:Client(w3wp_2392)\Total Local Cache
Hits
And I have to escape only backslashes (well I am using double quotes so
it is literal, no?) and not brackets or colon:
CounterName\\Windows Azure Caching:Client(w3wp_2392)\\Total Local Cache
Hits

Now, the 2392 number here is variable (pid on the box) so I am trying to
look for \Windows Azure Caching:Client(w3wp_*)\Total Local Cache Hits and
I have tried all these to no avail:

CounterName:\\Windows Azure Caching:Client(w3wp_*)\\Total Local Cache
Hits
CounterName:\\Windows Azure Caching:Client(w3wp_\*)\\Total Local Cache
Hits
CounterName:\Windows Azure Caching:Client(w3wp_*\Total Local Cache
Hits (nothing comes back)

And also tried regex:

CounterName:/\Windows Azure Caching:Client(w3wp_*)\\Total Local Cache
Hits/
CounterName:/\Windows Azure Caching:Client(w3wp_.*)\\Total Local Cache
Hits/
...

With many different combinations of replacing reserved chars with ?.

What am I doing wrong?

Thanks

--
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/54e8264f-00ee-4327-b4fc-ae074152669e%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/54e8264f-00ee-4327-b4fc-ae074152669e%40googlegroups.com?utm_medium=emailutm_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/CAHTr4Ztkn6wx%2BJB8iJVyLwmZTbX30SKuFkZOvZ38E-96guj7eQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Java client node creates data directory

Hi guys, I start a client node with the parameter node.data turned off, 
why is the data directory automatically created in my working directory? 
Can I avoid creating the data directory since it's a pure client node?

-- 
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/37534520-ec4d-4076-b6c6-d6c65b2f9207%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Elastic search with CouchDB river plugin - Can't find any documents

David,

Sorry for the old post revival, but I'm getting this same error with no 
hits with Couchdb rivers (2.4.1), Elasticsearch (1.4.2), and Couchdb 
(1.6.1).  I am fairly new to using couch-rivers but I've installed all the 
applications and they are running on Centos 7.  Can you please see if you 
notice anything wrong?  I've looked everywhere but can not find a solution. 
 Thank you in advance


I added some dummy data into my couchdb database testdb:
# curl -XGET localhost:5984/testdb/_changes
{results:[
{seq:1,id:1,changes:[{rev:1-0291.}]},
{seq:2,id:2,changes:[{rev:1-1945.}]},
{seq:3,id:3,changes:[{rev:1-62a5.}]},
{seq:4,id:4,changes:[{rev:1-7e93.}]},
],
last_seq:4}


I run this to make the index:
# curl -X PUT 'http://localhost:9200/_river/testdb/_meta' -d '{ type : 
couchdb, couchdb : { host : localhost, port : 5984, db : 
testdb, filter : null }'

Get a return of:
# 
{index:_river,_type:testdb,_id:_meta,_version:1,created:true}

When I try to do the query:
# curl localhost:9200/testdb/testdb/_search?pretty=1
{
  took : 1,
  timed_out : false,
  _shards : {
total : 5,
successful : 5,
failed : 0
  },
  hits : {
total : 0,
max_score : null,
hits : [ ]
  }
}



When I use the 
# curl http://localhost:9200/_search?q=*pretty=true
{
  took : 2,
  timed_out : false,
  _shards : {
total : 16,
successful : 16,
failed : 0
  },
  hits : {
total : 1,
max_score : 1.0,
hits : [ {
  _index : _river,
  _type : testdb,
  _id : _meta,
  _score : 1.0,
  _source : {type couchdb, couchdb : {host : localhost, 
port: 5984, db : testdb, filter : null}}
  } ]
  }
}





On Wednesday, June 5, 2013 at 1:59:04 AM UTC-4, David Pilato wrote:

 Just to double check, could you run:
 http://localhost:9200/_search?q=*pretty=true 
 http://localhost:9200/my_db/_search?q=*pretty=true

 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs


 Le 5 juin 2013 à 00:19, Yannis Psarras yannis@gmail.com javascript: 
 a écrit :

 And with the q=* I get the same really as above

 (for query: http://localhost:9200/my_db/_search?q=*pretty=true)


 On Wed, Jun 5, 2013 at 1:17 AM, Yannis Psarras yannis@gmail.com 
 javascript: wrote:

 I get the following:

 curl -XGET http://localhost:9200/my_db/_search?pretty=true 
 http://localhost:9200/my_db/my_db/_search?pretty=true
 {
   took : 2,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }



 On Wed, Jun 5, 2013 at 12:53 AM, David Pilato da...@pilato.fr 
 javascript: wrote:

 Not sure that default type is dbname.
 What do you get with:

 curl -XGET http://localhost:9200/my_db/_search?q=*pretty=true;

 ?

 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs


 Le 4 juin 2013 à 23:26, Yannis Psarras yannis@gmail.com 
 javascript: a écrit :

 I recently started using elastic search and couchdb and I have the 
 following problem. I have a couch database with a bunch of documents. I add 
 a couch db river index on elastic search and I expect to have those 
 documents indexed and searchable. But when I search for anything through ES 
 I dont get any results. The command flow is as follows:

 The command above verifies that there are 4 documents in the couch db 
 instance

 curl -H Content-Type: application/json -X GET http://localhost:5984/my_db

 {db_name:my_db,doc_count:4,doc_del_count:0,update_seq:4,purge_seq:0,compact_running:false,disk_size:16482,data_size:646,instance_start_time:1370204643908592,disk_format_version:6,committed_update_seq:4}

 The _changes output:

 curl -H Content-Type: application/json -X GET 
 http://localhost:5984/my_db/_changes
 {results:[
 {seq:1,id:1,changes:[{rev:1-40d928a959dd52d183ab7c413fabca92}]},
 {seq:2,id:2,changes:[{rev:1-42212757a56b240f5205266b1969e890}]},
 {seq:3,id:3,changes:[{rev:1-f59c2ae7acacb68d9414be05d56ed33a}]},
 {seq:4,id:4,changes:[{rev:1-e86cf1c287c16906e81d901365b9bf98}]}
 ],
 last_seq:4}

 Now, below I m creating my index in ES.

 curl -XPUT 'http://localhost:9200/_river/my_db/_meta' -d '{ type : 
 couchdb, couchdb : { host : localhost, port : 5984, db : 
 my_db, filter : null } }'

 {ok:true,_index:_river,_type:my_db,_id:_meta,_version:1}

 But I dont get anything back.

 curl -XGET http://localhost:9200/my_db/my_db/_search?pretty=true;
 {
   took : 2,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }

 Is there anything I m missing?

 Thanks, Yannis

 -- 
 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 javascript:.

 For more options, visit https://groups.google.com/groups/opt_out.
  
  
  
 -- 
 You received this

Re: Elastic search with CouchDB river plugin - Can't find any documents

Try with:

localhost:9200/testdb/_search

I think you are using the default type name here which is not IIRC the river 
name.

HTH
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

 Le 2 févr. 2015 à 11:43, Bao-Quan Ho ho.baoq...@gmail.com a écrit :
 
 David,
 
 Sorry for the old post revival, but I'm getting this same error with no hits 
 with Couchdb rivers (2.4.1), Elasticsearch (1.4.2), and Couchdb (1.6.1).  I 
 am fairly new to using couch-rivers but I've installed all the applications 
 and they are running on Centos 7.  Can you please see if you notice anything 
 wrong?  I've looked everywhere but can not find a solution.  Thank you in 
 advance
 
 
 I added some dummy data into my couchdb database testdb:
 # curl -XGET localhost:5984/testdb/_changes
 {results:[
 {seq:1,id:1,changes:[{rev:1-0291.}]},
 {seq:2,id:2,changes:[{rev:1-1945.}]},
 {seq:3,id:3,changes:[{rev:1-62a5.}]},
 {seq:4,id:4,changes:[{rev:1-7e93.}]},
 ],
 last_seq:4}
 
 
 I run this to make the index:
 # curl -X PUT 'http://localhost:9200/_river/testdb/_meta' -d '{ type : 
 couchdb, couchdb : { host : localhost, port : 5984, db : 
 testdb, filter : null }'
 
 Get a return of:
 # 
 {index:_river,_type:testdb,_id:_meta,_version:1,created:true}
 
 When I try to do the query:
 # curl localhost:9200/testdb/testdb/_search?pretty=1
 {
   took : 1,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }
 
 
 
 When I use the 
 # curl http://localhost:9200/_search?q=*pretty=true
 {
   took : 2,
   timed_out : false,
   _shards : {
 total : 16,
 successful : 16,
 failed : 0
   },
   hits : {
 total : 1,
 max_score : 1.0,
 hits : [ {
   _index : _river,
   _type : testdb,
   _id : _meta,
   _score : 1.0,
   _source : {type couchdb, couchdb : {host : localhost, 
 port: 5984, db : testdb, filter : null}}
   } ]
   }
 }
 
 
 
 
 
 On Wednesday, June 5, 2013 at 1:59:04 AM UTC-4, David Pilato wrote:
 Just to double check, could you run:
 http://localhost:9200/_search?q=*pretty=true
 
 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
 
 
 Le 5 juin 2013 à 00:19, Yannis Psarras yannis@gmail.com a écrit :
 
 And with the q=* I get the same really as above
 
 (for query: http://localhost:9200/my_db/_search?q=*pretty=true)
 
 
 On Wed, Jun 5, 2013 at 1:17 AM, Yannis Psarras yannis@gmail.com wrote:
 I get the following:
 
 curl -XGET http://localhost:9200/my_db/_search?pretty=true;
 {
   took : 2,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }
 
 
 On Wed, Jun 5, 2013 at 12:53 AM, David Pilato da...@pilato.fr wrote:
 Not sure that default type is dbname.
 What do you get with:
 curl -XGET http://localhost:9200/my_db/_search?q=*pretty=true;
 ?
 
 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
 
 
 Le 4 juin 2013 à 23:26, Yannis Psarras yannis@gmail.com a écrit :
 
 I recently started using elastic search and couchdb and I have the 
 following problem. I have a couch database with a bunch of documents. I 
 add a couch db river index on elastic search and I expect to have those 
 documents indexed and searchable. But when I search for anything through 
 ES I dont get any results. The command flow is as follows:
 
 The command above verifies that there are 4 documents in the couch db 
 instance
 
 curl -H Content-Type: application/json -X GET http://localhost:5984/my_db
 
 {db_name:my_db,doc_count:4,doc_del_count:0,update_seq:4,purge_seq:0,compact_running:false,disk_size:16482,data_size:646,instance_start_time:1370204643908592,disk_format_version:6,committed_update_seq:4}
 The _changes output:
 
 curl -H Content-Type: application/json -X GET 
 http://localhost:5984/my_db/_changes
 {results:[
 {seq:1,id:1,changes:[{rev:1-40d928a959dd52d183ab7c413fabca92}]},
 {seq:2,id:2,changes:[{rev:1-42212757a56b240f5205266b1969e890}]},
 {seq:3,id:3,changes:[{rev:1-f59c2ae7acacb68d9414be05d56ed33a}]},
 {seq:4,id:4,changes:[{rev:1-e86cf1c287c16906e81d901365b9bf98}]}
 ],
 last_seq:4}
 Now, below I m creating my index in ES.
 
 curl -XPUT 'http://localhost:9200/_river/my_db/_meta' -d '{ type : 
 couchdb, couchdb : { host : localhost, port : 5984, db : 
 my_db, filter : null } }'
 
 {ok:true,_index:_river,_type:my_db,_id:_meta,_version:1}
 But I dont get anything back.
 
 curl -XGET http://localhost:9200/my_db/my_db/_search?pretty=true;
 {
   took : 2,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }
 Is there anything I m missing?
 
 Thanks, Yannis
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 elasticsearch group.
 To unsubscribe from this group and

Re: Field data removed after deleting index

2015-02-02 Thread Mark Walkom

I am sure you can test it to confirm :)

On 2 February 2015 at 19:17, Ernesto Reig erniru...@gmail.com wrote:

It should but.. is it?

On Sunday, February 1, 2015 at 10:16:17 PM UTC+1, Mark Walkom wrote:

Yes, it should be.

On 30 January 2015 at 21:35, Ernesto Reig erni...@gmail.com wrote:

Any comments on this?

On Thursday, January 29, 2015 at 5:06:12 PM UTC+1, Ernesto Reig wrote:

Hi all,
This might sound a dumb question but just in case: Is the fielddata
belonging to a given index evicted when that index is removed?

Thnks

--
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/a53d21f9-bf45-47df-add1-3e3366c0385f%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/a53d21f9-bf45-47df-add1-3e3366c0385f%40googlegroups.com?utm_medium=emailutm_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/eade1151-5618-4fcf-8f68-3163b97103ce%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/eade1151-5618-4fcf-8f68-3163b97103ce%40googlegroups.com?utm_medium=emailutm_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/CAEYi1X-6wUWVZqm9Ta2v1t6jmebKwc3ysQcv7hiMo-9RzGhOoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: ES 1.4.2 - MasterNotDiscovered Exception with Java Node Client

2015-02-02 Thread Stefan Meiwald

I have found out, that it works when I use a Transport Client. Does this
give any hint what is wrong with the Node Client Configuration? Both
clients are using the elasticsearch binary protocol and port 9300 right?

Am Samstag, 31. Januar 2015 20:26:25 UTC+1 schrieb Stefan Meiwald:

I am trying to connect with a Java application from localhost to my
elasticsearch cluster on a root server. My problem is that the java client
is not able to get a connection.

Ports 9200-9299 and 9300-9400 are opened on the root server(groupelite.de
).

I configured my elasticsearch cluster to use unicast discovery and set its
inet ip address as network.host.
This is how I instantiate my client:

NodeBuilder.nodeBuilder()
.clusterName(neeedo-es)
.settings(ImmutableSettings.settingsBuilder()
.classLoader(classOf[Settings].getClassLoader)
.put(discovery.zen.ping.unicast.hosts, groupelite.de:9300)
.put(node.name, neeedo-client))
.client(true)
.data(false)
.node()

And this is my elasticsearch.yml
https://gist.github.com/MeiSign/ccfdcc62643c1185bab3

The firewall on the server should be turned off. You can also reach es
with http:
http://www.groupelite.de:9200/

The server is running ubuntu 14.04. Elasticsearch version is 1.4.2 on
client and server.

Iam not very used to networking stuff but I hope to get some ideas from
you guys what is wrong.

--
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/d5681c2c-6a34-437b-b9ac-c0074435c64a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Search in_order with Fuzziness

2015-02-02 Thread Pulkit Agrawal

Is it something not feasible with ElasticSearch ?

On Sun, Feb 1, 2015 at 10:44 AM, Pulkit Agrawal pulkitdot...@gmail.com
wrote:

 Hi All,

 I want to search tokens in_order with fuzziness in terms. What should be
 the query for it?

 Thanks!


-- 
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/CAMVa6uqK6FoM_m%2Bg8%2B2GV%3D7dOsetje5wi6F90E4zz-yV6iVcsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: term filter on field mapped to integer fails - a bug?

2015-02-02 Thread msbreuer

The affected integer fields take no effect for sorting. It looks like 
store only, the result document contains values. But the field itself is 
not searchable.

When creating index with mapping to long al lis fine. Does any one have 
an idea? 

-- 
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/7096839c-2baa-42e9-91da-b47c634f2c7a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ElasticSearch Acknowledgements

2015-02-02 Thread Abhishek Patel

Previously, I was using storm topology to build my pipeline to suffice my 
use case which was - Reading from Kafka topic through Kafka spout, process 
these tuples in Bolt, then emit them to ElasticSearch bolt to index my 
tuples. In storm topology, I was able to acknowledge each tuple i was 
indexing and these  acknowledgments were sent from EsBolt to spout and 
finally to Zookeeper.

Later I realised that Storm is not the appropriate component for my use 
case and I switched to Spark. I am doing the same thing with Spark - 
Reading from Kafka topic, reading messages in Spark stream, pass this 
stream to a component which converts this stream to RDD and finally indexes 
these RDDs. But now, there is no mechanism for acknowledgements. But I 
still want to send acknowledgements for each messages being indexed to the 
previous component.

My code looks like this - 

JavaEsSpark.saveJsonToEs(jrd, index_{date}/type);

How can I get acknowledgements in Spark-ElasticSearch framework? 

-- 
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/f73a57fd-1f5a-41f3-b6ec-077961668687%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: elasticsearch-hadoop for spark, index documents from a RDD in different index by day: myindex-2014-01-01 for example

2015-02-02 Thread Abhishek Patel

Hi Julien

Yes. Probably that's the only possible work around to do this. What I am 
planning to do is, calculate the name of index prior to writing and add a 
field named indexname in my JSON and then I will use 

  JavaEsSpark.saveJsonToEs(jrd, index_{indexname}/type);

 Thanks for the reply.



Abhishek

-- 
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/7d41dbce-964c-4c71-94cf-d4dcf0e902b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Java client node creates data directory

On Monday, February 2, 2015 at 10:31:34 PM UTC+8, David Pilato wrote:

As it's a node, it's storing some cluster info in it.
You could use a Transport Client which will act as a pure Client without
joining the cluster.

--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 2 févr. 2015 à 15:08, Daniel Woo daniel...@gmail.com javascript: a
écrit :

https://groups.google.com/d/msgid/elasticsearch/37534520-ec4d-4076-b6c6-d6c65b2f9207%40googlegroups.com?utm_medium=emailutm_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/74ad7956-564c-46dd-abaf-5cd7475eacb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: elasticsearch-hadoop for spark, index documents from a RDD in different index by day: myindex-2014-01-01 for example

2015-02-02 Thread Julien Naour

Hi Abhishek,

I'll probably do a previous step to process the day by line (like
-MM-dd).
And just do
JavaEsSpark.saveJsonToEs(jrd, index_{date}/type);

If the range is needed I'll probably do the same. Add a feature with {time}
- {time} % 86400}_{ {time} + 86400 - {date} % 86400 } and just
index_{my_new_feature}

It adds a step and a feature in the doc but it's simple to do.

Julien

2015-02-02 15:13 GMT+01:00 Abhishek Patel present.boiling2...@gmail.com:

Hi Julien,

Now I want to create my indexes dynamically. There is also possibility of
receiving a JSON which contain a value of time before current date.

To achieve this, I need to create index name dynamically by calculating it
at the time of creation then and there itself. Programmatically, I want to
achieve something like this

JavaEsSpark.saveJsonToEs(jrd, index_{time} - {time} % 86400}_{ {time} +
86400 - {date} % 86400 }/type);

Is it possible to achieve dynamic index name creation as described above?
If no, is there any work around to achieve my use case.

Thanks
Abhishek

--
You received this message because you are subscribed to a topic in the
Google Groups elasticsearch group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/5-LwjQxVlhk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/2326fa57-63d9-4b9c-8b71-b1c8b2b0e061%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/2326fa57-63d9-4b9c-8b71-b1c8b2b0e061%40googlegroups.com?utm_medium=emailutm_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/CAFGA2c3fFGtSpTtpR9tD%2BsfwjuRDftHTK7y2QUHUYEhH5iwkWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Java client node creates data directory

As it's a node, it's storing some cluster info in it.
You could use a Transport Client which will act as a pure Client without 
joining the cluster.

--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

 Le 2 févr. 2015 à 15:08, Daniel Woo daniel.y@gmail.com a écrit :
 
 Hi guys, I start a client node with the parameter node.data turned off, why 
 is the data directory automatically created in my working directory? Can I 
 avoid creating the data directory since it's a pure client node?
 -- 
 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/37534520-ec4d-4076-b6c6-d6c65b2f9207%40googlegroups.com.
 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/D913D5D6-DDF9-4B43-B501-F63EC18F7700%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Obtain jdbc river state via java api

2015-02-02 Thread Abid Hussain

Hi all,

is there a way to obtain state of a certain river (like *GET 
/_river/jdbc/river-name/_state*) via TransportClient or any other kind of 
java api call?

If not, I would have to perform a http get request programmatically and 
parse json result, I guess...

Regards,

Abid

-- 
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/eda0c348-4938-4900-a822-37aa520da7fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Segments marked as deleted?

2015-02-02 Thread Jason Zhang

Hi,

  I use segmentspy to detect segment merges in ES. But I find there's 
several Deleted Docs which is like Deleted Docs: 1.55630.
  I know ES will mark items as deleted and remove them later through GC.

  But what's the meaning of those deleted segments? Why does ES/lucene not 
remove them? There's no updates in this index since 10 days ago.
  How can I clean them out explicitly?

  Thank you.

-- 
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/8f0458a6-53ee-4e38-a3cc-6564eb693040%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Segments marked as deleted?

2015-02-02 Thread Mark Walkom

ES removes deleted docs via merging, not GC.

You can force a merge using the optimise API -
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-optimize.html#indices-optimize
- but be aware that it is resource intensive. Also be sure to read this
blog post -
http://www.elasticsearch.org/blog/lucenes-handling-of-deleted-documents/

On 3 February 2015 at 18:26, Jason Zhang moc...@gmail.com wrote:

Hi,

I use segmentspy to detect segment merges in ES. But I find there's
several Deleted Docs which is like Deleted Docs: 1.55630.
I know ES will mark items as deleted and remove them later through GC.

But what's the meaning of those deleted segments? Why does ES/lucene not
remove them? There's no updates in this index since 10 days ago.
How can I clean them out explicitly?

Thank you.

--
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/8f0458a6-53ee-4e38-a3cc-6564eb693040%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/8f0458a6-53ee-4e38-a3cc-6564eb693040%40googlegroups.com?utm_medium=emailutm_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/CAEYi1X9nurQur0KfHSv9TJgQf9FsoRSKNXOLUjAJaVbnhp9DEg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Segments marked as deleted?

2015-02-02 Thread Jason Zhang

I've tried `curl -XPOST http://foo:9200/bar/_optimize`, but there's still
some Deleted Docs here. Is this normal?

On Tuesday, February 3, 2015 at 3:31:02 PM UTC+8, Mark Walkom wrote:

ES removes deleted docs via merging, not GC.

You can force a merge using the optimise API -
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-optimize.html#indices-optimize

- but be aware that it is resource intensive. Also be sure to read this
blog post -
http://www.elasticsearch.org/blog/lucenes-handling-of-deleted-documents/

On 3 February 2015 at 18:26, Jason Zhang moc...@gmail.com javascript:
wrote:

Hi,

I use segmentspy to detect segment merges in ES. But I find there's
several Deleted Docs which is like Deleted Docs: 1.55630.
I know ES will mark items as deleted and remove them later through GC.

But what's the meaning of those deleted segments? Why does ES/lucene
not remove them? There's no updates in this index since 10 days ago.
How can I clean them out explicitly?

Thank you.

https://groups.google.com/d/msgid/elasticsearch/8f0458a6-53ee-4e38-a3cc-6564eb693040%40googlegroups.com?utm_medium=emailutm_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/8158bc66-2970-43b3-b771-6bc3d1c6cd87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Segments marked as deleted?

2015-02-02 Thread Mark Walkom

How many?

The amount of deleted docs really depends on the atomicity of the index.

On 3 February 2015 at 18:44, Jason Zhang moc...@gmail.com wrote:

I've tried `curl -XPOST http://foo:9200/bar/_optimize`
http://foo:9200/bar/_optimize, but there's still some Deleted Docs
here. Is this normal?

On Tuesday, February 3, 2015 at 3:31:02 PM UTC+8, Mark Walkom wrote:

ES removes deleted docs via merging, not GC.

You can force a merge using the optimise API -
http://www.elasticsearch.org/guide/en/elasticsearch/
reference/current/indices-optimize.html#indices-optimize - but be aware
that it is resource intensive. Also be sure to read this blog post -
http://www.elasticsearch.org/blog/lucenes-handling-of-deleted-documents/

On 3 February 2015 at 18:26, Jason Zhang moc...@gmail.com wrote:

Hi,

I use segmentspy to detect segment merges in ES. But I find there's
several Deleted Docs which is like Deleted Docs: 1.55630.
I know ES will mark items as deleted and remove them later through GC.

But what's the meaning of those deleted segments? Why does ES/lucene
not remove them? There's no updates in this index since 10 days ago.
How can I clean them out explicitly?

Thank you.

--
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/8f0458a6-53ee-4e38-a3cc-6564eb693040%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/8f0458a6-53ee-4e38-a3cc-6564eb693040%40googlegroups.com?utm_medium=emailutm_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/8158bc66-2970-43b3-b771-6bc3d1c6cd87%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/8158bc66-2970-43b3-b771-6bc3d1c6cd87%40googlegroups.com?utm_medium=emailutm_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/CAEYi1X8F0FznwO3QBbCkvTwMD2H_FpyRcDdu8xoPLr6JCU%3D8CA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Java client node creates data directory

No each node will use its own subdir. This also applies to data nodes BTW.

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr
https://twitter.com/elasticsearchfr | @scrutmydocs
https://twitter.com/scrutmydocs

Le 2 févr. 2015 à 16:30, Daniel Woo daniel.y@gmail.com a écrit :

Using a transport client would be slightly slower due to the two-hops, that's
why I prefer a client node. I guess a pure client node just need some cluster
info in memory, I don't see a reason why client need to save cluster info to
disk.
Now I have a interesting question, if I start multiple client nodes (multiple
VMs with the same working directory), they will write to the same temporary
data directory, will the data directory be messed up?

On Monday, February 2, 2015 at 10:31:34 PM UTC+8, David Pilato wrote:
As it's a node, it's storing some cluster info in it.
You could use a Transport Client which will act as a pure Client without
joining the cluster.

--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 2 févr. 2015 à 15:08, Daniel Woo daniel...@gmail.com javascript: a
écrit :

Hi guys, I start a client node with the parameter node.data turned off,
why is the data directory automatically created in my working directory? Can
I avoid creating the data directory since it's a pure client node?

https://groups.google.com/d/msgid/elasticsearch/37534520-ec4d-4076-b6c6-d6c65b2f9207%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout
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
mailto:elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/74ad7956-564c-46dd-abaf-5cd7475eacb4%40googlegroups.com

https://groups.google.com/d/msgid/elasticsearch/74ad7956-564c-46dd-abaf-5cd7475eacb4%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout
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/A462087C-2E39-4949-A61D-8BFA46A46475%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Re: Elastic search with CouchDB river plugin - Can't find any documents

Anything in logs?

-- 
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr 
https://twitter.com/elasticsearchfr | @scrutmydocs 
https://twitter.com/scrutmydocs



 Le 2 févr. 2015 à 17:04, Bao-Quan Ho ho.baoq...@gmail.com a écrit :
 
 Hello I tried as suggested but I get the same outcome:
 
 # curl localhost:9200/testdb/_search?pretty=1
 {
   took : 1,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }
 
 On Mon, Feb 2, 2015 at 6:35 AM, David Pilato da...@pilato.fr 
 mailto:da...@pilato.fr wrote:
 Try with:
 
 localhost:9200/testdb/_search
 
 I think you are using the default type name here which is not IIRC the river 
 name.
 
 HTH
 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
 
 Le 2 févr. 2015 à 11:43, Bao-Quan Ho ho.baoq...@gmail.com 
 mailto:ho.baoq...@gmail.com a écrit :
 
 David,
 
 Sorry for the old post revival, but I'm getting this same error with no hits 
 with Couchdb rivers (2.4.1), Elasticsearch (1.4.2), and Couchdb (1.6.1).  I 
 am fairly new to using couch-rivers but I've installed all the applications 
 and they are running on Centos 7.  Can you please see if you notice anything 
 wrong?  I've looked everywhere but can not find a solution.  Thank you in 
 advance
 
 
 I added some dummy data into my couchdb database testdb:
 # curl -XGET localhost:5984/testdb/_changes
 {results:[
 {seq:1,id:1,changes:[{rev:1-0291.}]},
 {seq:2,id:2,changes:[{rev:1-1945.}]},
 {seq:3,id:3,changes:[{rev:1-62a5.}]},
 {seq:4,id:4,changes:[{rev:1-7e93.}]},
 ],
 last_seq:4}
 
 
 I run this to make the index:
 # curl -X PUT 'http://localhost:9200/_river/testdb/_meta' 
 http://localhost:9200/_river/testdb/_meta' -d '{ type : couchdb, 
 couchdb : { host : localhost, port : 5984, db : testdb, filter 
 : null }'
 
 Get a return of:
 # 
 {index:_river,_type:testdb,_id:_meta,_version:1,created:true}
 
 When I try to do the query:
 # curl localhost:9200/testdb/testdb/_search?pretty=1
 {
   took : 1,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }
 
 
 
 When I use the 
 # curl http://localhost:9200/_search?q=*pretty=true 
 http://localhost:9200/_search?q=*pretty=true
 {
   took : 2,
   timed_out : false,
   _shards : {
 total : 16,
 successful : 16,
 failed : 0
   },
   hits : {
 total : 1,
 max_score : 1.0,
 hits : [ {
   _index : _river,
   _type : testdb,
   _id : _meta,
   _score : 1.0,
   _source : {type couchdb, couchdb : {host : localhost, 
 port: 5984, db : testdb, filter : null}}
   } ]
   }
 }
 
 
 
 
 
 On Wednesday, June 5, 2013 at 1:59:04 AM UTC-4, David Pilato wrote:
 Just to double check, could you run:
 http://localhost:9200/_search?q=*pretty=true 
 http://localhost:9200/my_db/_search?q=*pretty=true
 
 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
 
 
 Le 5 juin 2013 à 00:19, Yannis Psarras yannis@gmail.com  a écrit :
 
 And with the q=* I get the same really as above
 
 (for query: http://localhost:9200/my_db/_search?q=*pretty=true 
 http://localhost:9200/my_db/_search?q=*pretty=true)
 
 
 On Wed, Jun 5, 2013 at 1:17 AM, Yannis Psarras yannis@gmail.com  
 wrote:
 I get the following:
 
 curl -XGET http://localhost:9200/my_db/_search?pretty=true 
 http://localhost:9200/my_db/my_db/_search?pretty=true
 {
   took : 2,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }
 
 
 On Wed, Jun 5, 2013 at 12:53 AM, David Pilato da...@pilato.fr  wrote:
 Not sure that default type is dbname.
 What do you get with:
 curl -XGET http://localhost:9200/my_db/_search?q=*pretty=true 
 http://localhost:9200/my_db/_search?q=*pretty=true
 ?
 
 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
 
 
 Le 4 juin 2013 à 23:26, Yannis Psarras yannis@gmail.com  a écrit :
 
 I recently started using elastic search and couchdb and I have the following 
 problem. I have a couch database with a bunch of documents. I add a couch db 
 river index on elastic search and I expect to have those documents indexed 
 and searchable. But when I search for anything through ES I dont get any 
 results. The command flow is as follows:
 
 The command above verifies that there are 4 documents in the couch db 
 instance
 
 curl -H Content-Type: application/json -X GET http://localhost:5984/my_db 
 http://localhost:5984/my_db
 
 {db_name:my_db,doc_count:4,doc_del_count:0,update_seq:4,purge_seq:0,compact_running:false,disk_size:16482,data_size:646,instance_start_time:1370204643908592,disk_format_version:6,committed_update_seq:4}
 The _changes output:
 
 curl -H Content-Type: application/json -X GET

Re: Elastic search with CouchDB river plugin - Can't find any documents

looking in /vars/log/elasticsearch/elasticsearch.log
[2015-02-02 10:42:31,415][INFO ][river.couchdb ][Matt Murdock][couchdb][
testdb] starting couchdb stream: host [localhost], port [5984], filter [null
], db [testdb], indexing to [testdb]/[testdb]


On Monday, February 2, 2015 at 11:05:53 AM UTC-5, David Pilato wrote:

 Anything in logs?

 -- 
 *David Pilato* | *Technical Advocate* | *Elasticsearch.com 
 http://Elasticsearch.com*
 @dadoonet https://twitter.com/dadoonet | @elasticsearchfr 
 https://twitter.com/elasticsearchfr | @scrutmydocs 
 https://twitter.com/scrutmydocs


  
 Le 2 févr. 2015 à 17:04, Bao-Quan Ho ho.ba...@gmail.com javascript: a 
 écrit :

 Hello I tried as suggested but I get the same outcome:

 # curl localhost:9200/testdb/_search?pretty=1
 {
   took : 1,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }

 On Mon, Feb 2, 2015 at 6:35 AM, David Pilato da...@pilato.fr 
 javascript: wrote:

 Try with:

 localhost:9200/testdb/_search

 I think you are using the default type name here which is not IIRC the 
 river name.

 HTH
 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

 Le 2 févr. 2015 à 11:43, Bao-Quan Ho ho.ba...@gmail.com javascript: a 
 écrit :

 David,

 Sorry for the old post revival, but I'm getting this same error with no 
 hits with Couchdb rivers (2.4.1), Elasticsearch (1.4.2), and Couchdb 
 (1.6.1).  I am fairly new to using couch-rivers but I've installed all the 
 applications and they are running on Centos 7.  Can you please see if you 
 notice anything wrong?  I've looked everywhere but can not find a 
 solution.  Thank you in advance


 I added some dummy data into my couchdb database testdb:
 # curl -XGET localhost:5984/testdb/_changes
 {results:[
 {seq:1,id:1,changes:[{rev:1-0291.}]},
 {seq:2,id:2,changes:[{rev:1-1945.}]},
 {seq:3,id:3,changes:[{rev:1-62a5.}]},
 {seq:4,id:4,changes:[{rev:1-7e93.}]},
 ],
 last_seq:4}


 I run this to make the index:
 # curl -X PUT 'http://localhost:9200/_river/testdb/_meta' -d '{ type : 
 couchdb, couchdb : { host : localhost, port : 5984, db : 
 testdb, filter : null }'

 Get a return of:
 # 
 {index:_river,_type:testdb,_id:_meta,_version:1,created:true}

 When I try to do the query:
 # curl localhost:9200/testdb/testdb/_search?pretty=1
 {
   took : 1,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }



 When I use the 
 # curl http://localhost:9200/_search?q=*pretty=true
 {
   took : 2,
   timed_out : false,
   _shards : {
 total : 16,
 successful : 16,
 failed : 0
   },
   hits : {
 total : 1,
 max_score : 1.0,
 hits : [ {
   _index : _river,
   _type : testdb,
   _id : _meta,
   _score : 1.0,
   _source : {type couchdb, couchdb : {host : localhost, 
 port: 5984, db : testdb, filter : null}}
   } ]
   }
 }





 On Wednesday, June 5, 2013 at 1:59:04 AM UTC-4, David Pilato wrote:

 Just to double check, could you run:
 http://localhost:9200/_search?q=*pretty=true 
 http://localhost:9200/my_db/_search?q=*pretty=true

 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs


 Le 5 juin 2013 à 00:19, Yannis Psarras yannis@gmail.com a écrit :

 And with the q=* I get the same really as above

 (for query: http://localhost:9200/my_db/_search?q=*pretty=true)


 On Wed, Jun 5, 2013 at 1:17 AM, Yannis Psarras yannis@gmail.com 
 wrote:

 I get the following:

 curl -XGET http://localhost:9200/my_db/_search?pretty=true 
 http://localhost:9200/my_db/my_db/_search?pretty=true
 {
   took : 2,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }



 On Wed, Jun 5, 2013 at 12:53 AM, David Pilato da...@pilato.fr wrote:

 Not sure that default type is dbname.
 What do you get with:

 curl -XGET http://localhost:9200/my_db/_search?q=*pretty=true;

 ?

 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs


 Le 4 juin 2013 à 23:26, Yannis Psarras yannis@gmail.com a écrit :

 I recently started using elastic search and couchdb and I have the 
 following problem. I have a couch database with a bunch of documents. I add 
 a couch db river index on elastic search and I expect to have those 
 documents indexed and searchable. But when I search for anything through ES 
 I dont get any results. The command flow is as follows:

 The command above verifies that there are 4 documents in the couch db 
 instance

 curl -H Content-Type: application/json -X GET http://localhost:5984/my_db

Re: Elastic search with CouchDB river plugin - Can't find any documents

So you should try to change logs to DEBUG or TRACE and see what it tells.


-- 
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr 
https://twitter.com/elasticsearchfr | @scrutmydocs 
https://twitter.com/scrutmydocs



 Le 2 févr. 2015 à 17:20, Bao-Quan Ho ho.baoq...@gmail.com a écrit :
 
 looking in /vars/log/elasticsearch/elasticsearch.log
 [2015-02-02 10:42:31,415][INFO ][river.couchdb ][Matt 
 Murdock][couchdb][testdb] starting couchdb stream: host [localhost], port 
 [5984], filter [null], db [testdb], indexing to [testdb]/[testdb]
 
 
 On Monday, February 2, 2015 at 11:05:53 AM UTC-5, David Pilato wrote:
 Anything in logs?
 
 -- 
 David Pilato | Technical Advocate | Elasticsearch.com 
 http://elasticsearch.com/
 @dadoonet https://twitter.com/dadoonet | @elasticsearchfr 
 https://twitter.com/elasticsearchfr | @scrutmydocs 
 https://twitter.com/scrutmydocs
 
 
 
 Le 2 févr. 2015 à 17:04, Bao-Quan Ho ho.ba...@gmail.com javascript: a 
 écrit :
 
 Hello I tried as suggested but I get the same outcome:
 
 # curl localhost:9200/testdb/_search?pretty=1
 {
   took : 1,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }
 
 On Mon, Feb 2, 2015 at 6:35 AM, David Pilato da...@pilato.fr javascript: 
 wrote:
 Try with:
 
 localhost:9200/testdb/_search
 
 I think you are using the default type name here which is not IIRC the river 
 name.
 
 HTH
 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
 
 Le 2 févr. 2015 à 11:43, Bao-Quan Ho ho.ba...@gmail.com javascript: a 
 écrit :
 
 David,
 
 Sorry for the old post revival, but I'm getting this same error with no hits 
 with Couchdb rivers (2.4.1), Elasticsearch (1.4.2), and Couchdb (1.6.1).  I 
 am fairly new to using couch-rivers but I've installed all the applications 
 and they are running on Centos 7.  Can you please see if you notice anything 
 wrong?  I've looked everywhere but can not find a solution.  Thank you in 
 advance
 
 
 I added some dummy data into my couchdb database testdb:
 # curl -XGET localhost:5984/testdb/_changes
 {results:[
 {seq:1,id:1,changes:[{rev:1-0291.}]},
 {seq:2,id:2,changes:[{rev:1-1945.}]},
 {seq:3,id:3,changes:[{rev:1-62a5.}]},
 {seq:4,id:4,changes:[{rev:1-7e93.}]},
 ],
 last_seq:4}
 
 
 I run this to make the index:
 # curl -X PUT 'http://localhost:9200/_river/testdb/_meta' 
 http://localhost:9200/_river/testdb/_meta' -d '{ type : couchdb, 
 couchdb : { host : localhost, port : 5984, db : testdb, filter 
 : null }'
 
 Get a return of:
 # 
 {index:_river,_type:testdb,_id:_meta,_version:1,created:true}
 
 When I try to do the query:
 # curl localhost:9200/testdb/testdb/_search?pretty=1
 {
   took : 1,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }
 
 
 
 When I use the 
 # curl http://localhost:9200/_search?q=*pretty=true 
 http://localhost:9200/_search?q=*pretty=true
 {
   took : 2,
   timed_out : false,
   _shards : {
 total : 16,
 successful : 16,
 failed : 0
   },
   hits : {
 total : 1,
 max_score : 1.0,
 hits : [ {
   _index : _river,
   _type : testdb,
   _id : _meta,
   _score : 1.0,
   _source : {type couchdb, couchdb : {host : localhost, 
 port: 5984, db : testdb, filter : null}}
   } ]
   }
 }
 
 
 
 
 
 On Wednesday, June 5, 2013 at 1:59:04 AM UTC-4, David Pilato wrote:
 Just to double check, could you run:
 http://localhost:9200/_search?q=*pretty=true 
 http://localhost:9200/my_db/_search?q=*pretty=true
 
 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
 
 
 Le 5 juin 2013 à 00:19, Yannis Psarras yannis@gmail.com  a écrit :
 
 And with the q=* I get the same really as above
 
 (for query: http://localhost:9200/my_db/_search?q=*pretty=true 
 http://localhost:9200/my_db/_search?q=*pretty=true)
 
 
 On Wed, Jun 5, 2013 at 1:17 AM, Yannis Psarras yannis@gmail.com  
 wrote:
 I get the following:
 
 curl -XGET http://localhost:9200/my_db/_search?pretty=true 
 http://localhost:9200/my_db/my_db/_search?pretty=true
 {
   took : 2,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }
 
 
 On Wed, Jun 5, 2013 at 12:53 AM, David Pilato da...@pilato.fr  wrote:
 Not sure that default type is dbname.
 What do you get with:
 curl -XGET http://localhost:9200/my_db/_search?q=*pretty=true 
 http://localhost:9200/my_db/_search?q=*pretty=true
 ?
 
 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
 
 
 Le 4 juin 2013 à 23:26, Yannis Psarras yannis@gmail.com  a écrit :
 
 I recently started using elastic search and couchdb and I have the following 
 problem. I have a couch database with a bunch

Re: Elastic search with CouchDB river plugin - Can't find any documents

Hello I tried as suggested but I get the same outcome:

# curl localhost:9200/testdb/_search?pretty=1
{
  took : 1,
  timed_out : false,
  _shards : {
total : 5,
successful : 5,
failed : 0
  },
  hits : {
total : 0,
max_score : null,
hits : [ ]
  }
}

On Mon, Feb 2, 2015 at 6:35 AM, David Pilato da...@pilato.fr wrote:

 Try with:

 localhost:9200/testdb/_search

 I think you are using the default type name here which is not IIRC the
 river name.

 HTH
 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

 Le 2 févr. 2015 à 11:43, Bao-Quan Ho ho.baoq...@gmail.com a écrit :

 David,

 Sorry for the old post revival, but I'm getting this same error with no
 hits with Couchdb rivers (2.4.1), Elasticsearch (1.4.2), and Couchdb
 (1.6.1).  I am fairly new to using couch-rivers but I've installed all the
 applications and they are running on Centos 7.  Can you please see if you
 notice anything wrong?  I've looked everywhere but can not find a
 solution.  Thank you in advance


 I added some dummy data into my couchdb database testdb:
 # curl -XGET localhost:5984/testdb/_changes
 {results:[
 {seq:1,id:1,changes:[{rev:1-0291.}]},
 {seq:2,id:2,changes:[{rev:1-1945.}]},
 {seq:3,id:3,changes:[{rev:1-62a5.}]},
 {seq:4,id:4,changes:[{rev:1-7e93.}]},
 ],
 last_seq:4}


 I run this to make the index:
 # curl -X PUT 'http://localhost:9200/_river/testdb/_meta' -d '{ type :
 couchdb, couchdb : { host : localhost, port : 5984, db :
 testdb, filter : null }'

 Get a return of:
 #
 {index:_river,_type:testdb,_id:_meta,_version:1,created:true}

 When I try to do the query:
 # curl localhost:9200/testdb/testdb/_search?pretty=1
 {
   took : 1,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }



 When I use the
 # curl http://localhost:9200/_search?q=*pretty=true
 {
   took : 2,
   timed_out : false,
   _shards : {
 total : 16,
 successful : 16,
 failed : 0
   },
   hits : {
 total : 1,
 max_score : 1.0,
 hits : [ {
   _index : _river,
   _type : testdb,
   _id : _meta,
   _score : 1.0,
   _source : {type couchdb, couchdb : {host : localhost,
 port: 5984, db : testdb, filter : null}}
   } ]
   }
 }





 On Wednesday, June 5, 2013 at 1:59:04 AM UTC-4, David Pilato wrote:

 Just to double check, could you run:
 http://localhost:9200/_search?q=*pretty=true
 http://localhost:9200/my_db/_search?q=*pretty=true

 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs


 Le 5 juin 2013 à 00:19, Yannis Psarras yannis@gmail.com a écrit :

 And with the q=* I get the same really as above

 (for query: http://localhost:9200/my_db/_search?q=*pretty=true)


 On Wed, Jun 5, 2013 at 1:17 AM, Yannis Psarras yannis@gmail.com
 wrote:

 I get the following:

 curl -XGET http://localhost:9200/my_db/_search?pretty=true 
 http://localhost:9200/my_db/my_db/_search?pretty=true
 {
   took : 2,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }



 On Wed, Jun 5, 2013 at 12:53 AM, David Pilato da...@pilato.fr wrote:

 Not sure that default type is dbname.
 What do you get with:

 curl -XGET http://localhost:9200/my_db/_search?q=*pretty=true;

 ?

 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs


 Le 4 juin 2013 à 23:26, Yannis Psarras yannis@gmail.com a écrit :

 I recently started using elastic search and couchdb and I have the
 following problem. I have a couch database with a bunch of documents. I add
 a couch db river index on elastic search and I expect to have those
 documents indexed and searchable. But when I search for anything through ES
 I dont get any results. The command flow is as follows:

 The command above verifies that there are 4 documents in the couch db
 instance

 curl -H Content-Type: application/json -X GET http://localhost:5984/my_db

 {db_name:my_db,doc_count:4,doc_del_count:0,update_seq:4,purge_seq:0,compact_running:false,disk_size:16482,data_size:646,instance_start_time:1370204643908592,disk_format_version:6,committed_update_seq:4}

 The _changes output:

 curl -H Content-Type: application/json -X GET 
 http://localhost:5984/my_db/_changes
 {results:[
 {seq:1,id:1,changes:[{rev:1-40d928a959dd52d183ab7c413fabca92}]},
 {seq:2,id:2,changes:[{rev:1-42212757a56b240f5205266b1969e890}]},
 {seq:3,id:3,changes:[{rev:1-f59c2ae7acacb68d9414be05d56ed33a}]},
 {seq:4,id:4,changes:[{rev:1-e86cf1c287c16906e81d901365b9bf98}]}
 ],
 last_seq:4}

 Now, below I m creating my index in ES.

 curl -XPUT 'http://localhost:9200/_river/my_db/_meta' -d '{ type : 
 couchdb, couchdb : { host : localhost, port : 5984, db : 
 my_db, filter : null } }'

 {ok:true,_index:_river,_type:my_db,_id:_meta,_version:1}

 But I dont get anything back.

 curl -XGET

Re: Elastic search with CouchDB river plugin - Can't find any documents

Hello I tried as suggested but I get the same outcome:

# curl localhost:9200/testdb/_search?pretty=1


{
  took : 1,
  timed_out : false,
  _shards : {
total : 5,
successful : 5,
failed : 0
  },
  hits : {
total : 0,
max_score : null,
hits : [ ]
  }
}





On Monday, February 2, 2015 at 6:35:59 AM UTC-5, David Pilato wrote:

 Try with:

 localhost:9200/testdb/_search

 I think you are using the default type name here which is not IIRC the 
 river name.

 HTH
 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

 Le 2 févr. 2015 à 11:43, Bao-Quan Ho ho.ba...@gmail.com javascript: a 
 écrit :

 David,

 Sorry for the old post revival, but I'm getting this same error with no 
 hits with Couchdb rivers (2.4.1), Elasticsearch (1.4.2), and Couchdb 
 (1.6.1).  I am fairly new to using couch-rivers but I've installed all the 
 applications and they are running on Centos 7.  Can you please see if you 
 notice anything wrong?  I've looked everywhere but can not find a solution. 
  Thank you in advance


 I added some dummy data into my couchdb database testdb:
 # curl -XGET localhost:5984/testdb/_changes
 {results:[
 {seq:1,id:1,changes:[{rev:1-0291.}]},
 {seq:2,id:2,changes:[{rev:1-1945.}]},
 {seq:3,id:3,changes:[{rev:1-62a5.}]},
 {seq:4,id:4,changes:[{rev:1-7e93.}]},
 ],
 last_seq:4}


 I run this to make the index:
 # curl -X PUT 'http://localhost:9200/_river/testdb/_meta' -d '{ type : 
 couchdb, couchdb : { host : localhost, port : 5984, db : 
 testdb, filter : null }'

 Get a return of:
 # 
 {index:_river,_type:testdb,_id:_meta,_version:1,created:true}

 When I try to do the query:
 # curl localhost:9200/testdb/testdb/_search?pretty=1
 {
   took : 1,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }



 When I use the 
 # curl http://localhost:9200/_search?q=*pretty=true
 {
   took : 2,
   timed_out : false,
   _shards : {
 total : 16,
 successful : 16,
 failed : 0
   },
   hits : {
 total : 1,
 max_score : 1.0,
 hits : [ {
   _index : _river,
   _type : testdb,
   _id : _meta,
   _score : 1.0,
   _source : {type couchdb, couchdb : {host : localhost, 
 port: 5984, db : testdb, filter : null}}
   } ]
   }
 }





 On Wednesday, June 5, 2013 at 1:59:04 AM UTC-4, David Pilato wrote:

 Just to double check, could you run:
 http://localhost:9200/_search?q=*pretty=true 
 http://localhost:9200/my_db/_search?q=*pretty=true

 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs


 Le 5 juin 2013 à 00:19, Yannis Psarras yannis@gmail.com a écrit :

 And with the q=* I get the same really as above

 (for query: http://localhost:9200/my_db/_search?q=*pretty=true)


 On Wed, Jun 5, 2013 at 1:17 AM, Yannis Psarras yannis@gmail.com 
 wrote:

 I get the following:

 curl -XGET http://localhost:9200/my_db/_search?pretty=true 
 http://localhost:9200/my_db/my_db/_search?pretty=true
 {
   took : 2,
   timed_out : false,
   _shards : {
 total : 5,
 successful : 5,
 failed : 0
   },
   hits : {
 total : 0,
 max_score : null,
 hits : [ ]
   }
 }



 On Wed, Jun 5, 2013 at 12:53 AM, David Pilato da...@pilato.fr wrote:

 Not sure that default type is dbname.
 What do you get with:

 curl -XGET http://localhost:9200/my_db/_search?q=*pretty=true;

 ?

 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs


 Le 4 juin 2013 à 23:26, Yannis Psarras yannis@gmail.com a écrit :

 I recently started using elastic search and couchdb and I have the 
 following problem. I have a couch database with a bunch of documents. I 
 add 
 a couch db river index on elastic search and I expect to have those 
 documents indexed and searchable. But when I search for anything through 
 ES 
 I dont get any results. The command flow is as follows:

 The command above verifies that there are 4 documents in the couch db 
 instance

 curl -H Content-Type: application/json -X GET http://localhost:5984/my_db

 {db_name:my_db,doc_count:4,doc_del_count:0,update_seq:4,purge_seq:0,compact_running:false,disk_size:16482,data_size:646,instance_start_time:1370204643908592,disk_format_version:6,committed_update_seq:4}

 The _changes output:

 curl -H Content-Type: application/json -X GET 
 http://localhost:5984/my_db/_changes
 {results:[
 {seq:1,id:1,changes:[{rev:1-40d928a959dd52d183ab7c413fabca92}]},
 {seq:2,id:2,changes:[{rev:1-42212757a56b240f5205266b1969e890}]},
 {seq:3,id:3,changes:[{rev:1-f59c2ae7acacb68d9414be05d56ed33a}]},
 {seq:4,id:4,changes:[{rev:1-e86cf1c287c16906e81d901365b9bf98}]}
 ],
 last_seq:4}

 Now, below I m creating my index in ES.

 curl -XPUT 'http://localhost:9200/_river/my_db/_meta' -d '{ type : 
 couchdb, couchdb : { host : localhost, port : 5984, db : 
 my_db, filter : null } }'

 {ok:true,_index:_river,_type:my_db,_id:_meta,_version:1}

 But I dont get

Re: Obtain jdbc river state via java api

2015-02-02 Thread joergpra...@gmail.com

There is no stateful river concept in Elasticsearch.

Jörg

On Mon, Feb 2, 2015 at 3:57 PM, Abid Hussain huss...@novacom.mygbiz.com
wrote:

 Hi all,

 is there a way to obtain state of a certain river (like *GET
 /_river/jdbc/river-name/_state*) via TransportClient or any other kind
 of java api call?

 If not, I would have to perform a http get request programmatically and
 parse json result, I guess...

 Regards,

 Abid

 --
 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/eda0c348-4938-4900-a822-37aa520da7fe%40googlegroups.com
 https://groups.google.com/d/msgid/elasticsearch/eda0c348-4938-4900-a822-37aa520da7fe%40googlegroups.com?utm_medium=emailutm_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/CAKdsXoE5B_oJn9A8%2Bi3-Vzqhiazgij0Q%2BRR77XfA1fpZ162Z2w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: not able to refine from o/p of query in logstash

2015-02-02 Thread raj@

can some put some light on my problem. I am sorry to bump this thread again.
I am not able to get any idea if we have any option that we can call another
script within my logstash query to get on my requirements.

Please let me know if anything is not clear.

Thanks In advance !




--
View this message in context: 
http://elasticsearch-users.115913.n3.nabble.com/not-able-to-refine-from-o-p-of-query-in-logstash-tp4069573p4069952.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.

-- 
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/1422904061306-4069952.post%40n3.nabble.com.
For more options, visit https://groups.google.com/d/optout.

Re: Elastic search with CouchDB river plugin - Can't find any documents