Story #5142

[DRAFT] [API] Enrich supported dataclass values for pipeline templates

Added by Brett Smith about 4 years ago. Updated 11 days ago.

Status:
Rejected
Priority:
Normal
Assigned To:
-
Category:
API
Target version:
Start date:
02/05/2015
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

<tomclegg> tetron: is this an opportunity to "do whatever cwl does"?
<tetron> unfortunately I don't have a good answer, the current CWL spec is based on json schema, but the next draft is going to use arvo which has a different type system
<tetron> the minimum to do here is at least distinguish between floats and integers
<tetron> tomclegg: a quick glance at json schema suggests that it doesn't even go that far
<tetron> tomclegg: avro has int/long/float/double for 32/64 bit integers and floats respectively
<tetron> tomclegg: so, I would say use 64 bit types, but we can call them whatever
<tomclegg> yeah. the names 'long' and 'double' seem much less obvious/friendly than 'int' and 'float'. I think Go's approach is pretty good: if anyone actually wants to specify #bits, they might as well come right out and say int64, instead of "double what?"

History

#1 Updated by Brett Smith about 4 years ago

  • Subject changed from [DRAFT] [API] Enrich support dataclass values for pipeline templates to [DRAFT] [API] Enrich supported dataclass values for pipeline templates

#2 Updated by Tom Morris 11 days ago

  • Status changed from New to Rejected

PIpeline templates are gone

Also available in: Atom PDF