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
Describe the bug azureblob type conection requires in URI relative path of container to the resource.
connections which follow on the screenshots:
with wine connection as a data connection, the training succeded, but with either wine-azure-full-uri, wine-azure or wine-azure-1, the training failed. the only change for training is the data connection.
The text was updated successfully, but these errors were encountered:
BPylypenko
added
bug
Something isn't working
major
without one user can perform the target action in a workaround, but it's not obvious
1.3
labels
Sep 18, 2020
BPylypenko
changed the title
azureblob type of connection doesn't work without webUILink
azureblob type of connection needs only relative path of container in uri
Sep 18, 2020
Possible options:
- full uri like "https://storage-account-name.windows.net/blob-container-name/path/to/file"
- path like "/blob-container-name/path/to/file"
- path without leading slash like "blob-container-name/path/to/file"
Before only the last option worked.
Co-authored-by: Innokentii Min <innokentii_min@epam.com>
Possible options:
- full uri like "https://storage-account-name.windows.net/blob-container-name/path/to/file"
- path like "/blob-container-name/path/to/file"
- path without leading slash like "blob-container-name/path/to/file"
Before only the last option worked.
Co-authored-by: Innokentii Min <innokentii_min@epam.com>
Describe the bug
azureblob
type conection requires inURI
relative path of container to the resource.connections which follow on the screenshots:
with
wine
connection as a data connection, the training succeded, but with eitherwine-azure-full-uri
,wine-azure
orwine-azure-1
, the training failed. the only change for training is the data connection.Screenshots
training logs
wine-azure-check.log.txt
wine-azure-1-check.log.txt
The text was updated successfully, but these errors were encountered: