[jira] [Created] (ARROW-3994) [C++] Remove ARROW_GANDIVA_BUILD_TESTS option

Wes McKinney created ARROW-3994: --- Summary: [C++] Remove ARROW_GANDIVA_BUILD_TESTS option Key: ARROW-3994 URL: https://issues.apache.org/jira/browse/ARROW-3994 Project: Apache Arrow Issue Type:

[jira] [Created] (ARROW-3993) [JS] CI Jobs Failing

Brian Hulette created ARROW-3993: Summary: [JS] CI Jobs Failing Key: ARROW-3993 URL: https://issues.apache.org/jira/browse/ARROW-3993 Project: Apache Arrow Issue Type: Task

[jira] [Created] (ARROW-3992) pyarrow compile from source issues on RedHat 7.4

David Lee created ARROW-3992: Summary: pyarrow compile from source issues on RedHat 7.4 Key: ARROW-3992 URL: https://issues.apache.org/jira/browse/ARROW-3992 Project: Apache Arrow Issue Type:

[jira] [Created] (ARROW-3991) [gandiva] floating point division shouldn't cause errors

Pindikura Ravindra created ARROW-3991: - Summary: [gandiva] floating point division shouldn't cause errors Key: ARROW-3991 URL: https://issues.apache.org/jira/browse/ARROW-3991 Project: Apache

[jira] [Created] (ARROW-3990) [Python] developer documentation is missing double-conversion dep

Francois Saint-Jacques created ARROW-3990: - Summary: [Python] developer documentation is missing double-conversion dep Key: ARROW-3990 URL: https://issues.apache.org/jira/browse/ARROW-3990

Re: Thread-safety of buffer allocators in Java

Thanks Jacques! On Sun, Dec 9, 2018 at 6:47 AM Jacques Nadeau wrote: > Yes, that is true. Allocators, buffers and pretty much everything inbetween > is thread safe. Locking around the memory backing a buffer itself needs to > be managed in the app. You can review the doc here which talks more

[jira] [Created] (ARROW-3989) [RUST] CSV Reader Should Handle Case Sensitivity for Boolean Values

nevi_me created ARROW-3989: -- Summary: [RUST] CSV Reader Should Handle Case Sensitivity for Boolean Values Key: ARROW-3989 URL: https://issues.apache.org/jira/browse/ARROW-3989 Project: Apache Arrow

[jira] [Created] (ARROW-3988) [C++] Do not build unit tests by default in build system

Wes McKinney created ARROW-3988: --- Summary: [C++] Do not build unit tests by default in build system Key: ARROW-3988 URL: https://issues.apache.org/jira/browse/ARROW-3988 Project: Apache Arrow

Analytics in Rust [was Re: Timeline for Arrow 0.12.0 release]

Changing the subject as we've veered off topic On Mon, Dec 10, 2018 at 8:04 AM Andy Grove wrote: > > Cool. I will continue to add primitive operations but I am now adding this > in a separate source file to keep it separate from the core array code. > > I'm not sure how important it will be to

Re: valid NaNs versus invalid NaNs?

Alternately Rhys, what Wes said. :) Donald E. Foss | @DonaldFoss Never Stop Learning! -- __o _`\<,_ ---(_)/ (_) > On Dec 10, 2018, at 11:23 AM, Donald Foss wrote: > > +1 on NaNs being an interop nightmare already, especially for those who work > with

Re: valid NaNs versus invalid NaNs?

+1 on NaNs being an interop nightmare already, especially for those who work with multiple coding languages at the same time. Issues regarding NaNs may be found at https://issues.apache.org/jira/browse/ARROW-2806?jql=text%20~%20%22NaN%22

RE: valid NaNs versus invalid NaNs?

>> Anyhow, it seems worth addressing this gap at the written specification >> level. > What would you suggest? We could add a statement to be explicit that no > special / sentinel values (which includes NaN) are recognized as null. I like your suggestion Wes. Please consider making that

Re: valid NaNs versus invalid NaNs?

hi Rhys, On Mon, Dec 10, 2018 at 9:53 AM Rhys Ulerich wrote: > > 'Morning, > > > > Regarding https://arrow.apache.org/docs/memory_layout.html, how should > is_valid be interpreted for primitive types that have their own notions of > is_valid? > > > > Concretely, how should folks interpret a

[jira] [Created] (ARROW-3987) Compact ArrowBuf to reduce its heap footprint

shyam narayan singh created ARROW-3987: -- Summary: Compact ArrowBuf to reduce its heap footprint Key: ARROW-3987 URL: https://issues.apache.org/jira/browse/ARROW-3987 Project: Apache Arrow

Re: Timeline for Arrow 0.12.0 release

Cool. I will continue to add primitive operations but I am now adding this in a separate source file to keep it separate from the core array code. I'm not sure how important it will be to support Rust data sources with Gandiva. I can see that each language should be able to construct the logical

[jira] [Created] (ARROW-3986) [C++] Write prose documentation

Antoine Pitrou created ARROW-3986: - Summary: [C++] Write prose documentation Key: ARROW-3986 URL: https://issues.apache.org/jira/browse/ARROW-3986 Project: Apache Arrow Issue Type:

[jira] [Created] (ARROW-3983) [Gandiva][Crossbow] Use static boost while packaging

Praveen Kumar Desabandu created ARROW-3983: -- Summary: [Gandiva][Crossbow] Use static boost while packaging Key: ARROW-3983 URL: https://issues.apache.org/jira/browse/ARROW-3983 Project:

[jira] [Created] (ARROW-3982) [C++] Allow "binary" input in simple JSON format

Antoine Pitrou created ARROW-3982: - Summary: [C++] Allow "binary" input in simple JSON format Key: ARROW-3982 URL: https://issues.apache.org/jira/browse/ARROW-3982 Project: Apache Arrow

[jira] [Created] (ARROW-3981) [C++] Rename json.h

Antoine Pitrou created ARROW-3981: - Summary: [C++] Rename json.h Key: ARROW-3981 URL: https://issues.apache.org/jira/browse/ARROW-3981 Project: Apache Arrow Issue Type: Wish

[jira] [Created] (ARROW-3980) [C++] Fix CRTP use in json-simple.cc

Antoine Pitrou created ARROW-3980: - Summary: [C++] Fix CRTP use in json-simple.cc Key: ARROW-3980 URL: https://issues.apache.org/jira/browse/ARROW-3980 Project: Apache Arrow Issue Type: Bug

[jira] [Created] (ARROW-3979) [Gandiva] fix all valgrind reported errors

Pindikura Ravindra created ARROW-3979: - Summary: [Gandiva] fix all valgrind reported errors Key: ARROW-3979 URL: https://issues.apache.org/jira/browse/ARROW-3979 Project: Apache Arrow