> > [...] "node type". It could provide an unambiguous link between a node and > its indexing strategy(ies).
Hey I'll just toss out that for us, we need multiple indexing strategies for the same node! E.g. if you have a "movie", you may want to "exact" index an "alias" or "username" (a short but human-readable ID for popular movies, like "lotr2" or "hp5") while at the same-time "fulltext" index a "title" and "description" to facilitate search. Aseem On Mon, Jul 18, 2011 at 8:15 AM, Rick Bullotta <[email protected]>wrote: > Chris, I think that auto indexing is another great reason for a formal > concept of "node type". It could provide an unambiguous link between a node > and its indexing strategy(ies). > > > > ----- Reply message ----- > From: "Chris Gioran" <[email protected]> > Date: Mon, Jul 18, 2011 6:16 am > Subject: [Neo4j] Auto-index fulltext? > To: "Neo4j user discussions" <[email protected]> > > No, that is not what i meant. The main idea is to provide the means to > configure at least some aspects of the auto index instead of relying > on the default settings only. There will still be one auto index for > each primitive category. > However, one feature under consideration is to actually allow an > arbitrary number of auto indexes, each of which will allow for > individual configuration. So, when that comes along you will have what > you described (and more, actually). > > thanks, > CG > > On Mon, Jul 18, 2011 at 12:29 PM, Aseem Kishore <[email protected]> > wrote: > > Awesome to hear, Chris, thanks. Just to clarify/confirm then: in the > future, > > we will be able to have *both* an exact auto-index and a fulltext > auto-index > > side-by-side? > > > > Cheers, > > Aseem > > > > On Mon, Jul 18, 2011 at 3:18 AM, Chris Gioran < > > [email protected]> wrote: > > > >> Hi Aseem, > >> > >> On Sat, Jul 16, 2011 at 9:46 AM, Aseem Kishore <[email protected] > > > >> wrote: > >> > Is the 1.4 auto-index only "exact"? Or can it be configured to be a > >> > "fulltext" index? > >> > >> Yes, currently the auto-indexes are only exact, there is no > >> straightforward way to configure them explicitly. This is a known > >> shortcoming and will be remedied pretty soon. > >> Another addition that is coming, by the way, is the visibility of > >> changes of the auto index within the transaction, instead of waiting > >> for commit time as is now. > >> > >> > (Btw, it would be awesome if we could have two auto-indexes: one > exact, > >> one > >> > full-text. It would be great in general if all indexing could be auto. > >> Not > >> > sure when you would ever want/need manual indexing.) > >> > >> Well, a lot of use cases call for manual indexing, when for example it > >> is conditional or the use of multiple indexes is required. If, > >> however, auto indexing covers all your needs then by all means, do > >> just that. > >> > >> cheers, > >> CG > >> > >> > Aseem > >> > _______________________________________________ > >> > Neo4j mailing list > >> > [email protected] > >> > https://lists.neo4j.org/mailman/listinfo/user > >> > > >> _______________________________________________ > >> Neo4j mailing list > >> [email protected] > >> https://lists.neo4j.org/mailman/listinfo/user > >> > > _______________________________________________ > > Neo4j mailing list > > [email protected] > > https://lists.neo4j.org/mailman/listinfo/user > > > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
