Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Silent failing #3

Open
danpaulsmith opened this issue Jun 4, 2019 · 6 comments
Open

Silent failing #3

danpaulsmith opened this issue Jun 4, 2019 · 6 comments

Comments

@danpaulsmith
Copy link

danpaulsmith commented Jun 4, 2019

Hi,

I'm feeding in a REST endpoint that returns 2.3MB of JSON.

The connector hangs for about 30 seconds while still on the form and then un-hangs and nothing happens with no error message.

Another endpoint from the same endpoint, returning the same formatted JSON, but a much smaller response (2kb), works.

Is there anyway to debug/understand what's failing? Is there a timeout or size limit for the endpoint that's failing?

Thanks

@danpaulsmith danpaulsmith changed the title Silent failing on JSON endpoints Silent failing Jun 4, 2019
@niranjan94
Copy link
Owner

@danpaulsmith thanks for the bug report. Will check this out.

@quack3d
Copy link

quack3d commented Oct 31, 2019

Same issue here. It also fails in Internet Explorer but works fine in Chrome. Old web browser in Tableau perhaps?

@niranjan94
Copy link
Owner

@sepodele yes. IE does not handle large amounts of data and fails.

@quack3d
Copy link

quack3d commented Nov 4, 2019

No workaround to make it work in Tableau?

@kadamkajal11
Copy link

Hi.. Thanks for this amazing WDC. It helped me so much but now I am stuck with the same issue. It is not able to handle large amount of Data. Can you please let us know if there is a solution or workaround for this?

Thank you

@niranjan94
Copy link
Owner

The limitation is at the client side. Since all of the data manipulation happens in the browser. One thing I could consider doing is turning off the data preview in the Export Data dialog for large amounts of data. That should help a bit. But not a lot.

Significant improvements will be possible only when some refactor is done on the data fetching logic. This would be anyway needed for #26 . So, hopefully with that is resolved, there should also be improvements in performance.

I will keep this issue open until them.

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

No branches or pull requests

4 participants