[jira] [Updated] (OAK-3679) Rollback to timestamp

2017-01-17 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/OAK-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Dürig updated OAK-3679:
---
Fix Version/s: 1.8

> Rollback to timestamp
> -
>
> Key: OAK-3679
> URL: https://issues.apache.org/jira/browse/OAK-3679
> Project: Jackrabbit Oak
>  Issue Type: New Feature
>  Components: core, documentmk, segment-tar
>Reporter: Thomas Mueller
>  Labels: operations, tooling
> Fix For: 1.8
>
>
> We should have a feature to roll back to a certain point in time. The use 
> case are: 
> * undo a failed, large operation (for example upgrade, migration, installing 
> a package),
> * on a copy of the repository, switch to an old state for reading old content
> * recover from a corruption (for example corruption due to incorrect 
> "discovery" state, such as concurrent async index updates).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OAK-3679) Rollback to timestamp

2016-12-22 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/OAK-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Dürig updated OAK-3679:
---
Labels: operations tooling  (was: tooling)

> Rollback to timestamp
> -
>
> Key: OAK-3679
> URL: https://issues.apache.org/jira/browse/OAK-3679
> Project: Jackrabbit Oak
>  Issue Type: New Feature
>  Components: core, documentmk, segment-tar
>Reporter: Thomas Mueller
>  Labels: operations, tooling
>
> We should have a feature to roll back to a certain point in time. The use 
> case are: 
> * undo a failed, large operation (for example upgrade, migration, installing 
> a package),
> * on a copy of the repository, switch to an old state for reading old content
> * recover from a corruption (for example corruption due to incorrect 
> "discovery" state, such as concurrent async index updates).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OAK-3679) Rollback to timestamp

2016-11-09 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/OAK-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Dürig updated OAK-3679:
---
Labels: tooling  (was: )

> Rollback to timestamp
> -
>
> Key: OAK-3679
> URL: https://issues.apache.org/jira/browse/OAK-3679
> Project: Jackrabbit Oak
>  Issue Type: New Feature
>  Components: core, documentmk, segment-tar
>Reporter: Thomas Mueller
>  Labels: tooling
>
> We should have a feature to roll back to a certain point in time. The use 
> case are: 
> * undo a failed, large operation (for example upgrade, migration, installing 
> a package),
> * on a copy of the repository, switch to an old state for reading old content
> * recover from a corruption (for example corruption due to incorrect 
> "discovery" state, such as concurrent async index updates).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OAK-3679) Rollback to timestamp

2016-04-20 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/OAK-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Dürig updated OAK-3679:
---
Component/s: (was: segmentmk)
 segment-next

> Rollback to timestamp
> -
>
> Key: OAK-3679
> URL: https://issues.apache.org/jira/browse/OAK-3679
> Project: Jackrabbit Oak
>  Issue Type: New Feature
>  Components: core, documentmk, segment-next
>Reporter: Thomas Mueller
>
> We should have a feature to roll back to a certain point in time. The use 
> case are: 
> * undo a failed, large operation (for example upgrade, migration, installing 
> a package),
> * on a copy of the repository, switch to an old state for reading old content
> * recover from a corruption (for example corruption due to incorrect 
> "discovery" state, such as concurrent async index updates).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)