-
Notifications
You must be signed in to change notification settings - Fork 591
HTTP Part 2 #642
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
HTTP Part 2 #642
Conversation
Signed-off-by: ortyomka <[email protected]>
Signed-off-by: ortyomka <[email protected]>
Signed-off-by: ortyomka <[email protected]>
Signed-off-by: ortyomka <[email protected]>
I have problems with temp tables. They are stored within the same session, in HTTP the session is indicated by the Is it worth separating them or specifying context is ok? Example here |
Signed-off-by: ortyomka <[email protected]>
I have fixed 2 race conditions:
|
@gingerwizard need advice. Each request can read 3 000 000 rows, with shared decode. If the request will be larger, then a result will be incorrect. What better: shared decode and wait group with rows limit |
@gingerwizard, okay. Do I need to revert creation of decoder on each request? |
@ortyomka getting some failures in #646 around HTTP
This doesn't include this PR but it seems we fail on trying to read the last block with the new reader - unclear why this isn't the case on the old decoder. |
@ortyomka i think we need to set |
I will see, today |
New reader is wrapping the eof..meaning we error back on Next(). I'll fix in #646 |
@gingerwizard one moment |
Signed-off-by: ortyomka <[email protected]>
Signed-off-by: ortyomka <[email protected]>
@gingerwizard Done |
@ortyomka please resolve the conflicts now #646 was merged - should be easy but ping me if any issues. The last unresolved point is temporary tables. I think for now we can rely on the user having to specify the context if they need consistent routing. I'm going to write the new doc soon - I'll make sure to note. |
Actually leave the test flattenning, ill do as a separate PR on all tests. Just resolve conflicts @ortyomka and LGTM. |
Signed-off-by: ortyomka <[email protected]>
@gingerwizard resolved |
Merging, thanks to @ortyomka and also for the patience. |
Issue #597
Changes
cc @gingerwizard