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
The Data Explorer component in Onyxia currently does not support accessing parquet data from URLs that do not have the .parquet file extension. This limitation hinders the ability to fetch and explore parquet data provided by APIs, which often do not include file extensions in their URLs.
Problem:
When attempting to access parquet data from URLs provided by APIs, such as the example below, the Data Explorer fails to process the data correctly:
Attempt to load parquet data from the example URL above.
Observe that the Data Explorer fails to load the data.
Expected Behavior:
The Data Explorer should correctly handle URLs pointing to parquet data regardless of whether they include a .parquet file extension.
Additional Context:
This feature is essential for working with data APIs that dynamically generate and serve parquet files without including the .parquet extension in the URL.
The text was updated successfully, but these errors were encountered:
Description:
The Data Explorer component in Onyxia currently does not support accessing parquet data from URLs that do not have the .parquet file extension. This limitation hinders the ability to fetch and explore parquet data provided by APIs, which often do not include file extensions in their URLs.
Problem:
When attempting to access parquet data from URLs provided by APIs, such as the example below, the Data Explorer fails to process the data correctly:
Example URL:
Steps to Reproduce:
Expected Behavior:
The Data Explorer should correctly handle URLs pointing to parquet data regardless of whether they include a .parquet file extension.
Additional Context:
This feature is essential for working with data APIs that dynamically generate and serve parquet files without including the .parquet extension in the URL.
The text was updated successfully, but these errors were encountered: