Correct. Just wanted peace of mind if we keep the database clean on the app side, we could have unlimited RIDs.
So if hundreds of thousands of RIDs are deleted on a regular basis, those RIDs are not gone for good. They would be reused sometime in the future. The longer the period between reuse, the better. This would also relieve the concerns of those who may not want the confusion of immediate reuse. On Jan 27, 2014 9:06 AM, "Andrey Lomakin" <[email protected]> wrote: > So as I can see it the problem is not rid reuse but space reuse, does not > it ? > > > On Mon, Jan 27, 2014 at 3:54 PM, Giraldo Rosales <[email protected]>wrote: > >> That would be a great solution. Or even if it's an eventual reuse. Where >> if and when the RIDs run out (I am aware the limit is far beyond >> trillions), the database will start from 0 again and reuse any unused RIDs. >> >> Andrey, >> The fact that local will be deprecated helps in choosing the right option >> between the two. Thanks. >> On Jan 27, 2014 8:24 AM, "Sylvain Spinelli" <[email protected]> >> wrote: >> >>> For a customer, I have a use case where more than 50000 records are >>> deleted and re-created every night by batch. Not reuse RID can be a problem >>> here. >>> >>> Ideally I think we should have a customizable interface "RidFactory" >>> with 3 default implementations : "never reuse", "reuse immediately", "reuse >>> later" (means reuse after a reasonable delay, 1 day for example). >>> >>> My 2 cents contribution ;) >>> >>> >>> Sylvain >>> >>> >>> Le 27/01/2014 13:14, Giraldo Rosales a écrit : >>> >>> Ah. Ok. Saw your concerns. Will trust them. >>> >>> I was thinking of something less durable like "votes" or "likes" in a >>> database. Let's say you get a couple thousand votes and then start a new >>> poll. That old, deleted, poll is just wasted RIDs. >>> On Jan 27, 2014 7:09 AM, "Andrey Lomakin" <[email protected]> >>> wrote: >>> >>>> Giraldo, >>>> It is controversial issues, there are doubts that rid reuse will reduce >>>> ability to scale database also local storage will be deprecated soon. >>>> >>>> What is your problem with RID reuse ? >>>> >>>> >>>> >>>> On Mon, Jan 27, 2014 at 1:45 PM, Giraldo Rosales <[email protected]>wrote: >>>> >>>>> Yes. I read this. Great documentation on plocal storage but what >>>>> about local storage? Does it handle deletions in the same way? I couldn't >>>>> find documentation on local deletions. >>>>> >>>>> I also saw a request in this discussion about adding a setting to >>>>> plocal to reuse RIDs. Was not sure if that request was implemented. I >>>>> know, >>>>> as of the latest build, local reuses and plocal doesn't. I was interested >>>>> in reusing RIDs in plocal. >>>>> >>>>> Thanks! >>>>> On Jan 27, 2014 5:01 AM, "Andrey Lomakin" <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi Giraldo, >>>>>> Could you take a look here >>>>>> https://github.com/orientechnologies/orientdb/wiki/plocal-storage-components#wiki-cluster >>>>>> >>>>>> >>>>>> >>>>>> On Mon, Jan 27, 2014 at 8:27 AM, Giraldo Rosales >>>>>> <[email protected]>wrote: >>>>>> >>>>>>> Has there been an official update to the reuse issue in plocal? Is >>>>>>> there a setting to reuse an RID in plocal without storing the deleted >>>>>>> records permanently? Also does local store in this way? Reusing RIDs but >>>>>>> storing the deleted records permanently? Or does local reuse RIDs and >>>>>>> keep >>>>>>> clean by removing deleted records? >>>>>>> >>>>>>> Thanks! >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> --- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "OrientDB" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to [email protected]. >>>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Best regards, >>>>>> Andrey Lomakin. >>>>>> >>>>>> Orient Technologies >>>>>> the Company behind OrientDB >>>>>> >>>>>> -- >>>>>> >>>>>> --- >>>>>> You received this message because you are subscribed to a topic in >>>>>> the Google Groups "OrientDB" group. >>>>>> To unsubscribe from this topic, visit >>>>>> https://groups.google.com/d/topic/orient-database/wXs6HoaiQkY/unsubscribe >>>>>> . >>>>>> To unsubscribe from this group and all its topics, send an email to >>>>>> [email protected]. >>>>>> >>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>> >>>>> -- >>>>> >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "OrientDB" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>> >>>> >>>> >>>> -- >>>> Best regards, >>>> Andrey Lomakin. >>>> >>>> Orient Technologies >>>> the Company behind OrientDB >>>> >>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "OrientDB" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/orient-database/wXs6HoaiQkY/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "OrientDB" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "OrientDB" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/orient-database/wXs6HoaiQkY/unsubscribe >>> . >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "OrientDB" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Best regards, > Andrey Lomakin. > > Orient Technologies > the Company behind OrientDB > > -- > > --- > You received this message because you are subscribed to a topic in the > Google Groups "OrientDB" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/orient-database/wXs6HoaiQkY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
