You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@loripusey had this good idea: Some submitters think in terms of files, so as a convenience to them, we could accept a name for the payload they are submitting, and they could choose to pass in a filename. Then we'll send it back to them later, as part or lineage API.
Note: The API has no idea what file was used to create the payload. The API just sees bytes in the body payload, and doesn't know where it came from. hence the need for the user to send a name string separately.
Tasks:
Accept a payloadName as an additional header or query param or both.
Create a new payload_name varchar in the ACTION table, and store it there if it exists, else null.
Also create an index on this column - you could see lookups being done on this in the future.
Add this to the release notes - this is a customer facing feature.
Establish what the format for this filename is. E.g. length, allowed characters, etc. Need to make sure to sanitize this value
The text was updated successfully, but these errors were encountered:
@loripusey had this good idea: Some submitters think in terms of files, so as a convenience to them, we could accept a name for the payload they are submitting, and they could choose to pass in a filename. Then we'll send it back to them later, as part or lineage API.
Note: The API has no idea what file was used to create the payload. The API just sees bytes in the body payload, and doesn't know where it came from. hence the need for the user to send a name string separately.
Tasks:
The text was updated successfully, but these errors were encountered: