Mattias,
I just listed one of the use cases, I have ample types of relationships in
my database.
I will be connecting all the 50k users to certain common nodes that will
depict something about the users. Example: A user node can be
directly/indirectly related to a "place" node that will depict the
You say that you will store mostly strings and that you only have one
relationship type. Feels to me that you're trying to treat neo4j as nothing
more than a bucket for tossing in your data and using lucene to search and
retrieve everything. What's the real use case you're having? If you
elaborate/
Peter,
The project requires quick retrieval of data bases upon certain parameters,
which, without indexing, would not be feasible (as the relations that hold
the data are all same, so simple traversals won't work). As I said earlier,
I would have to extract data based upon combination of some param
Aman,
I think to start with, you probably want to set up indexing on only
the interesting aspects of your CMS and documents, not everything.
Normally, that leads to a much slimmer storage, and better speed in
mutating operations.
Given 50K users, the question is how much index-relevant content the
I've been working on a project (a CMS) that would require a lot of indexing
as it would manage user generated content (mostly strings). Could I get some
suggestions on what is the extent of indexing that can be useful in a
typical CMS which could have a fair use by about 5 people? And how does
5 matches
Mail list logo
