2010/11/14 Samuel Feng okos...@gmail.com
Mattias,
Thanks a lot. Please find my update in red.
Thanks and Regards,
Samuel
2010/11/14 Mattias Persson matt...@neotechnology.com
2010/11/13 Samuel Feng okos...@gmail.com
Hi,
I am new to neo4j.
I am using a custom analyzer
Hi all, I am checking out the Neo4j REST Server.
I put in the MATRIX examples and used curl -H Accept:application/json -H
Content-Type:application/json -X POST -d '{order:depth first}'
http://localhost:/node/3/traverse/node; to traverse the relations.
While doing that I have seen that the
Hi Christopher,
http://localhost:/node/1/relationships/in/{-list||types}
This is a URI template, inviting you to replace the {...} with values of your
own. In this case it's giving you the opportunity to provide a list of
ampersand separated types.
Now I believe this URI template syntax
Hi,
I am new to neo4j.
I am using a custom analyzer in index in order to support Chinese.
chnIndex = this.graphDb.index().forNodes(product_chinese,
MapUtil.stringMap(analyzer,
org.wltea.analyzer.lucene.IKAnalyzer));
Below is the usage of the IKAnalyzer in
Sounds fine to me. The main idea behind this suggestion is to support
concurrent access and the new server component. I can think of many use
cases where data is inserted in aa database from any type of client and
the result is accessed via e.g. geoserver. Currently we'd use PostGIS
for such
Hi Jim,
Yes I know what you mean, the {} are part of the JAX-RS specification.
I hope that I am not too controversy :-)
The Neo4j Rest server uses HTTP and JSON thats true, but it violates IMHO
some of the REST principles. I think that a technical interface should
contain, if the content is a
Hi Christopher,
Yes I know what you mean, the {} are part of the JAX-RS specification.
They're part of the URI template specification. JAX-RS uses these URI templates.
The Neo4j Rest server uses HTTP and JSON thats true, but it violates IMHO
some of the REST principles. I think that a
There is nothing fundamentally wrong with JSON (o.k. maybe a *few* things),
but with the right structures, it or any format can be completely
self-describing. I have found that including a bit of additional metadata in
the content helps IMMENSELY for both loosely-coupled and tightly-coupled
Hi,
To my understanding, if you use one
Similarity in indexWriter, you should also use it in indexSearcher.
And the scoring is not written during writing index, as it depends on the
relationship between query terms and the indexed documents. It is calculated
for each query.
2010/11/18 Mattias
2010/11/18 Samuel Feng okos...@gmail.com
Hi,
To my understanding, if you use one
Similarity in indexWriter, you should also use it in indexSearcher.
And the scoring is not written during writing index, as it depends on the
relationship between query terms and the indexed documents. It is
If you can get the above test case working using other TMs together
with Neo4j would be great!
OK, it took some time, since I messed with some things for the first time.
I have created the following:
- I have added two classes in the kernel module that provide support
for registration
of
From
http://lucene.apache.org/java/2_4_0/api/org/apache/lucene/search/Similarity.html
http://lucene.apache.org/java/2_4_0/api/org/apache/lucene/search/Similarity.htmlIf
the custom Similarity overwrite the
Allright, then there probably have to be a configuration parameter for
similarity, and maybe something in QueryContext as well (if you wouldn't use
the configuration parameter).
2010/11/18 Samuel Feng okos...@gmail.com
From
There's also a problem going with the QueryContext approach... an
IndexSearcher can be shared by multiple threads and multiple queries so
using IndexSearcher#setSimilarity can't be done on a per-query basis.
Setting a similarity in one query may also set it for another thread/query
which might not
Alex,
sounds great, don't hesitate to get back to the list with question and
suggestions!
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn http://www.linkedin.com/in/neubauer
Twitter http://twitter.com/peterneubauer
I just spent less than two hours making this change locally and everything
works and it generally feels great. Now that I've tried it out myself, this
way of controlling pruning/filtering feels more awesome. I'll post some
examples soon so that you can feedback :)
2010/11/10 Mattias Persson
Chris,
This sounds like some major progress! IMHO you should start a branch
in the SVN so others can look at the code. Having the compatibility
tests is great - there are other breaking test that Mattias and Johan
are using to purposely break recovery on both the normal server and HA
setups. They
2010/11/18 Mattias Persson matt...@neotechnology.com
I just spent less than two hours making this change locally and everything
works and it generally feels great. Now that I've tried it out myself, this
way of controlling pruning/filtering feels more awesome. I'll post some
examples soon so
Fantastic! I have yet to try the implementation out, but I'm positive that
it's an improvement. The only comment I have right now is the use of the
word SKIP. IMO it is ambiguous with respect to stopping vs excluding. I
prefer EXCLUDE. Will try it out soon. Thanks Mattias!
David
On Thu, Nov 18,
Maybe instead:
INCLUDE_AND_CONTINUE,
INCLUDE_AND_PRUNE,
EXCLUDE_AND_CONTINUE,
EXCLUDE_AND_PRUNE,
because stop sounds that the traverser is stopping, where it's really just
stopping that particular branch, i.e. prunes that branch. Or maybe even:
INCLUDE,
INCLUDE_AND_PRUNE,
EXCLUDE,
Hi,
Currently considering neo4j. We know a graph DB is the right solution long
term, but we need to get our app out fast and with minimal infrastructure
overhead.
We won't hit performance issues on SQL for at least 6 months, and we're
iterating weekly, so while that may seem close, using
21 matches
Mail list logo
