When is 1.2 planned for release? Sent from my iPhone
> On Aug 18, 2015, at 2:53 PM, Paul Mogren <[email protected]> wrote: > > I looked at JIRA and it seems this fix is sitting around waiting for a > 1.2.0 release to roll around, which looks like it is still going to be a > while longer. Could we please have a point release for this? > > Thanks, > Paul > > > >> On 7/28/15, 2:42 PM, "Daniel Barclay" <[email protected]> wrote: >> >> Parth Chandra wrote: >>> Yes and I probably reviewed it and missed it. We were missing a unit >>> test >>> which would have caught this. >> >> Yes; evidently we didn't have any test that used PreparedStatement enough >> to execute a query. >> >> Daniel >> >>> >>> It's being fixed ASAP. ( DRILL-3566 ) >>> >>> >>> >>> On Mon, Jul 27, 2015 at 9:23 PM, Jacques Nadeau <[email protected]> >>> wrote: >>> >>>> Agreed. It should be fixed. Just trying to provide work around until >>>> it >>>> is fixed. It is unfortunate that it was broken 1.1. Must have been >>>> all the >>>> jdbc refactoring. >>>>> On Jul 27, 2015 7:57 PM, "Anas Mesrah" <[email protected]> wrote: >>>>> >>>>> Hi Jacques, >>>>> >>>>> You are right BUT there are many softwares built on PreparedStatements >>>> and >>>>> they may integrate with Drll. I am not sure about the current big BI >>>>> products integrating with drill, if you skip that you are simply >>>>> ignoring >>>>> them. In addition, this is working on previous versions, I tested >>>>> 1.0.0 >>>> and >>>>> 0.8.0. I am sure something can be fixed. >> >> >> -- >> Daniel Barclay >> MapR Technologies > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This e-mail message from State Compensation Insurance Fund and all attachments transmitted with it may be privileged or confidential and protected from disclosure. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying, or taking any action based on it is strictly prohibited and may have legal consequences. If you have received this e-mail in error, please notify the sender by reply e-mail and destroy the original message and all copies. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
