I think I see the problem. We're getting connection close messages in relationship to all our queries run on a connection at close time (after queries have completed successfully) and we're using PrintingResultsListener, that simply print results for success and failure. Working on a patch.
I don't believe this should be failing any unit tests. Please confirm or share a test that is now failing. On Sat, May 9, 2015 at 10:32 AM, Jacques Nadeau <[email protected]> wrote: > I ran full suite before but I just saw some of these as well. Are you > seeing failures or simply messages like this? > On May 9, 2015 10:30 AM, "Sudheesh Katkam" <[email protected]> wrote: > >> Hey y’all, >> >> On my Linux VM, I am seeing a lot of these errors. Any one else see these? >> >> Exception (no rows returned): >> org.apache.drill.common.exceptions.UserException: CONNECTION ERROR: >> Connection null <--> null (user client) closed unexpectedly. >> >> >> [Error Id: d9194b8a-cd66-43e3-9200-190ae9ed13ba ]. Returned in 2882ms. >> >> I am guessing is due to Jacques’s change [960f876]. >> >> Thank you, >> Sudheesh >> >>
