[jira] [Created] (ARROW-4296) [Plasma] Starting Plasma store with use_one_memory_mapped_file enabled crashes due to improper memory alignment

2019-01-18 Thread Anurag Khandelwal (JIRA)
Anurag Khandelwal created ARROW-4296: Summary: [Plasma] Starting Plasma store with use_one_memory_mapped_file enabled crashes due to improper memory alignment Key: ARROW-4296 URL: https://issues.apache.org/jir

[jira] [Created] (ARROW-4295) [Plasma] Incorrect log message when evicting objects

2019-01-18 Thread Anurag Khandelwal (JIRA)
Anurag Khandelwal created ARROW-4295: Summary: [Plasma] Incorrect log message when evicting objects Key: ARROW-4295 URL: https://issues.apache.org/jira/browse/ARROW-4295 Project: Apache Arrow

Re: [VOTE] Release Apache Arrow 0.12.0 RC4

2019-01-18 Thread Andrew Palumbo
My mistake I missed the note about using the verify script from master. On Jan 18, 2019 3:38 PM, Andrew Palumbo wrote: I seem have been failing here: ../../../release/libgandiva.so.12.0.0: undefined reference to `llvm::sys::DynamicLibrary::getPermanentLibrary(char const*, std::string*)' collect

Re: [VOTE] Release Apache Arrow 0.12.0 RC4

2019-01-18 Thread Andrew Palumbo
I seem have been failing here: ../../../release/libgandiva.so.12.0.0: undefined reference to `llvm::sys::DynamicLibrary::getPermanentLibrary(char const*, std::string*)' collect2: error: ld returned 1 exit status src/gandiva/tests/CMakeFiles/gandiva-date_time_test.dir/build.make:94: recipe for ta

[jira] [Created] (ARROW-4294) [Plasma] Add support for evicting objects to external store

2019-01-18 Thread Anurag Khandelwal (JIRA)
Anurag Khandelwal created ARROW-4294: Summary: [Plasma] Add support for evicting objects to external store Key: ARROW-4294 URL: https://issues.apache.org/jira/browse/ARROW-4294 Project: Apache Arr

[jira] [Created] (ARROW-4293) [C++] Can't access parquet statistics on binary columns

2019-01-18 Thread Ildar (JIRA)
Ildar created ARROW-4293: Summary: [C++] Can't access parquet statistics on binary columns Key: ARROW-4293 URL: https://issues.apache.org/jira/browse/ARROW-4293 Project: Apache Arrow Issue Type: Bug

Re: Benchmarking dashboard proposal

2019-01-18 Thread Tom Augspurger
I'll see if I can figure out why the benchmarks at https://pandas.pydata.org/speed/arrow/ aren't being updated this weekend. On Fri, Jan 18, 2019 at 2:34 AM Uwe L. Korn wrote: > Hello, > > note that we have(had?) the Python benchmarks continuously running and > reported at https://pandas.pydata.

[jira] [Created] (ARROW-4292) [Release] Add script to test release verification script against master branch

2019-01-18 Thread Wes McKinney (JIRA)
Wes McKinney created ARROW-4292: --- Summary: [Release] Add script to test release verification script against master branch Key: ARROW-4292 URL: https://issues.apache.org/jira/browse/ARROW-4292 Project: A

Re: Export symbol guidelines

2019-01-18 Thread Wes McKinney
It is probably safer to namespace those symbols On Thu, Jan 17, 2019 at 11:51 AM shyam narayan singh wrote: > > Vendored code is part of the arrow. Gandiva is just the caller of the > timezone apis. > > Regards > Shyam > > On Thu, Jan 17, 2019 at 11:06 PM Antoine Pitrou wrote: > > > > > Side not

[jira] [Created] (ARROW-4291) [Dev] Support selecting features in release scripts

2019-01-18 Thread Uwe L. Korn (JIRA)
Uwe L. Korn created ARROW-4291: -- Summary: [Dev] Support selecting features in release scripts Key: ARROW-4291 URL: https://issues.apache.org/jira/browse/ARROW-4291 Project: Apache Arrow Issue Ty

[jira] [Created] (ARROW-4290) [C++/Gandiva] Support detecting correct LLVM version in Homebrew

2019-01-18 Thread Uwe L. Korn (JIRA)
Uwe L. Korn created ARROW-4290: -- Summary: [C++/Gandiva] Support detecting correct LLVM version in Homebrew Key: ARROW-4290 URL: https://issues.apache.org/jira/browse/ARROW-4290 Project: Apache Arrow

[jira] [Created] (ARROW-4289) [C++] Forward AR and RANLIB to thirdparty builds

2019-01-18 Thread Uwe L. Korn (JIRA)
Uwe L. Korn created ARROW-4289: -- Summary: [C++] Forward AR and RANLIB to thirdparty builds Key: ARROW-4289 URL: https://issues.apache.org/jira/browse/ARROW-4289 Project: Apache Arrow Issue Type:

Re: Benchmarking dashboard proposal

2019-01-18 Thread Brian Hulette
We also have some JS benchmarks [1]. Currently they're only really run on an ad-hoc basis to manually test major changes but it would be great to include them in this. [1] https://github.com/apache/arrow/tree/master/js/perf On Fri, Jan 18, 2019 at 12:34 AM Uwe L. Korn wrote: > Hello, > > note t

Re: 0.12.0-rc2 not building on win32

2019-01-18 Thread Wes McKinney
Can we open a JIRA issue about the 32-bit MSYS2 build? Thanks On Sun, Jan 13, 2019 at 2:03 PM Wes McKinney wrote: > > Understood. My sense from the other email thread was that R is definitely > going to miss 0.12. That will give you all around 8-10 weeks to sort out the > build and packaging q

[jira] [Created] (ARROW-4288) Installation instructions don't work on Ubuntu 18.04

2019-01-18 Thread JIRA
Kirill Müller created ARROW-4288: Summary: Installation instructions don't work on Ubuntu 18.04 Key: ARROW-4288 URL: https://issues.apache.org/jira/browse/ARROW-4288 Project: Apache Arrow Iss

[jira] [Created] (ARROW-4287) [C++] Ensure minimal bison version on OSX for Thrift

2019-01-18 Thread Uwe L. Korn (JIRA)
Uwe L. Korn created ARROW-4287: -- Summary: [C++] Ensure minimal bison version on OSX for Thrift Key: ARROW-4287 URL: https://issues.apache.org/jira/browse/ARROW-4287 Project: Apache Arrow Issue T

[jira] [Created] (ARROW-4286) [C++/R] Namespace vendored Boost

2019-01-18 Thread Uwe L. Korn (JIRA)
Uwe L. Korn created ARROW-4286: -- Summary: [C++/R] Namespace vendored Boost Key: ARROW-4286 URL: https://issues.apache.org/jira/browse/ARROW-4286 Project: Apache Arrow Issue Type: New Feature

Re: Benchmarking dashboard proposal

2019-01-18 Thread Uwe L. Korn
Hello, note that we have(had?) the Python benchmarks continuously running and reported at https://pandas.pydata.org/speed/arrow/. Seems like this stopped in July 2018. UWe On Fri, Jan 18, 2019, at 9:23 AM, Antoine Pitrou wrote: > > Hi Areg, > > That sounds like a good idea to me. Note our be

Re: Benchmarking dashboard proposal

2019-01-18 Thread Antoine Pitrou
Hi Areg, That sounds like a good idea to me. Note our benchmarks are currently scattered accross the various implementations. The two that I know of: - the C++ benchmarks are standalone executables created using the Google Benchmark library, aptly named "*-benchmark" (or "*-benchmark.exe" on