Skip to content
This repository was archived by the owner on Jul 3, 2023. It is now read-only.

Add check next_uri because presto 0.153 may have no data but have data in next_uri#55

Closed
wyukawa wants to merge 1 commit intotreasure-data:masterfrom
wyukawa:next_url
Closed

Add check next_uri because presto 0.153 may have no data but have data in next_uri#55
wyukawa wants to merge 1 commit intotreasure-data:masterfrom
wyukawa:next_url

Conversation

@wyukawa
Copy link
Contributor

@wyukawa wyukawa commented Oct 19, 2016

In my environment, I use pentaho and access presto through prestogres.

In presto 0.153, presto 0.154, there is a case without data but has next_uri.

for example,

http://.../1
there is data
http://.../2
there is data
http://.../3
there is no data
http://.../4
there is data
...

In this case, prestogres seems to cancel http://.../4 wrongly.

I check https://github.com/prestodb/presto/wiki/HTTP-Protocol

So I think that prestogres should check next_uri.

Thanks

@wontonst
Copy link

This PR already exists. #52

@wontonst
Copy link

Can we please get my PR merged in so others aren't wasting their time? This is a clear bug.

@teamsoo
Copy link

teamsoo commented Oct 21, 2016

@wontonst I think this project is not maintained anymore. no one will come and merge your PR.
People’d just use the Teradata’s Presto ODBC driver

@wontonst
Copy link

Literally was on the phone with these guys a few months back and they said
they'd merge in changes :/

On Thu, Oct 20, 2016 at 8:18 PM, Phakin Cheangkrachange <
notifications@github.com> wrote:

@wontonst https://github.com/wontonst I think this project is not
maintained anymore. no one will come and merge your PR.
People’d just use the Teradata’s Presto ODBC driver


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#55 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB773DVDmwbrMgq0aPJO3_zvqXP16OHnks5q2C72gaJpZM4Kaz64
.

@wyukawa wyukawa closed this Apr 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants