Hi Tim

Congratulations to you and the DB team on successfully implementing the first big change in the DB schema and data set for many years :)

On 06/05/2015 17:26, Tim Bruijnzeels wrote:
Dear colleagues

The new attributes "created:" and "last-modified:" have now been enabled in output.

However, we found a minor bug regarding no-op changes, that was not noticed in development or the RC environment.

If an object is submitted without any changes it will always result in an update, because when we compare the object the "last-modified:" value will typically not match.(unless the update is done at sub-second speed) In other words what should be a "no-op" now results in a "touch" operation where only the "last-modified:" attribute is changed.

Just an observation. This might actually be a useful side effect. It allows maintainers of objects to 'touch' their objects and show they are alive and actively maintaining their data even when nothing needs to change. I am sure some people in the community who are going to start monitoring "last-changed:" attributes to argue that data is out of date would appreciate that, or even request it.

cheers
denis


While this is unfortunate we do not believe that this bug is severe enough to disable the new attributes. Instead, we are working on a fix for this and plan to deploy this, after thorough testing, as 1.79.2 at the end of the week. We will also work on a retro-active fix to the history of objects to remove those revisions of an object, where only "last-modified:" was updated.


Kind regards,

Tim Bruijnzeels

Assistant Manager Software Engineering
RIPE NCC





On 04 May 2015, at 21:54, Tim Bruijnzeels <tim@ripe.net> wrote:

Dear colleagues,

The batch job to add the "created:" and "last-modified:" to all objects took longer to complete than we anticipated (due to the higher rate of updates in the production environment). The job was completed late afternoon today, but since tomorrow is a public holiday in Amsterdam we thought it better to postpone switching on the new attributes in output until this Wednesday to make sure we have all engineers on board when we do this.

Kind regards,

Tim Bruijnzeels

Assistant Manager Software Engineering
RIPE NCC


On 28 Apr 2015, at 15:54, Tim Bruijnzeels <tim@ripe.net> wrote:

Dear working group,

On 22 Apr 2015, at 11:07, Tim Bruijnzeels <tim@ripe.net> wrote:
Because no major changes were introduced with these fixes we plan to adhere to the original planning and deploy the 1.79.1 release of whois to the production environment on Tuesday 28 April (Monday is a public holiday here), and we plan to enable the new attributes in the output on Monday 4 May.

We have deployed 1.79.1 to production today.

We are currently running the updates to generate the values for 'last-modified:' and 'created:' in the background and plan to enable these new attributes in output Monday 4 May - because the background job needs some time to complete, and we prefer not make changes like this too close to the weekend.

Kind regards,

Tim Bruijnzeels

Assistant Manager Software Engineering
RIPE NCC