Jing
here is the new releases compatible with 1.7.10
https://oss.sonatype.org/content/repositories/releases/com/orientechnologies/orientdb-lucene/1.7.10/orientdb-lucene-1.7.10-dist.jar
Try it and tell me if the issue still occurs
Enrico
2015-01-14 0:14 GMT+01:00 Jing Chen
Thanks Enrico. We have downloaded the new release and will test it out
today.
On Wednesday, January 14, 2015 at 7:15:38 AM UTC-8, Enrico Risa wrote:
Jing
here is the new releases compatible with 1.7.10
Hi Enrico and OrientDB team,
I just wanted to comment on the implications of this issue: after the error
occurs, all subsequent operations that invoke search will fail.
Our only solution is to restart the server!
Moreover, the error has happened several times on our production server
that -
Hi Jing
i see this error:
Caused by: org.apache.lucene.queryparser.classic.ParseException: Cannot
parse '*hoxd3': '*' or '?' not allowed as first character in WildcardQuery
is not a valid syntax syntax
But after this error you got
targetGen=14871 right?
We have done a ton of fixes on lucene
Hi Enrico,
This error came out again and completely brought the search function down
in our production site. It becomes a very critical issue for us, and we
really appreciate if you can help us to resolve this issue.
Here are some more information I found from our tomcat log. Hope it can
Hi Enrico,
I did more tests and it seems the ParseException won't cause the closure of
Lucene index. It is more likely to be the other error:
2015-01-12 16:22:58:555 INFO Account 80421cb7-39f3-11e4-a848-
000c29202374 does not exist for class: user
Great! Thanks.
On Tuesday, January 13, 2015 at 3:06:57 PM UTC-8, Enrico Risa wrote:
Hi Jing
tomorrow i will roll a release with some backports from 2.0,
so you can try if resolve this issue. I will send you the link
2015-01-14 0:03 GMT+01:00 Jing Chen jingj...@gmail.com javascript::
Hi
Hi Enrico,
Thanks for looking into this. I couldn't create a test case to reproduce
this this error yet. It seems to happen when we try to call a rollback()
(in the graph API) in a connection and then close the connection. This can
trigger the error sometimes.
Thanks,
Jing
On Friday,
Hi Jing
I see that seems that somehow the index was closed ad then start to give
the second error.
i'm trying to replicate it any hint on how can replicate it?
2015-01-09 19:09 GMT+01:00 Jing Chen jingjing...@gmail.com:
Hi Enrico,
Could you take a look of this problem? What could be the
Hi Enrico,
Could you take a look of this problem? What could be the cause of it and is
there anything we can do in our application to avoid this? This error
failed all the search functions on our production server.
Thanks,
Jing
On Monday, January 5, 2015 at 11:32:12 AM UTC-8, Jing Chen
10 matches
Mail list logo
