Skip to content
This repository has been archived by the owner on Dec 22, 2020. It is now read-only.

How would i know the status of the currently imported pbix file #41

Open
hassanwasef opened this issue Jan 23, 2017 · 3 comments
Open

Comments

@hassanwasef
Copy link

I have imported a .PBIX file on an azure work space. and it seems to be taking a while to complete, but it seemed to be taking a forever. so i would like to know whether there is a problem with the importing process or the process is still in progress..
is there a command to view that status? Thank you

@ali-hamud
Copy link
Contributor

Why do you need this?
if import doesn't continue it means that there is a bug we need to fix.
what you are trying to do?

here is an example of successful import:

> powerbi import -c Al..ction -w 7b80b..55 -k UtCsCafxQXacuda..cF62Lg== -f C:\Po..metry.pbix -n name1
[ powerbi ] Importing C:\Power..emetry.pbix to workspace: 7b80b..55
[ powerbi ] File uploaded successfully
[ powerbi ] Import ID: 0d3...0ac59
[ powerbi ] Checking import state: Succeeded
[ powerbi ] Import succeeded

@marjorienorm
Copy link

marjorienorm commented Jun 12, 2017

I'm having the same issue with a long import time. I do see
[ powerbi ] Importing C:\PowerBI_Data\somefile.pbix to workspace: d8d3...5

then after a very long time I get
[ powerbi ] read ECONNRESET

At a minimum it would be nice to get some ASCII progress bar as the upload is going. But yes, the underlining issues must be fixed first. My pbix is ~330MB in size.

@ali-hamud
Copy link
Contributor

Hi @marjorienorm ,

Importing a large file could fail because of a request redirecting.
That means, if you import a file using cli (which uses Power BI API), the request will arrive to the closest Power BI Cluster, and then the request will be redirected to the correct cluster which can handle the request.
To avoid that, you need to use a flag called PreferClientRouting (we don't have a support to it in cli)
https://msdn.microsoft.com/en-us/library/azure/mt711504.aspx

using this flag, if the request arrives to a wrong cluster, the request will not be redirected. the request will return the name of the good cluster to use in Location header. you can use the location header to call the right cluster directly which will succeed.

Tell me if it works for you.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants