Recent testing of publishing a new version of an existing dataset fails at PCMDI. This dataset had been published prior to the versioning upgrade. It appears the cause is a null LogicalFile "versionIdentifier" which should be corrected. (See: AddOrUpdateFileVersionProducer:186)

Original email bug report follows:

I did some further testing on the new gateway version, to try to publish a new dataset / version. Here's what happened:

(1) Republished an existing dataset/version: pcmdi.ipcc4.CNRM.cnrm_cm3.amip.3hourly.atm.run1, version=1

The catalog had fewer variables than on the gateway. The publication appeared to succeed, however the new catalog was not reflected on the gateway. In other words, nothing happened. I would have expected to either get an error (dataset version exists) or see the most recently published catalog.

(2) Republished the same dataset with version=2. This time an exception occurred:

WARNING 2010-02-25 15:03:44,305 Publication failed for dataset pcmdi.ipcc4.CNRM.cnrm_cm3.amip.3hourly.atm.run1 with message: Publishing operation description. THREDDS catalog: http://pcmdi3.llnl.gov/thredds/esgcet/11/pcmdi.ipcc4.CNRM.cnrm_cm3.amip.3hourly.atm.run1.v2.xml
       Parent: CM3 Model Output
       Overwrite mode: ALWAYS_UPDATE
Completed.

Publishing task description. THREDDS catalog: http://pcmdi3.llnl.gov/thredds/esgcet/11/pcmdi.ipcc4.CNRM.cnrm_cm3.amip.3hourly.atm.run1.v2.xml
       Parent: CM3 Model Output
       Overwrite mode: ALWAYS_UPDATE
java.lang.NullPointerException
       at eske.metadata.harvest.thredds.AddOrUpdateFileVersionProducer.findLogicalFile(Unknown Source)
...

How difficult would it be to provide an SQL script that completely deletes a dataset (hard delete)?

Bob