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

perf: Using an iterator instead of going through all the data #150

Merged

Conversation

giomerlin
Copy link
Contributor

@davidrabinowitz Comparing the version 0.9.2-beta with the current one I realized that it was pretty slow when doing limit or show operations. It was due the introduction of the ReadRowsHelper in the version 0.10.0-beta which was iterating over all the results before returning the final iterator, so I wrapped the results in a new iterator, achieving the same retry functionality

@davidrabinowitz
Copy link
Member

Thanks @giomerlin for this PR! This task was on my to-do list for 0.15... Can you please revert the changes to build.sbt?

@davidrabinowitz
Copy link
Member

/gcbrun

@giomerlin
Copy link
Contributor Author

@davidrabinowitz I didn't realize I pushed the sbt changes, I've just reverted them

@davidrabinowitz
Copy link
Member

Have you made changes to ReadRowsSuite.scala? Unfortunately it fails now.

@giomerlin
Copy link
Contributor Author

@davidrabinowitz I just pushed the changes to the test, forgot to run the test after I made the scope change to the fetchResponses method, It should run now

@davidrabinowitz davidrabinowitz merged commit a1536d3 into GoogleCloudDataproc:master Apr 8, 2020
@davidrabinowitz
Copy link
Member

/gcbrun

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

Successfully merging this pull request may close these issues.

None yet

2 participants