Sure thing!
and your original problem (.toString()) is now fixed as per your suggestion.
Best,
Mattias
2011/6/29 Balazs E. Pataki
> OK, I will then try use this as a "feature". We will always have the
> source to hack it back in case these "_e" fields go away in the future. :-)
> ---
> balazs
OK, I will then try use this as a "feature". We will always have the
source to hack it back in case these "_e" fields go away in the future. :-)
---
balazs
On 6/29/11 10:22 AM, Mattias Persson wrote:
> Reading the source is always a good thing :)
>
> I don't see them changing in the near future,
Reading the source is always a good thing :)
I don't see them changing in the near future, and even if it's a bit of a
hack to use them (since they are there mostly to be able to remove stuff)
I've used them also in at least one scenario. I think you can give it a go,
but it's not an "official" fe
Great, thank you!
Another thing I just found in IndexType: for a fulltext index each field
is stored as fulltext (tokenized into terms) and there's also an "exact"
field (the same index postfixed with "_e"). I think this feature is not
documented officially, so my question is, whether we can co
Wow, thank you for finding that. Well done!
I'll fix it and if it doesn't break anything else then I'll commit it.
Best,
Mattias
Den tisdagen den 28:e juni 2011 skrev Balazs E. Pataki:
> Hi Mattias,
>
> Thanks for the tip!
>
> I started to look around and I think I found something. When "fulltex
Hi Mattias,
Thanks for the tip!
I started to look around and I think I found something. When "fulltext"
type index is created its type will be CustomType (subclass of IndexType
- IndexType is used for "exact" indexes) in neo4j. CustomType overrides
the addToDocument() of IndexType method, whic
Hi Balazs,
I think the issue could be in lucene, with the mix of the
white-space-tokenizing-analyzer and numeric values. I don't know. What I see
in neo4j is that it treats the values the exact same way, the queries to the
index is exactly the same, but it just doesn't return any values. I think
t
Hi,
I'm playing around with indexing and numeric range queries according to
this documentation:
http://docs.neo4j.org/chunked/snapshot/indexing-lucene-extras.html
According to my tests numeric range queries
(QueryContext.numericRange()) only have effect when "exact" type index
is used.
I
8 matches
Mail list logo
