-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stand alone indexed properties #67
Comments
Hello
Yes you need be very careful when sharing indexes. I have mentioned this before and I've now added a warning to the docs. I definitely want to add support for full text indexes, it's a feature I shall be using soon. As for indexes per property, I do want to add support for this however the issue is knowing what class to inflate the returned node(s) to. neo4j 2.0 adds labels which I believe will make this possible. |
Hi Robin and everyone ! I been working on this feature, before any pull request y would like you to check it out and make some recomendations if is the case. Please check the last 3 commits https://github.com/neoecos/neomodel/commits/feature_indexed_proerties |
In neo4j 2 the old index system has been deprecated.. This means in order to index a property the best way is to create a label with an index on that said property. This can be achieved in the new neo4j branch by creating an inheritance hierarchy. # index name properties on nodes with the label :Names
class Names(StructuredNode):
name = StringProperty(unique_index=True)
# Names.index.get(name="") returns nodes saved as a 'Person' object
class Person(Names):
age = IntegerProperty() HTH |
Hi,
With a recent update, i was able to share index on subclasses, and it helped in order to find any node type using just one index and just one property (uuid).
Today, i noticed this approach outcome with some ussues, like having indexed a property with the same name on different classes, and worst if is a unique_index.
Also I'll should be to be able to do a text search on other properties of some classes, looking for indexing information, i found there are other types of index on lucene, specific there is a fulltext type of index for search for text within fields of the node.
Now, i think a possible solution for this could be standalone indexes for properties, so is possible to share and index for a common property, and use specific type of index for same kind of properties.
Probably i will be able to work on this feature within the end of this month, and would be useful your comments and ideas.
So, now i'm thin
The text was updated successfully, but these errors were encountered: