#836 SysDB commands that save lastUpdate and dataExpireTimestamp should allow this value to be passed in
Closed: Fixed None Opened 8 years ago by sgallagh.

It can complicate the LDB index processing if the lastUpdate values for a large update (such as group memberships) takes more than one second to run.

We should instead set the lastUpdate time when we start the transaction and use the same time value for all elements within that transaction.


Fields changed

summary: SysDB commands that save lastUpdate should allow this value to be passed in => SysDB commands that save lastUpdate and dataExpireTimestamp should allow this value to be passed in

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.7.0

Fields changed

milestone: SSSD 1.8.0 => SSSD 1.7.0
patch: => 0

Fields changed

owner: sgallagh => pbrezina
rhbz: =>

Fields changed

patch: 0 => 1

Fields changed

status: new => assigned

Master: 684d1b4

resolution: => fixed
status: assigned => closed

Fields changed

rhbz: => 0

Metadata Update from @sgallagh:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD 1.7.0

2 years ago

Login to comment on this ticket.

Metadata