[DM-21840] Disallow NULL/None for implied dimension values in data IDs - Jira

XML

Word

Printable

Details

Type: Story
Status: In Progress
Resolution: Unresolved
Fix Version/s: None
Component/s: daf_butler
Labels:
- gen3-middleware
- gen3-registry-incompatibility

Story Points:
2
Epic Link:
s23a-drp-emergent
Team:
Data Release Production
Urgent?:
No

Description

The Gen3 Registry's implied dimension dependencies (e.g. visit.physical_filter, exposure.visit) are allowed to be None, which translates nicely to NULL in SQL. Unfortunately SQL NULLs and Python Nones compare differently, and we want the latter behavior in SQL queries. That means we need to either

add special NULL-handling logic to the query-generation code
do our own mapping from Python None to sentinal values in all fetch/insert code
drop support for None/NULL in implied dimensions and make the associated foreign key columns in the database NOT NULL to support this.

Attachments

Issue Links

relates to

DM-34616 Avoid NULL/None for implied dimensions in test data IDs

Done

DM-21832 lsst.obs.base.FilterDefinition should raise if abstract_filter is not set

To Do

DM-21836 Add OBSTYPE/purpose to Gen3 Registry exposure table

Done

DM-33942 Northern Spring 2022 Butler schema migration

Done

Activity

No work has yet been logged on this issue.

People

Assignee:: Jim Bosch

Reporter:: Jim Bosch

Watchers:: Christopher Waters, Jim Bosch, John Parejko, Tim Jenness

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 21/Oct/19 5:39 PM

Updated:: 05/Jan/23 1:29 AM

Jenkins

No builds found.

Data Management