What would be the consequence of running a background thread that iterated through all nodes and relationships, and if any had a short string property, it would re-save the property? I assume the properties store would get a lot of empty space in the beginning, or would old-id reuse kick in and prevent this?
It seems like something can can be done at application level easily enough. And if only some fraction of your properties are really short strings, this should be more efficient than copying the entire database. On Thu, Mar 3, 2011 at 11:52 AM, Tobias Ivarsson < [email protected]> wrote: > No there is no simpler way, yet. We've been thinking about creating a > "short > string compression tool" for accomplishing this, but haven't done so yet. > > Cheers, > Tobias > > On Thu, Mar 3, 2011 at 11:35 AM, Balazs E. Pataki <[email protected] > >wrote: > > > Hi, > > > > I have a big database based on Neo4J 1.2. Now, if I would like to use > > the "short strings" feature of Neo4j 1.3 M03 I should regenerate my full > > database, that is all strings should be reset so that it may or may not > > be stored according to the new "short strings" policy. > > > > It seems to me that the easiest way to do this would be to somehow be > > able to copy the full 1.2 database to a newly created 1.3 M03 database > > by traversing the 1.2 database. But there maybe a simpler (neo4j > > builtin) way to do this. Any hints about this? > > > > Thanks, > > --- > > balazs > > _______________________________________________ > > Neo4j mailing list > > [email protected] > > https://lists.neo4j.org/mailman/listinfo/user > > > > > > -- > Tobias Ivarsson <[email protected]> > Hacker, Neo Technology > www.neotechnology.com > Cellphone: +46 706 534857 > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
