-
Updated
Jul 19, 2021 - Go
data-versioning
Here are 18 public repositories matching this topic...
Currently lakeFS register openapi handlers and handle all specific routes.
In case of a call to /api/v1/test
, the unknown path under the API prefix, the mux will serve the request by the UI handler and return a valid HTML (UI) page.
The expected behaviour is to return a non-2xx status code with JSON error - prefered the internal error format, so the developer will handle an error and not fai
-
Updated
Jul 18, 2021 - Jupyter Notebook
-
Updated
Jun 20, 2021 - JavaScript
-
Updated
Jul 3, 2019
While API action names have been renamed to refer to tag
, there are some cases where parameter names and returned struct keys still refer to version
.
Examples:
- in
resource_show_tag
:version_id
parameter,version_metadata
in the returned dict - Same in
package_show_tag
-
Updated
Jan 6, 2021
-
Updated
Jun 16, 2021 - Jupyter Notebook
-
Updated
Jul 17, 2021 - Go
-
Updated
Jun 30, 2021 - Java
-
Updated
Apr 22, 2021 - HTML
-
Updated
Mar 22, 2020 - TypeScript
-
Updated
Jun 1, 2021 - Java
-
Updated
Jul 5, 2021 - JavaScript
-
Updated
Feb 12, 2020
Improve this page
Add a description, image, and links to the data-versioning topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the data-versioning topic, visit your repo's landing page and select "manage topics."
Description
We're running usability tests and would love for you to record walking through our tutorials. The idea for this ticket is that you do a screen capture walking through one of more of the following examples: