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

Memory consumption #35

Open
RaniRaven opened this issue May 4, 2017 · 0 comments
Open

Memory consumption #35

RaniRaven opened this issue May 4, 2017 · 0 comments

Comments

@RaniRaven
Copy link

Hi,

It seems like there is an issue of memory while doing a select from index (type) without where clause filter, or limit.
lets say we have index/type - foo/bar, and we write the statement "select * from bar",
If the index is large enough, the driver will explode with memory, no matter what fetch.size is set to.
Is there any way to limit this ? Doesn't the fetch.size parameter supposed to stop it from growing that much ?

BTW, this should be very easy to reproduce, even on the twitter example.
(Of course, as the number of fields returning is larger, this issue will be more "burning")

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

1 participant