You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2011/06/19 20:49:47 UTC

[jira] [Created] (OODT-288) Make transaction update default to off

Make transaction update default to off
--------------------------------------

                 Key: OODT-288
                 URL: https://issues.apache.org/jira/browse/OODT-288
             Project: OODT
          Issue Type: New Feature
          Components: catalog
         Environment: from JPL internal JIRA
            Reporter: Brian Foster
             Fix For: 0.4


make transaction update default to off, introduce metadata key which will turn it on.

will introduce metadata key 'urn:CatalogService:EnableUpdate' which, if set to true, an ingest done with an existing TransactionId will be updated . . . otherwise ingest will kick back an exception telling the user to set the new metadata key to allow an update to existing Transaction.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (OODT-288) Make transaction update default to off

Posted by "Chris A. Mattmann (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann updated OODT-288:
-----------------------------------


- push out to 0.5
                
> Make transaction update default to off
> --------------------------------------
>
>                 Key: OODT-288
>                 URL: https://issues.apache.org/jira/browse/OODT-288
>             Project: OODT
>          Issue Type: New Feature
>          Components: catalog
>         Environment: from JPL internal JIRA
>            Reporter: Brian Foster
>             Fix For: 0.5
>
>
> make transaction update default to off, introduce metadata key which will turn it on.
> will introduce metadata key 'urn:CatalogService:EnableUpdate' which, if set to true, an ingest done with an existing TransactionId will be updated . . . otherwise ingest will kick back an exception telling the user to set the new metadata key to allow an update to existing Transaction.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (OODT-288) Make transaction update default to off

Posted by "Chris A. Mattmann (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann updated OODT-288:
-----------------------------------

    Fix Version/s:     (was: 0.4)
                   0.5

- push to 0.5
                
> Make transaction update default to off
> --------------------------------------
>
>                 Key: OODT-288
>                 URL: https://issues.apache.org/jira/browse/OODT-288
>             Project: OODT
>          Issue Type: New Feature
>          Components: catalog
>         Environment: from JPL internal JIRA
>            Reporter: Brian Foster
>             Fix For: 0.5
>
>
> make transaction update default to off, introduce metadata key which will turn it on.
> will introduce metadata key 'urn:CatalogService:EnableUpdate' which, if set to true, an ingest done with an existing TransactionId will be updated . . . otherwise ingest will kick back an exception telling the user to set the new metadata key to allow an update to existing Transaction.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira