apple
A solution is needed when max_allowed_instances is exceeded.
apm@… originally submitted this as ticket:319
With the ability to create events longer into the future the possibility that a user will create an event with more than "max_allowed_instances" (currently 1000) increases.
From instance.py:
The maximum number of instances we will ezpand out to. # Raise a TooManyInstancesError exception if we exceed this. max_allowed_instances = 1000
... which will make events disappear from instance 1000 or not get created at all if you place the mother event sufficiently far back in the past. If - say - your default_future_expansion_duration is 2 years, you currently cannot create a daily recurring event with a motherevent before ~ april 2008. Or if you create a daily recurring event today, it will no longer work after 1000 days.
I see no good solution to this without some mechanism for the user to clean up old calendars, so the don't unnecessarily contain - say - 5 year old daily events.
@wsanchez originally submitted this as comment:1:ticket:319
- Owner changed from @wsanchez to @cyrusdaboo
- Priority changed from 5: Not set to 2: Expected
- Milestone set to CalendarServer-2.x
@wsanchez originally submitted this as comment:2:ticket:319
- Milestone changed from CalendarServer-2.x to CalendarServer-3.x
@wsanchez originally submitted this as comment:7:ticket:319
- Milestone changed from CalendarServer-3.x to CalendarServer-5.x
@wsanchez originally submitted this as comment:8:ticket:319
The limit is still there, defaults to 3000, but is configurable via the plist.
@wsanchez originally submitted this as comment:9:ticket:319
- Milestone changed from CalendarServer-5.x to Later