Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Incompletely defined storage classes cause butler query failure

Description

The following `query-dataset-types` query currently fails as seen below, due to some experimental storage classes that are apparently not completely defined. This failure mode should be caught and reported without causing an exception. Furthermore, we should probably remove the dataset-type(s) that cause this particular failure.
 

Checklist

Issue Matrix

hide

Lucidchart Diagrams

Activity

Nate Pease [X] June 13, 2022 at 5:06 PM

looks good to me

 

Tim Jenness June 10, 2022 at 9:15 PM

can you please take a look at this? It's a very small review.

Tim Jenness April 14, 2022 at 10:15 PM

We could likely turn that into a more explicit for loop where we catch failures, but I think it might be best to add a DatasetType.storageClass_name public property and use that instead. The problem is that dataset types are defined with storage class names and we load the storage class on demand. In this particular example we obviously only care about the name and not the actual storage class so getting the name from the DatasetType is fine (and also much much faster than instantiating a StorageClass every row).

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Reviewers

Nate Pease [X]

Story Points

RubinTeam

Architecture

Components

Checklist

Created April 14, 2022 at 10:06 PM
Updated June 13, 2022 at 11:04 PM
Resolved June 13, 2022 at 11:04 PM