from:"Aaliyah"

Re: ES doesn't work with rexster gremlin extension

2014-07-03 Thread Aaliyah

Nobody has some idea?

在 2014年7月2日星期三UTC+2下午9时41分52秒，Aaliyah写道：
>
> the problem is like the topic. I'm not sure if I misunderstood something 
> or I missed some configurations. The ES works fine in usual situations, but 
> doesn't work with rexster gremlin extension. 
>
> In java, I configured the graph as follows:
>
>
> <https://lh3.googleusercontent.com/-kd6vKDQdH6g/U7RbYPE-ciI/AHk/sSU5e5R3DMM/s1600/1.PNG>
>
>
> <https://lh3.googleusercontent.com/-9HiEPJmS1FQ/U7Rbjmg4oCI/AHs/2FgdAtjiBHc/s1600/2.PNG>
>
> In the extension, I wrote:
>
> *String query = "v." + propKey + ": (" + propValue + ")"; *
>
> *if(((TitanGraph) graph).indexQuery("search", 
> query).vertices().iterator().hasNext()){...}*
>
> When I invoked the extension, the rexster told: null pointer exception, 
> unknown index, etc. As follows:
>
>
> <https://lh4.googleusercontent.com/-I0w-hVgu0F0/U7RdQCcjOZI/AH4/4l13192eR2k/s1600/3.PNG>
>
>
> <https://lh3.googleusercontent.com/-phHCRqzQN6I/U7RdUkyE8oI/AIA/rhkTlffd8lI/s1600/4.PNG>
>
> After this, I searched some advices from google and made some 
> configurations in rexster.xml
>
>
> <https://lh4.googleusercontent.com/-_6zRCaQtvRw/U7ReJ41k4jI/AIQ/Nwgon5WqPtU/s1600/6.PNG>
>
> Then, the problems seemed as another way. (As you can see, first_example 
> is the name of the graph.)
>
>
> <https://lh5.googleusercontent.com/-r8TvH5CxjqA/U7Rfb9NFNEI/AIs/epemSCk5-8c/s1600/8.PNG>
>
> Besides, when I invoked the extension, I've been told: the graph is 
> non-configured.
>
>
> <https://lh4.googleusercontent.com/-uPWbHmgKL28/U7RfO3PoVlI/AIk/6ndP888fGYA/s1600/7.PNG>
>
> I've also tried the embedded mode. The problems seem to be the same.
>
> Plus,  I'm using:
>
> Titan 0.4.2
>
>  Tinkerpop 0.2.4
>
>  Cassandra 2.0.7
>
> ElasticSearch 1.2.1 
>
>
> This problem's driving me crazy. Any pointer would be appreciated! Thanks 
> in advance!
>
>
>
>
>
>
>
>
>
>
>
>

-- 
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/90b0b3a6-1ffd-4161-84b6-e56bda649b1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ES doesn't work with rexster gremlin extension

2014-07-02 Thread Aaliyah

the problem is like the topic. I'm not sure if I misunderstood something or
I missed some configurations. The ES works fine in usual situations, but
doesn't work with rexster gremlin extension.

In java, I configured the graph as follows:

In the extension, I wrote:

*String query = "v." + propKey + ": (" + propValue + ")"; *

*if(((TitanGraph) graph).indexQuery("search",
query).vertices().iterator().hasNext()){...}*

When I invoked the extension, the rexster told: null pointer exception,
unknown index, etc. As follows:

After this, I searched some advices from google and made some
configurations in rexster.xml

Then, the problems seemed as another way. (As you can see, first_example is
the name of the graph.)

Besides, when I invoked the extension, I've been told: the graph is
non-configured.

I've also tried the embedded mode. The problems seem to be the same.

Plus, I'm using:

Titan 0.4.2

Tinkerpop 0.2.4

Cassandra 2.0.7

ElasticSearch 1.2.1

This problem's driving me crazy. Any pointer would be appreciated! Thanks
in advance!

--
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/1a915c28-dd2f-4b72-b640-0fd8f9961c8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: No node available

2014-06-23 Thread Aaliyah

I'm using:
   Titan 0.4.2
   Tinkerpop 0.2.4
   Cassandra 2.0.7
   ElasticSearch 1.2.1

I did not add netty and lucene dependencies to my project indeed. But after 
I've done that, still got the same problem.

<https://lh6.googleusercontent.com/-BkWBCDrK89k/U6ifRxgOBZI/AHU/Yw-A2mDZM0A/s1600/4.PNG>

In fact, I added lucene-core of version 4.4.0 which is included in the lib 
folder of titan 0.4.2. But the problem was still there and there's another 
version 4.8.1 in the lib folder of elasticsearch 1.2.1. Then I tried the 
latter again. As you see, the same problem.

Earlier I also tried elasticsearch 0.90.3 which is said to be a compitable 
version with titan 0.4.2. It didn't work.




Am Montag, 23. Juni 2014 16:51:37 UTC+2 schrieb Ivan Brusic:
>
> Are you using the same version of the Elasticsearch jar with respect to 
> the server? Which version are you using? Do you have any added jar 
> dependencies to your project such as netty or Lucene?
>
> -- 
> Ivan
>
>
> On Mon, Jun 23, 2014 at 7:13 AM, Aaliyah 
> > wrote:
>
>> The log file has this content:
>>
>> [2014-06-23 16:07:32,313][WARN ][transport.netty  ] [Boost] 
>> exception caught on transport layer [[id: 0x0d18c137, /127.0.0.1:55654 
>> :> /127.0.0.1:9300]], closing connection
>> java.io.StreamCorruptedException: invalid internal transport message 
>> format
>> at 
>> org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeHeaderFrameDecoder.java:27)
>>  at 
>> org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
>> at 
>> org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
>>  at 
>> org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
>> at 
>> org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
>>  at 
>> org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
>> at 
>> org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:74)
>>  at 
>> org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
>> at 
>> org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
>>  at 
>> org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:268)
>> at 
>> org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:255)
>>  at 
>> org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
>> at 
>> org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109)
>>  at 
>> org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
>> at 
>> org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90)
>>  at 
>> org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
>> at 
>> org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
>>  at 
>> org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
>> at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>  at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:744)
>>
>>
>> 在 2014年6月23日星期一UTC+2下午2时47分52秒，Aaliyah写道：
>>
>>> I've just tried the first example with java, following http://www.
>>> elasticsearch.org/guide/en/elasticsearch/client/java-api/
>>> current/client.html and http://www.elasticsearch.org/guide/
>>> en/elasticsearch/client/java-api/current/index_.html. When I ran this 
>>> sample, got an NoNodeAvailableException.
>>>
>>> The code and the exception are in the following:
>>>
>>>
>>> <https://lh6.googleusercontent.com/-8N7TcjYn8T4/U6ggVcQI4PI/AG8/dyarDdKo2hQ/s1600/1.PNG>
>>>
>>>
>>> <https://lh6.googleusercontent.com/-8E0mGaN2Jh4/U6ggmlTfEYI/AHE/X0ZsVP1xYHg/s1600/2.PNG>
>>>
>>> I've searched some posted questions which are also like mine and 
>>> followed the suggestions to rectify my codes. But it didn't work.
>>>
>>> Does anybody have

Re: No node available

2014-06-23 Thread Aaliyah

The log file has this content:

[2014-06-23 16:07:32,313][WARN ][transport.netty  ] [Boost] 
exception caught on transport layer [[id: 0x0d18c137, /127.0.0.1:55654 :> 
/127.0.0.1:9300]], closing connection
java.io.StreamCorruptedException: invalid internal transport message format
at 
org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeHeaderFrameDecoder.java:27)
at 
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
at 
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
at 
org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
at 
org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
at 
org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
at 
org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:74)
at 
org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
at 
org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
at 
org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:268)
at 
org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:255)
at 
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
at 
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109)
at 
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at 
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90)
at 
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
at 
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at 
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)


在 2014年6月23日星期一UTC+2下午2时47分52秒，Aaliyah写道：
>
> I've just tried the first example with java, following 
> http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/current/client.html
>  and 
> http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/current/index_.html.
>  
> When I ran this sample, got an NoNodeAvailableException.
>
> The code and the exception are in the following:
>
>
> <https://lh6.googleusercontent.com/-8N7TcjYn8T4/U6ggVcQI4PI/AG8/dyarDdKo2hQ/s1600/1.PNG>
>
>
> <https://lh6.googleusercontent.com/-8E0mGaN2Jh4/U6ggmlTfEYI/AHE/X0ZsVP1xYHg/s1600/2.PNG>
>
> I've searched some posted questions which are also like mine and followed 
> the suggestions to rectify my codes. But it didn't work.
>
> Does anybody have an idea? Any pointer would be appreciated!
>
>
> Thanks in advance!
>
>
>
>

-- 
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/e5abfc69-3849-462e-aac2-500b4a8b29d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No node available

2014-06-23 Thread Aaliyah

I've just tried the first example with java, following 
http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/current/client.html
 and 
http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/current/index_.html.
 
When I ran this sample, got an NoNodeAvailableException.

The code and the exception are in the following:





I've searched some posted questions which are also like mine and followed 
the suggestions to rectify my codes. But it didn't work.

Does anybody have an idea? Any pointer would be appreciated!


Thanks in advance!



-- 
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/bb5ac8e6-2684-4ac5-9253-554e3a5f4a8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem when indexing data

2014-06-10 Thread Aaliyah

thanks a lot. It finally works.

在 2014年6月10日星期二UTC+2下午11时13分41秒，Jörg Prante写道：
>
> Just install Cygwin https://www.cygwin.com/ and leave Windows crappy 
> console behind.
>
> Jörg
>
>
> On Tue, Jun 10, 2014 at 9:31 PM, Aaliyah 
> > wrote:
>
>>
>>
>> I've already read a lot about installing and setting of elasticsearch. 
>> Most of them are for non-windosw OS. However, it seems the principle is 
>> sort of the same thing. So I followed one site 
>> http://www.elasticsearchtutorial.com/elasticsearch-in-5-minutes.html#Indexing
>>
>> My OS is windows 7. I've downloaded elasticsearch-1.2.1.zip and extracted 
>> it to C:\elasticsearch. Then ran it bin\elasticsearch and everything worked 
>> fine. 
>>
>>  
>> <https://lh6.googleusercontent.com/-wQsMdVDlveA/U5daKfkt_jI/AFw/2bE0u6XksFY/s1600/1.PNG>
>>
>> But when I started indexing data, then the problem came out.
>>
>> [image: screenshot 2] 
>> <https://lh4.googleusercontent.com/-WxchsYQv18g/U5daUyXdypI/AF8/aSTIxb1Sxe0/s1600/2.PNG>
>>
>>  I googled much about this problem which was often and was answered many 
>> times. Someone said it might be caused by the single quotation marks. Then 
>> I tried the other probabilities, but the problem was still there.
>>
>>
>> <https://lh3.googleusercontent.com/-KfpEvNthGhs/U5dcHzjcK5I/AGQ/Qmq3vL63YMk/s1600/3.PNG>
>>
>>
>> <https://lh6.googleusercontent.com/-3RlG5hHaO8A/U5dcXZtZCNI/AGc/bJOuEkWbQJA/s1600/4.PNG>
>>
>> Any pointer would be appreciated. Thanks in advance!
>>
>>
>>
>>
>>
>>
>>
>>  -- 
>> 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/b3f974af-a53b-4ef9-9f72-368dc10fbaa0%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/elasticsearch/b3f974af-a53b-4ef9-9f72-368dc10fbaa0%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/886091a5-e667-49fc-bdb7-da653e14d8f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem when indexing data

2014-06-10 Thread Aaliyah

thanks a lot. Finally it works.

在 2014年6月10日星期二UTC+2下午11时13分41秒，Jörg Prante写道：
>
> Just install Cygwin https://www.cygwin.com/ and leave Windows crappy 
> console behind.
>
> Jörg
>
>
> On Tue, Jun 10, 2014 at 9:31 PM, Aaliyah 
> > wrote:
>
>>
>>
>> I've already read a lot about installing and setting of elasticsearch. 
>> Most of them are for non-windosw OS. However, it seems the principle is 
>> sort of the same thing. So I followed one site 
>> http://www.elasticsearchtutorial.com/elasticsearch-in-5-minutes.html#Indexing
>>
>> My OS is windows 7. I've downloaded elasticsearch-1.2.1.zip and extracted 
>> it to C:\elasticsearch. Then ran it bin\elasticsearch and everything worked 
>> fine. 
>>
>>  
>> <https://lh6.googleusercontent.com/-wQsMdVDlveA/U5daKfkt_jI/AFw/2bE0u6XksFY/s1600/1.PNG>
>>
>> But when I started indexing data, then the problem came out.
>>
>> [image: screenshot 2] 
>> <https://lh4.googleusercontent.com/-WxchsYQv18g/U5daUyXdypI/AF8/aSTIxb1Sxe0/s1600/2.PNG>
>>
>>  I googled much about this problem which was often and was answered many 
>> times. Someone said it might be caused by the single quotation marks. Then 
>> I tried the other probabilities, but the problem was still there.
>>
>>
>> <https://lh3.googleusercontent.com/-KfpEvNthGhs/U5dcHzjcK5I/AGQ/Qmq3vL63YMk/s1600/3.PNG>
>>
>>
>> <https://lh6.googleusercontent.com/-3RlG5hHaO8A/U5dcXZtZCNI/AGc/bJOuEkWbQJA/s1600/4.PNG>
>>
>> Any pointer would be appreciated. Thanks in advance!
>>
>>
>>
>>
>>
>>
>>
>>  -- 
>> 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/b3f974af-a53b-4ef9-9f72-368dc10fbaa0%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/elasticsearch/b3f974af-a53b-4ef9-9f72-368dc10fbaa0%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/9ca0a0ff-8dfb-48d3-88be-2b030292b79d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Problem when indexing data

2014-06-10 Thread Aaliyah



I've already read a lot about installing and setting of elasticsearch. Most 
of them are for non-windosw OS. However, it seems the principle is sort of 
the same thing. So I followed one site 
http://www.elasticsearchtutorial.com/elasticsearch-in-5-minutes.html#Indexing

My OS is windows 7. I've downloaded elasticsearch-1.2.1.zip and extracted 
it to C:\elasticsearch. Then ran it bin\elasticsearch and everything worked 
fine. 



But when I started indexing data, then the problem came out.

[image: screenshot 2] 


 I googled much about this problem which was often and was answered many 
times. Someone said it might be caused by the single quotation marks. Then 
I tried the other probabilities, but the problem was still there.





Any pointer would be appreciated. Thanks in advance!







-- 
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/b3f974af-a53b-4ef9-9f72-368dc10fbaa0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ES doesn't work with rexster gremlin extension

ES doesn't work with rexster gremlin extension

Re: No node available

Re: No node available

No node available

Re: Problem when indexing data

Re: Problem when indexing data

Problem when indexing data

8 matches

Site Navigation

Mail list logo

Footer information