[jira] [Created] (ARROW-1758) [Python] Remove pickle=True option for object serialization

2017-10-31 Thread Philipp Moritz (JIRA)
Philipp Moritz created ARROW-1758: - Summary: [Python] Remove pickle=True option for object serialization Key: ARROW-1758 URL: https://issues.apache.org/jira/browse/ARROW-1758 Project: Apache Arrow

[jira] [Created] (ARROW-1759) [Python] Add function / property to get implied Arrow schema from Parquet file

2017-10-31 Thread Wes McKinney (JIRA)
Wes McKinney created ARROW-1759: --- Summary: [Python] Add function / property to get implied Arrow schema from Parquet file Key: ARROW-1759 URL: https://issues.apache.org/jira/browse/ARROW-1759 Project: A

RE: JDBC Adapter for Apache-Arrow

2017-10-31 Thread Atul Dambalkar
Hi Julian, Thanks for your response. If I understand correctly (looking at other adapters), Calcite-Arrow adapter would provide SQL front end for in-memory Arrow data objects/structures. So from that perspective, are you suggesting building the Calcite-Arrow adapter? In this case, what we are

Re: JDBC Adapter for Apache-Arrow

2017-10-31 Thread Julian Hyde
Sorry I didn’t read your email thoroughly enough. I was talking about the inverse (JDBC reading from Arrow) whereas you are talking about Arrow reading from JDBC. Your proposal makes perfect sense. JDBC is quite a chatty interface (a call for every column of every row, plus an occasional call t

RE: JDBC Adapter for Apache-Arrow

2017-10-31 Thread Atul Dambalkar
Thanks for your thoughts Julian. I think, adding support for Arrow objects for Avatica Remote Driver (AvaticaToArrowConverter) can be certainly taken up as another activity. And you are right, we will have to look at specific JDBC driver to really optimize it individually. I would be curious if

Re: JDBC Adapter for Apache-Arrow

2017-10-31 Thread Laurent Goujon
I really like Julian's idea of unwrapping Arrow objects out of the JDBC ResultSet, but I wonder if the unwrap class has to be specific to the driver and if an interface can be designed to be used by multiple drivers: for drivers based on Arrow, it means you could totally skip the serialization/dese

Re: JDBC Adapter for Apache-Arrow

2017-10-31 Thread Julian Hyde
Yeah, I agree, it should be an interface defined as part of Arrow. Not driver-specific. > On Oct 31, 2017, at 1:37 PM, Laurent Goujon wrote: > > I really like Julian's idea of unwrapping Arrow objects out of the JDBC > ResultSet, but I wonder if the unwrap class has to be specific to the > driv

Re: JDBC Adapter for Apache-Arrow

2017-10-31 Thread 丁锦祥
unsubscribe On Tue, Oct 31, 2017 at 4:28 PM, Julian Hyde wrote: > Yeah, I agree, it should be an interface defined as part of Arrow. Not > driver-specific. > > > On Oct 31, 2017, at 1:37 PM, Laurent Goujon wrote: > > > > I really like Julian's idea of unwrapping Arrow objects out of the JDBC >

[jira] [Created] (ARROW-1760) [Java] Add Apache Mnemonic (incubating) as alternative allocator for storage-class memory support

2017-10-31 Thread Wes McKinney (JIRA)
Wes McKinney created ARROW-1760: --- Summary: [Java] Add Apache Mnemonic (incubating) as alternative allocator for storage-class memory support Key: ARROW-1760 URL: https://issues.apache.org/jira/browse/ARROW-1760