[jira] [Commented] (ARROW-3086) [Glib] GISCAN fails due to conda-shipped openblas
[
https://issues.apache.org/jira/browse/ARROW-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783196#comment-16783196
]
Uwe L. Korn commented on ARROW-3086:
No, this is working for me.
> [Glib] GISCAN fails due to conda-shipped openblas
> -
>
> Key: ARROW-3086
> URL: https://issues.apache.org/jira/browse/ARROW-3086
> Project: Apache Arrow
> Issue Type: Bug
> Components: GLib
>Affects Versions: 0.10.0
>Reporter: Uwe L. Korn
>Assignee: Kouhei Sutou
>Priority: Major
> Fix For: 0.14.0
>
>
> With the changes in [https://github.com/apache/arrow/pull/2374], the
> libraries provided by conda are now in the library path when running the
> GISCAN step. This sadly leads to the poisoning of the search path with the
> conda provided openblas which is incompatible with the system provided
> libLAPACK.dylib
> {code:java}
> dyld: Library not loaded:
> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
> Referenced from:
> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
> Reason: Incompatible library version: vecLib requires version 1.0.0 or later,
> but libLAPACK.dylib provides version 0.0.0{code}
> While mentioned that it explicitly loads
> {{/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib}},
> it seems that {{liblapack.so}} from the conda installation gets picked up
> first. This only provides the library symbols with version 0.0.0 and thus is
> incompatible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ARROW-3086) [Glib] GISCAN fails due to conda-shipped openblas
[
https://issues.apache.org/jira/browse/ARROW-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn resolved ARROW-3086.
Resolution: Fixed
> [Glib] GISCAN fails due to conda-shipped openblas
> -
>
> Key: ARROW-3086
> URL: https://issues.apache.org/jira/browse/ARROW-3086
> Project: Apache Arrow
> Issue Type: Bug
> Components: GLib
>Affects Versions: 0.10.0
>Reporter: Uwe L. Korn
>Assignee: Kouhei Sutou
>Priority: Major
> Fix For: 0.13.0
>
>
> With the changes in [https://github.com/apache/arrow/pull/2374], the
> libraries provided by conda are now in the library path when running the
> GISCAN step. This sadly leads to the poisoning of the search path with the
> conda provided openblas which is incompatible with the system provided
> libLAPACK.dylib
> {code:java}
> dyld: Library not loaded:
> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
> Referenced from:
> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
> Reason: Incompatible library version: vecLib requires version 1.0.0 or later,
> but libLAPACK.dylib provides version 0.0.0{code}
> While mentioned that it explicitly loads
> {{/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib}},
> it seems that {{liblapack.so}} from the conda installation gets picked up
> first. This only provides the library symbols with version 0.0.0 and thus is
> incompatible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ARROW-3086) [Glib] GISCAN fails due to conda-shipped openblas
[
https://issues.apache.org/jira/browse/ARROW-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn updated ARROW-3086:
---
Fix Version/s: (was: 0.14.0)
0.13.0
> [Glib] GISCAN fails due to conda-shipped openblas
> -
>
> Key: ARROW-3086
> URL: https://issues.apache.org/jira/browse/ARROW-3086
> Project: Apache Arrow
> Issue Type: Bug
> Components: GLib
>Affects Versions: 0.10.0
>Reporter: Uwe L. Korn
>Assignee: Kouhei Sutou
>Priority: Major
> Fix For: 0.13.0
>
>
> With the changes in [https://github.com/apache/arrow/pull/2374], the
> libraries provided by conda are now in the library path when running the
> GISCAN step. This sadly leads to the poisoning of the search path with the
> conda provided openblas which is incompatible with the system provided
> libLAPACK.dylib
> {code:java}
> dyld: Library not loaded:
> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
> Referenced from:
> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
> Reason: Incompatible library version: vecLib requires version 1.0.0 or later,
> but libLAPACK.dylib provides version 0.0.0{code}
> While mentioned that it explicitly loads
> {{/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib}},
> it seems that {{liblapack.so}} from the conda installation gets picked up
> first. This only provides the library symbols with version 0.0.0 and thus is
> incompatible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ARROW-4609) [C++] Use google benchmark from toolchain
[ https://issues.apache.org/jira/browse/ARROW-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn updated ARROW-4609: --- Fix Version/s: (was: 0.14.0) 0.13.0 > [C++] Use google benchmark from toolchain > - > > Key: ARROW-4609 > URL: https://issues.apache.org/jira/browse/ARROW-4609 > Project: Apache Arrow > Issue Type: Improvement > Components: C++, Packaging >Reporter: Uwe L. Korn >Assignee: Uwe L. Korn >Priority: Major > Labels: pull-request-available > Fix For: 0.13.0 > > Time Spent: 2h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ARROW-4242) [C++] Seg fault when running unit tests on fresh Arch Linux install
[
https://issues.apache.org/jira/browse/ARROW-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn updated ARROW-4242:
---
Fix Version/s: (was: 0.14.0)
> [C++] Seg fault when running unit tests on fresh Arch Linux install
> ---
>
> Key: ARROW-4242
> URL: https://issues.apache.org/jira/browse/ARROW-4242
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
> Environment: Arch Linux x86-64
>Reporter: Michael Vilim
>Assignee: Uwe L. Korn
>Priority: Minor
> Attachments: Dockerfile
>
>
> First, let me say I appreciate all the work that has been put into this
> project. I have been following it with great interest and recently decided to
> include it in one of my projects.
> However, I have run into an issue with a segmentation fault when trying to
> run the C++ unit tests (which previously worked for me). This issue appears
> to be something specific to my system (I am running Arch Linux). I can
> reproduce the issue with the minimal Docker install of Arch:
> {noformat}
> FROM archimg/base
> RUN \
> pacman -Sy --noconfirm git cmake gcc make boost autoconf python; \
> git clone --recursive https://github.com/apache/arrow.git; \
> cd arrow/cpp; \
> mkdir build; \
> cd build; \
> cmake -DARROW_BUILD_TESTS=ON ..; \
> make
> {noformat}
> If you create a Dockerfile with those contents and then run
> {noformat}
> docker build -t mvilim/arch-arrow-test-segfault .
> docker run mvilim/arch-arrow-test-segfault /bin/bash -c "cd /arrow/cpp/build;
> make unittest; gcc --version; cmake --version"{noformat}
> you should be able to reproduce the issue:
> {noformat}
> The following tests FAILED:
> 2 - arrow-array-test (Failed)
> 3 - arrow-buffer-test (Failed)
> 8 - arrow-stl-test (Failed)
> 9 - arrow-type-test (Failed)
> 10 - arrow-table-test (Failed)
> 15 - arrow-compute-boolean-test (Failed)
> 16 - arrow-compute-cast-test (Failed)
> 17 - arrow-compute-hash-test (Failed)
> 18 - arrow-feather-test (Failed)
> 19 - arrow-ipc-read-write-test (Failed)
> 20 - arrow-ipc-json-simple-test (Failed)
> 21 - arrow-ipc-json-test (Failed)
> 24 - arrow-csv-column-builder-test (Failed)
> 28 - arrow-io-compressed-test (Failed)
> 31 - arrow-io-memory-test (Failed){noformat}
> If you run the container interactively and inspect the logs, you will see
> that all the failures are caused by seg faults.
> I used git bisect to narrow the problem down to commit 7cdab9b06 when the
> tests were switched to use shared linking by default. Static linking works
> fine for me (using -DARROW_TEST_LINKAGE=static).
> I also compiled with Clang and -DARROW_USE_ASAN=ON and inspected several of
> the stack traces. It looks like all the seg faults happen during creation of
> a shared pointer, but in varied places.
> On creation of Int32Type:
> {noformat}
> ./debug/arrow-array-test
> AddressSanitizer:DEADLYSIGNAL
> =
> ==29563==ERROR: AddressSanitizer: SEGV on unknown address 0x (pc
> 0x558afa951b70 bp 0x7ffcf1c34880 sp 0x7ffcf1c34810 T0)
> ==29563==The signal is caused by a READ memory access.
> ==29563==Hint: address points to the zero page.
> #0 0x558afa951b6f in std::type_info::operator==(std::type_info const&) const
> /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/typeinfo:123:12
> #1 0x558afa9b2c16 in std::Sp_counted_ptr_inplace std::allocator,
> (_gnu_cxx::_Lock_policy)2>::_M_get_deleter(std::type_info const&)
> /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/bits/shared_ptr_base.h:573:16
> #2 0x7fe7b711e6f1 in
> std::_shared_count<(_gnu_cxx::_Lock_policy)2>::_M_get_deleter(std::type_info
> const&) const
> /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/bits/shared_ptr_base.h:751:31
> #3 0x7fe7b73ec240 in std::_shared_ptr (gnu_cxx::_Lock_policy)2>::_shared_ptr
> >(std::_Sp_make_shared_tag, std::allocator const&)
> /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/bits/shared_ptr_base.h:1328:28
> #4 0x7fe7b73ec1c7 in
> std::shared_ptr::shared_ptr
> >(std::_Sp_make_shared_tag, std::allocator const&)
> /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/bits/shared_ptr.h:360:4
> #5 0x7fe7b73ec14b in std::shared_ptr
> std::allocate_shared
> >(std::allocator const&)
> /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/bits/shared_ptr.h:706:14
> #6 0x7fe7b73cd323 in std::shared_ptr
> std::make_shared()
> /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/bits/shared_ptr.h:722:14
> #7 0x7fe7b73c3f2f in arrow::int32()
> /home/mvilim/repos/arrow/cpp/src/arrow/type.cc:484:1
> #8 0
[jira] [Resolved] (ARROW-4242) [C++] Seg fault when running unit tests on fresh Arch Linux install
[
https://issues.apache.org/jira/browse/ARROW-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn resolved ARROW-4242.
Resolution: Won't Fix
We need to wait for the upstream fix, we cannot fix this ourselves. Spent quite
some time in looking into workaround but this is a major hurdle for our
codebase.
> [C++] Seg fault when running unit tests on fresh Arch Linux install
> ---
>
> Key: ARROW-4242
> URL: https://issues.apache.org/jira/browse/ARROW-4242
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
> Environment: Arch Linux x86-64
>Reporter: Michael Vilim
>Assignee: Uwe L. Korn
>Priority: Minor
> Attachments: Dockerfile
>
>
> First, let me say I appreciate all the work that has been put into this
> project. I have been following it with great interest and recently decided to
> include it in one of my projects.
> However, I have run into an issue with a segmentation fault when trying to
> run the C++ unit tests (which previously worked for me). This issue appears
> to be something specific to my system (I am running Arch Linux). I can
> reproduce the issue with the minimal Docker install of Arch:
> {noformat}
> FROM archimg/base
> RUN \
> pacman -Sy --noconfirm git cmake gcc make boost autoconf python; \
> git clone --recursive https://github.com/apache/arrow.git; \
> cd arrow/cpp; \
> mkdir build; \
> cd build; \
> cmake -DARROW_BUILD_TESTS=ON ..; \
> make
> {noformat}
> If you create a Dockerfile with those contents and then run
> {noformat}
> docker build -t mvilim/arch-arrow-test-segfault .
> docker run mvilim/arch-arrow-test-segfault /bin/bash -c "cd /arrow/cpp/build;
> make unittest; gcc --version; cmake --version"{noformat}
> you should be able to reproduce the issue:
> {noformat}
> The following tests FAILED:
> 2 - arrow-array-test (Failed)
> 3 - arrow-buffer-test (Failed)
> 8 - arrow-stl-test (Failed)
> 9 - arrow-type-test (Failed)
> 10 - arrow-table-test (Failed)
> 15 - arrow-compute-boolean-test (Failed)
> 16 - arrow-compute-cast-test (Failed)
> 17 - arrow-compute-hash-test (Failed)
> 18 - arrow-feather-test (Failed)
> 19 - arrow-ipc-read-write-test (Failed)
> 20 - arrow-ipc-json-simple-test (Failed)
> 21 - arrow-ipc-json-test (Failed)
> 24 - arrow-csv-column-builder-test (Failed)
> 28 - arrow-io-compressed-test (Failed)
> 31 - arrow-io-memory-test (Failed){noformat}
> If you run the container interactively and inspect the logs, you will see
> that all the failures are caused by seg faults.
> I used git bisect to narrow the problem down to commit 7cdab9b06 when the
> tests were switched to use shared linking by default. Static linking works
> fine for me (using -DARROW_TEST_LINKAGE=static).
> I also compiled with Clang and -DARROW_USE_ASAN=ON and inspected several of
> the stack traces. It looks like all the seg faults happen during creation of
> a shared pointer, but in varied places.
> On creation of Int32Type:
> {noformat}
> ./debug/arrow-array-test
> AddressSanitizer:DEADLYSIGNAL
> =
> ==29563==ERROR: AddressSanitizer: SEGV on unknown address 0x (pc
> 0x558afa951b70 bp 0x7ffcf1c34880 sp 0x7ffcf1c34810 T0)
> ==29563==The signal is caused by a READ memory access.
> ==29563==Hint: address points to the zero page.
> #0 0x558afa951b6f in std::type_info::operator==(std::type_info const&) const
> /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/typeinfo:123:12
> #1 0x558afa9b2c16 in std::Sp_counted_ptr_inplace std::allocator,
> (_gnu_cxx::_Lock_policy)2>::_M_get_deleter(std::type_info const&)
> /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/bits/shared_ptr_base.h:573:16
> #2 0x7fe7b711e6f1 in
> std::_shared_count<(_gnu_cxx::_Lock_policy)2>::_M_get_deleter(std::type_info
> const&) const
> /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/bits/shared_ptr_base.h:751:31
> #3 0x7fe7b73ec240 in std::_shared_ptr (gnu_cxx::_Lock_policy)2>::_shared_ptr
> >(std::_Sp_make_shared_tag, std::allocator const&)
> /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/bits/shared_ptr_base.h:1328:28
> #4 0x7fe7b73ec1c7 in
> std::shared_ptr::shared_ptr
> >(std::_Sp_make_shared_tag, std::allocator const&)
> /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/bits/shared_ptr.h:360:4
> #5 0x7fe7b73ec14b in std::shared_ptr
> std::allocate_shared
> >(std::allocator const&)
> /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/bits/shared_ptr.h:706:14
> #6 0x7fe7b73cd323 in std::shared_ptr
> std::make_shared()
> /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/8.2.1/.
[jira] [Commented] (ARROW-4356) [CI] Add integration (docker) test for turbodbc
[
https://issues.apache.org/jira/browse/ARROW-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783465#comment-16783465
]
Uwe L. Korn commented on ARROW-4356:
I hope so.
> [CI] Add integration (docker) test for turbodbc
> ---
>
> Key: ARROW-4356
> URL: https://issues.apache.org/jira/browse/ARROW-4356
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, Continuous Integration
>Reporter: Uwe L. Korn
>Priority: Major
> Fix For: 0.13.0
>
>
> We regularly break our API so that {{turbodbc}} needs to make minor changes
> to support the new Arrow version. We should setup a small integration test to
> check before a release that {{turbodbc}} can easily upgrade.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARROW-3277) [Python] Validate manylinux1 builds with crossbow instead of each Travis CI build
[ https://issues.apache.org/jira/browse/ARROW-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783506#comment-16783506 ] Uwe L. Korn commented on ARROW-3277: With my CMake refactor, this is the last build to run with GCC 4.8. I'd rather invest in speeding this up a bit again. We're currently again at <30min runtime with the recent changes by [~kszucs], so I have the feeling we're fine for some time. > [Python] Validate manylinux1 builds with crossbow instead of each Travis CI > build > - > > Key: ARROW-3277 > URL: https://issues.apache.org/jira/browse/ARROW-3277 > Project: Apache Arrow > Issue Type: Improvement > Components: Python >Reporter: Wes McKinney >Priority: Major > Fix For: 0.14.0 > > > The recent manylinxu1 timeouts bring up a bigger question which is > centralizing the validation of packaging builds. We definitely want the > project to be notified in a timely way when there is some problem with a > packaging build -- since manylinux1 can be run locally in Docker, it is > easier to debug and need not necessarily be run on every commit -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-4760) [C++] protobuf 3.7 defines EXPECT_OK that clashes with Arrow's macro
Uwe L. Korn created ARROW-4760:
--
Summary: [C++] protobuf 3.7 defines EXPECT_OK that clashes with
Arrow's macro
Key: ARROW-4760
URL: https://issues.apache.org/jira/browse/ARROW-4760
Project: Apache Arrow
Issue Type: Bug
Components: C++
Reporter: Uwe L. Korn
Assignee: Uwe L. Korn
Fix For: 0.13.0
This fails for me with the following error:
{code:java}
/home/travis/build/xhochy/arrow/cpp/src/arrow/flight/test-util.cc
In file included from
/home/travis/build/xhochy/arrow/cpp-toolchain/include/google/protobuf/util/type_resolver.h:39:0,
from
/home/travis/build/xhochy/arrow/cpp-toolchain/include/google/protobuf/util/json_util.h:37,
from
/home/travis/build/xhochy/arrow/cpp-toolchain/include/grpcpp/impl/codegen/config_protobuf.h:70,
from
/home/travis/build/xhochy/arrow/cpp/src/arrow/flight/customize_protobuf.h:23,
from
/home/travis/build/xhochy/arrow/cpp/src/arrow/flight/protocol-internal.h:20,
from
/home/travis/build/xhochy/arrow/cpp/src/arrow/flight/internal.h:23,
from
/home/travis/build/xhochy/arrow/cpp/src/arrow/flight/test-util.cc:35:
/home/travis/build/xhochy/arrow/cpp-toolchain/include/google/protobuf/stubs/status.h:111:0:
error: "EXPECT_OK" redefined [-Werror]
#define EXPECT_OK(value) EXPECT_TRUE((value).ok())
In file included from
/home/travis/build/xhochy/arrow/cpp/src/arrow/ipc/test-common.h:35:0,
from
/home/travis/build/xhochy/arrow/cpp/src/arrow/flight/test-util.cc:30:
/home/travis/build/xhochy/arrow/cpp/src/arrow/testing/gtest_util.h:80:0: note:
this is the location of the previous definition
#define EXPECT_OK(expr) \
cc1plus: all warnings being treated as errors{code}
I would workaround this by renaming our {{EXPECT_OK}} to {{ARROW_EXPECT_OK}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARROW-4761) [C++] Support zstandard<1
Uwe L. Korn created ARROW-4761: -- Summary: [C++] Support zstandard<1 Key: ARROW-4761 URL: https://issues.apache.org/jira/browse/ARROW-4761 Project: Apache Arrow Issue Type: Improvement Components: C++, Packaging Reporter: Uwe L. Korn Assignee: Uwe L. Korn Fix For: 0.13.0 To support building with as many system packages as possible on Ubuntu, we should support building with zstandard 0.5.1 which is the one available on Ubuntu Xenial. Given the size of our current code for Zstandard, this seems feasible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-4762) [C++] Support RapidJSON<1.1.0
Uwe L. Korn created ARROW-4762:
--
Summary: [C++] Support RapidJSON<1.1.0
Key: ARROW-4762
URL: https://issues.apache.org/jira/browse/ARROW-4762
Project: Apache Arrow
Issue Type: Improvement
Components: C++, Packaging
Reporter: Uwe L. Korn
To support building with as many system packages as possible, we should support
RapidJSON<1.1.0. For example the distribution provided RapidJSON on Ubuntu
Xenial is {{0.12~git20141031-3}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARROW-4763) [C++/Python] Cannot build Gandiva in conda on OSX due to package conflicts
Uwe L. Korn created ARROW-4763:
--
Summary: [C++/Python] Cannot build Gandiva in conda on OSX due to
package conflicts
Key: ARROW-4763
URL: https://issues.apache.org/jira/browse/ARROW-4763
Project: Apache Arrow
Issue Type: Improvement
Components: C++, C++ - Gandiva, Python
Reporter: Uwe L. Korn
It is currently not reliably possible to build Gandiva with one of the conda
toolchains on OSX as the packages {{llvm==4.0.1}} (pulled in by the compilers)
and {{llvmdev==7.0.1}} conflict in some files:
https://github.com/conda-forge/llvmdev-feedstock/issues/60
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ARROW-4763) [C++/Python] Cannot build Gandiva in conda on OSX due to package conflicts
[
https://issues.apache.org/jira/browse/ARROW-4763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn updated ARROW-4763:
---
Issue Type: Bug (was: Improvement)
> [C++/Python] Cannot build Gandiva in conda on OSX due to package conflicts
> --
>
> Key: ARROW-4763
> URL: https://issues.apache.org/jira/browse/ARROW-4763
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, C++ - Gandiva, Python
>Reporter: Uwe L. Korn
>Priority: Major
>
> It is currently not reliably possible to build Gandiva with one of the conda
> toolchains on OSX as the packages {{llvm==4.0.1}} (pulled in by the
> compilers) and {{llvmdev==7.0.1}} conflict in some files:
> https://github.com/conda-forge/llvmdev-feedstock/issues/60
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARROW-4764) [C++/Java] conda-built libplasma_java doesn't work with system Java on Ubuntu Xenial
Uwe L. Korn created ARROW-4764:
--
Summary: [C++/Java] conda-built libplasma_java doesn't work with
system Java on Ubuntu Xenial
Key: ARROW-4764
URL: https://issues.apache.org/jira/browse/ARROW-4764
Project: Apache Arrow
Issue Type: Bug
Components: C++, C++ - Plasma, Packaging, Python
Reporter: Uwe L. Korn
System Java will load also the system {{libstdc++}} which is older then the
conda provided one. Thus a later loading of the plasma library will raise
missing symbol errors:
{code:java}
TODO{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ARROW-4764) [C++/Java] conda-built libplasma_java doesn't work with system Java on Ubuntu Xenial
[
https://issues.apache.org/jira/browse/ARROW-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn updated ARROW-4764:
---
Description:
System Java will load also the system {{libstdc++}} which is older then the
conda provided one. Thus a later loading of the plasma library will raise
missing symbol errors:
{code:java}
Start process 317574433 OK, cmd =
[/home/travis/build/xhochy/arrow/cpp-install/bin/plasma_store_server -s
/tmp/store14796 -m 1000]
Start object store success
Kill plasma store process forcely
Exception in thread "main" java.lang.UnsatisfiedLinkError:
/home/travis/build/xhochy/arrow/cpp-build/debug/libplasma_java.so:
/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.11' not found
(required by /home/travis/build/xhochy/arrow/cpp-build/debug/libplasma.so.13)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1941)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1857)
at java.lang.Runtime.loadLibrary0(Runtime.java:870)
at java.lang.System.loadLibrary(System.java:1122)
at
org.apache.arrow.plasma.PlasmaClientTest.(PlasmaClientTest.java:49)
at
org.apache.arrow.plasma.PlasmaClientTest.main(PlasmaClientTest.java:252){code}
was:
System Java will load also the system {{libstdc++}} which is older then the
conda provided one. Thus a later loading of the plasma library will raise
missing symbol errors:
{code:java}
TODO{code}
> [C++/Java] conda-built libplasma_java doesn't work with system Java on Ubuntu
> Xenial
>
>
> Key: ARROW-4764
> URL: https://issues.apache.org/jira/browse/ARROW-4764
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, C++ - Plasma, Packaging, Python
>Reporter: Uwe L. Korn
>Priority: Major
>
> System Java will load also the system {{libstdc++}} which is older then the
> conda provided one. Thus a later loading of the plasma library will raise
> missing symbol errors:
> {code:java}
> Start process 317574433 OK, cmd =
> [/home/travis/build/xhochy/arrow/cpp-install/bin/plasma_store_server -s
> /tmp/store14796 -m 1000]
> Start object store success
> Kill plasma store process forcely
> Exception in thread "main" java.lang.UnsatisfiedLinkError:
> /home/travis/build/xhochy/arrow/cpp-build/debug/libplasma_java.so:
> /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.11' not found
> (required by /home/travis/build/xhochy/arrow/cpp-build/debug/libplasma.so.13)
> at java.lang.ClassLoader$NativeLibrary.load(Native Method)
> at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1941)
> at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1857)
> at java.lang.Runtime.loadLibrary0(Runtime.java:870)
> at java.lang.System.loadLibrary(System.java:1122)
> at
> org.apache.arrow.plasma.PlasmaClientTest.(PlasmaClientTest.java:49)
> at
> org.apache.arrow.plasma.PlasmaClientTest.main(PlasmaClientTest.java:252){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ARROW-4756) [CI] document the procedure to update docker image for manylinux1 builds
[ https://issues.apache.org/jira/browse/ARROW-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn resolved ARROW-4756. Resolution: Fixed Fix Version/s: 0.13.0 Issue resolved by pull request 3802 [https://github.com/apache/arrow/pull/3802] > [CI] document the procedure to update docker image for manylinux1 builds > > > Key: ARROW-4756 > URL: https://issues.apache.org/jira/browse/ARROW-4756 > Project: Apache Arrow > Issue Type: Task > Components: Continuous Integration >Reporter: Pindikura Ravindra >Assignee: Pindikura Ravindra >Priority: Major > Labels: pull-request-available > Fix For: 0.13.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARROW-4775) [Website] Site navbar cannot be expanded
[ https://issues.apache.org/jira/browse/ARROW-4775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn resolved ARROW-4775. Resolution: Fixed Fix Version/s: 0.13.0 Issue resolved by pull request 3814 [https://github.com/apache/arrow/pull/3814] > [Website] Site navbar cannot be expanded > > > Key: ARROW-4775 > URL: https://issues.apache.org/jira/browse/ARROW-4775 > Project: Apache Arrow > Issue Type: Bug > Components: Website >Reporter: Kenta Murata >Assignee: Kenta Murata >Priority: Major > Labels: pull-request-available > Fix For: 0.13.0 > > Time Spent: 20m > Remaining Estimate: 0h > > I found that the navbar at the top of the page cannot be expanded when the > page is narrow. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ARROW-4758) [Flight] Build fails on Mac due to missing Schema_generated.h
[ https://issues.apache.org/jira/browse/ARROW-4758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn reassigned ARROW-4758: -- Assignee: Pindikura Ravindra > [Flight] Build fails on Mac due to missing Schema_generated.h > - > > Key: ARROW-4758 > URL: https://issues.apache.org/jira/browse/ARROW-4758 > Project: Apache Arrow > Issue Type: Task > Components: FlightRPC >Reporter: Pindikura Ravindra >Assignee: Pindikura Ravindra >Priority: Major > Labels: ci-failure, pull-request-available > Fix For: 0.13.0 > > Time Spent: 40m > Remaining Estimate: 0h > > I saw this on CI, a retrigger of the build fixed the issue and I am not able > to get the link of the previous build failure. > The error happened for the file flight/client.cc, which includes > -ipc/metadata--internal.h, which includes arrow/ipc/Schema_generated.h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARROW-4758) [Flight] Build fails on Mac due to missing Schema_generated.h
[ https://issues.apache.org/jira/browse/ARROW-4758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn resolved ARROW-4758. Resolution: Fixed Issue resolved by pull request 3803 [https://github.com/apache/arrow/pull/3803] > [Flight] Build fails on Mac due to missing Schema_generated.h > - > > Key: ARROW-4758 > URL: https://issues.apache.org/jira/browse/ARROW-4758 > Project: Apache Arrow > Issue Type: Task > Components: FlightRPC >Reporter: Pindikura Ravindra >Priority: Major > Labels: ci-failure, pull-request-available > Fix For: 0.13.0 > > Time Spent: 40m > Remaining Estimate: 0h > > I saw this on CI, a retrigger of the build fixed the issue and I am not able > to get the link of the previous build failure. > The error happened for the file flight/client.cc, which includes > -ipc/metadata--internal.h, which includes arrow/ipc/Schema_generated.h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-4777) [C++/Python] manylinux1: Update lz4 to 1.8.3
Uwe L. Korn created ARROW-4777: -- Summary: [C++/Python] manylinux1: Update lz4 to 1.8.3 Key: ARROW-4777 URL: https://issues.apache.org/jira/browse/ARROW-4777 Project: Apache Arrow Issue Type: Improvement Components: C++, Packaging, Python Reporter: Uwe L. Korn Assignee: Uwe L. Korn Fix For: 0.13.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-4778) [C++/Python] manylinux1: Update Thrift to 0.12.0
Uwe L. Korn created ARROW-4778: -- Summary: [C++/Python] manylinux1: Update Thrift to 0.12.0 Key: ARROW-4778 URL: https://issues.apache.org/jira/browse/ARROW-4778 Project: Apache Arrow Issue Type: Task Components: C++, Packaging, Python Reporter: Uwe L. Korn Assignee: Uwe L. Korn Fix For: 0.13.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ARROW-4760) [C++] protobuf 3.7 defines EXPECT_OK that clashes with Arrow's macro
[
https://issues.apache.org/jira/browse/ARROW-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16785494#comment-16785494
]
Uwe L. Korn commented on ARROW-4760:
This has been there for over 4 years now. This error simply popped up as I
didn't include protobuf headers using {{include(SYSTEM …)}}. Using {{SYSTEM}}
will let the compiler ignore all warnings in third-party headers. We have been
using this for now and I'll also switched to using this now in my CMake
refactor as there is an awful lot of warnings in the thirdparty headers.
> [C++] protobuf 3.7 defines EXPECT_OK that clashes with Arrow's macro
>
>
> Key: ARROW-4760
> URL: https://issues.apache.org/jira/browse/ARROW-4760
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
>Reporter: Uwe L. Korn
>Assignee: Uwe L. Korn
>Priority: Major
> Fix For: 0.13.0
>
>
> This fails for me with the following error:
> {code:java}
> /home/travis/build/xhochy/arrow/cpp/src/arrow/flight/test-util.cc
> In file included from
> /home/travis/build/xhochy/arrow/cpp-toolchain/include/google/protobuf/util/type_resolver.h:39:0,
> from
> /home/travis/build/xhochy/arrow/cpp-toolchain/include/google/protobuf/util/json_util.h:37,
> from
> /home/travis/build/xhochy/arrow/cpp-toolchain/include/grpcpp/impl/codegen/config_protobuf.h:70,
> from
> /home/travis/build/xhochy/arrow/cpp/src/arrow/flight/customize_protobuf.h:23,
> from
> /home/travis/build/xhochy/arrow/cpp/src/arrow/flight/protocol-internal.h:20,
> from
> /home/travis/build/xhochy/arrow/cpp/src/arrow/flight/internal.h:23,
> from
> /home/travis/build/xhochy/arrow/cpp/src/arrow/flight/test-util.cc:35:
> /home/travis/build/xhochy/arrow/cpp-toolchain/include/google/protobuf/stubs/status.h:111:0:
> error: "EXPECT_OK" redefined [-Werror]
> #define EXPECT_OK(value) EXPECT_TRUE((value).ok())
>
> In file included from
> /home/travis/build/xhochy/arrow/cpp/src/arrow/ipc/test-common.h:35:0,
> from
> /home/travis/build/xhochy/arrow/cpp/src/arrow/flight/test-util.cc:30:
> /home/travis/build/xhochy/arrow/cpp/src/arrow/testing/gtest_util.h:80:0:
> note: this is the location of the previous definition
> #define EXPECT_OK(expr) \
>
> cc1plus: all warnings being treated as errors{code}
> I would workaround this by renaming our {{EXPECT_OK}} to {{ARROW_EXPECT_OK}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ARROW-4538) [PYTHON] Remove index column from subschema in write_to_dataframe
[
https://issues.apache.org/jira/browse/ARROW-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn resolved ARROW-4538.
Resolution: Fixed
Fix Version/s: 0.13.0
Issue resolved by pull request 3744
[https://github.com/apache/arrow/pull/3744]
> [PYTHON] Remove index column from subschema in write_to_dataframe
> -
>
> Key: ARROW-4538
> URL: https://issues.apache.org/jira/browse/ARROW-4538
> Project: Apache Arrow
> Issue Type: Bug
> Components: Python
>Affects Versions: 0.12.0
>Reporter: Christian Thiel
>Priority: Major
> Labels: pull-request-available
> Fix For: 0.13.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When using {{pa.Table.from_pandas()}} with preserve_index=True and
> dataframe.index.name!=None the prefix {{__index_level_}} is not added to the
> respective schema name. This breaks {{write_to_dataset}} with active
> partition columns.
> {code}
> import pyarrow as pa
> import pyarrow.parquet as pq
> import os
> import shutil
> import pandas as pd
> import numpy as np
> PATH_PYARROW_MANUAL = '/tmp/pyarrow_manual.pa/'
> if os.path.exists(PATH_PYARROW_MANUAL):
> shutil.rmtree(PATH_PYARROW_MANUAL)
> os.mkdir(PATH_PYARROW_MANUAL)
> arrays = np.array([np.array([0, 1, 2]), np.array([3, 4]), np.nan, np.nan])
> df = pd.DataFrame([0, 0, 1, 1], columns=['partition_column'])
> df['arrays'] = pd.Series(arrays)
> df.index.name='ID'
> table = pa.Table.from_pandas(df, preserve_index=True)
> print(table.schema.names)
> pq.write_to_dataset(table, root_path=PATH_PYARROW_MANUAL,
> partition_cols=['partition_column'],
> preserve_index=True
>)
> {code}
> Removing {{df.index.name='ID'}} works. Also disabling {{partition_cols}} in
> {{write_to_dataset}} works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ARROW-4538) [PYTHON] Remove index column from subschema in write_to_dataframe
[
https://issues.apache.org/jira/browse/ARROW-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn reassigned ARROW-4538:
--
Assignee: Christian Thiel
> [PYTHON] Remove index column from subschema in write_to_dataframe
> -
>
> Key: ARROW-4538
> URL: https://issues.apache.org/jira/browse/ARROW-4538
> Project: Apache Arrow
> Issue Type: Bug
> Components: Python
>Affects Versions: 0.12.0
>Reporter: Christian Thiel
>Assignee: Christian Thiel
>Priority: Major
> Labels: pull-request-available
> Fix For: 0.13.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When using {{pa.Table.from_pandas()}} with preserve_index=True and
> dataframe.index.name!=None the prefix {{__index_level_}} is not added to the
> respective schema name. This breaks {{write_to_dataset}} with active
> partition columns.
> {code}
> import pyarrow as pa
> import pyarrow.parquet as pq
> import os
> import shutil
> import pandas as pd
> import numpy as np
> PATH_PYARROW_MANUAL = '/tmp/pyarrow_manual.pa/'
> if os.path.exists(PATH_PYARROW_MANUAL):
> shutil.rmtree(PATH_PYARROW_MANUAL)
> os.mkdir(PATH_PYARROW_MANUAL)
> arrays = np.array([np.array([0, 1, 2]), np.array([3, 4]), np.nan, np.nan])
> df = pd.DataFrame([0, 0, 1, 1], columns=['partition_column'])
> df['arrays'] = pd.Series(arrays)
> df.index.name='ID'
> table = pa.Table.from_pandas(df, preserve_index=True)
> print(table.schema.names)
> pq.write_to_dataset(table, root_path=PATH_PYARROW_MANUAL,
> partition_cols=['partition_column'],
> preserve_index=True
>)
> {code}
> Removing {{df.index.name='ID'}} works. Also disabling {{partition_cols}} in
> {{write_to_dataset}} works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARROW-4786) [C++/Python] Support better parallelisation in manylinux1 base build
Uwe L. Korn created ARROW-4786: -- Summary: [C++/Python] Support better parallelisation in manylinux1 base build Key: ARROW-4786 URL: https://issues.apache.org/jira/browse/ARROW-4786 Project: Apache Arrow Issue Type: Task Components: C++, Packaging, Python Reporter: Uwe L. Korn Assignee: Uwe L. Korn Fix For: 0.13.0 Currently we're building some dependencies single-threaded but could build them with much higher parallelisation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ARROW-4822) [C++/Python] arrow::py::is_table segmentation fault on nullptr
[
https://issues.apache.org/jira/browse/ARROW-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn updated ARROW-4822:
---
Summary: [C++/Python] arrow::py::is_table segmentation fault on nullptr
(was: arrow::py::is_table segmentation fault on nullptr)
> [C++/Python] arrow::py::is_table segmentation fault on nullptr
> --
>
> Key: ARROW-4822
> URL: https://issues.apache.org/jira/browse/ARROW-4822
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
>Affects Versions: 0.12.1
>Reporter: Andreas
>Priority: Trivial
>
> Calling \{arrow::py::is_table} with a null pointer causes a segmentation
> fault; this should be caught.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ARROW-4822) [C++/Python] arrow::py::is_table segmentation fault on nullptr
[
https://issues.apache.org/jira/browse/ARROW-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn updated ARROW-4822:
---
Description: Calling {{arrow::py::is_table}} with a null pointer causes a
segmentation fault; this should be caught. (was: Calling
\{{arrow::py::is_table}} with a null pointer causes a segmentation fault; this
should be caught.)
> [C++/Python] arrow::py::is_table segmentation fault on nullptr
> --
>
> Key: ARROW-4822
> URL: https://issues.apache.org/jira/browse/ARROW-4822
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
>Affects Versions: 0.12.1
>Reporter: Andreas
>Priority: Trivial
> Fix For: 0.13.0
>
>
> Calling {{arrow::py::is_table}} with a null pointer causes a segmentation
> fault; this should be caught.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ARROW-4822) [C++/Python] arrow::py::is_table segmentation fault on nullptr
[
https://issues.apache.org/jira/browse/ARROW-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn updated ARROW-4822:
---
Component/s: Python
> [C++/Python] arrow::py::is_table segmentation fault on nullptr
> --
>
> Key: ARROW-4822
> URL: https://issues.apache.org/jira/browse/ARROW-4822
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, Python
>Affects Versions: 0.12.1
>Reporter: Andreas
>Priority: Trivial
> Fix For: 0.13.0
>
>
> Calling {{arrow::py::is_table}} with a null pointer causes a segmentation
> fault; this should be caught.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ARROW-4822) [C++/Python] arrow::py::is_table segmentation fault on nullptr
[
https://issues.apache.org/jira/browse/ARROW-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn updated ARROW-4822:
---
Fix Version/s: 0.13.0
> [C++/Python] arrow::py::is_table segmentation fault on nullptr
> --
>
> Key: ARROW-4822
> URL: https://issues.apache.org/jira/browse/ARROW-4822
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
>Affects Versions: 0.12.1
>Reporter: Andreas
>Priority: Trivial
> Fix For: 0.13.0
>
>
> Calling \{arrow::py::is_table} with a null pointer causes a segmentation
> fault; this should be caught.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ARROW-4822) [C++/Python] arrow::py::is_table segmentation fault on nullptr
[
https://issues.apache.org/jira/browse/ARROW-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn reassigned ARROW-4822:
--
Assignee: Uwe L. Korn
> [C++/Python] arrow::py::is_table segmentation fault on nullptr
> --
>
> Key: ARROW-4822
> URL: https://issues.apache.org/jira/browse/ARROW-4822
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, Python
>Affects Versions: 0.12.1
>Reporter: Andreas
>Assignee: Uwe L. Korn
>Priority: Trivial
> Fix For: 0.13.0
>
>
> Calling {{arrow::py::is_table}} with a null pointer causes a segmentation
> fault; this should be caught.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ARROW-4790) [Python/Packaging] Update manylinux docker image in crossbow task
[
https://issues.apache.org/jira/browse/ARROW-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn reassigned ARROW-4790:
--
Assignee: Krisztian Szucs
> [Python/Packaging] Update manylinux docker image in crossbow task
> -
>
> Key: ARROW-4790
> URL: https://issues.apache.org/jira/browse/ARROW-4790
> Project: Apache Arrow
> Issue Type: Task
> Components: Python
>Reporter: Krisztian Szucs
>Assignee: Krisztian Szucs
>Priority: Major
> Labels: pull-request-available
> Fix For: 0.13.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> to {{ARROW - 4778}} see
> https://github.com/apache/arrow/pull/3823#issuecomment-470129575
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ARROW-4790) [Python/Packaging] Update manylinux docker image in crossbow task
[
https://issues.apache.org/jira/browse/ARROW-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn resolved ARROW-4790.
Resolution: Fixed
Issue resolved by pull request 3830
[https://github.com/apache/arrow/pull/3830]
> [Python/Packaging] Update manylinux docker image in crossbow task
> -
>
> Key: ARROW-4790
> URL: https://issues.apache.org/jira/browse/ARROW-4790
> Project: Apache Arrow
> Issue Type: Task
> Components: Python
>Reporter: Krisztian Szucs
>Priority: Major
> Labels: pull-request-available
> Fix For: 0.13.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> to {{ARROW - 4778}} see
> https://github.com/apache/arrow/pull/3823#issuecomment-470129575
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ARROW-4822) [C++/Python] pyarrow.Table.equals segmentation fault on None
[
https://issues.apache.org/jira/browse/ARROW-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn updated ARROW-4822:
---
Summary: [C++/Python] pyarrow.Table.equals segmentation fault on None
(was: [C++/Python] arrow::py::is_table segmentation fault on nullptr)
> [C++/Python] pyarrow.Table.equals segmentation fault on None
>
>
> Key: ARROW-4822
> URL: https://issues.apache.org/jira/browse/ARROW-4822
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, Python
>Affects Versions: 0.12.1
>Reporter: Andreas
>Assignee: Uwe L. Korn
>Priority: Trivial
> Fix For: 0.13.0
>
>
> Calling {{arrow::py::is_table}} with a null pointer causes a segmentation
> fault; this should be caught.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARROW-4822) [C++/Python] pyarrow.Table.equals segmentation fault on None
[
https://issues.apache.org/jira/browse/ARROW-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16789478#comment-16789478
]
Uwe L. Korn commented on ARROW-4822:
[~amerkel3] Updated the decription to what this segmentation fault actually
refers.
> [C++/Python] pyarrow.Table.equals segmentation fault on None
>
>
> Key: ARROW-4822
> URL: https://issues.apache.org/jira/browse/ARROW-4822
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, Python
>Affects Versions: 0.12.1
>Reporter: Andreas
>Assignee: Uwe L. Korn
>Priority: Trivial
> Fix For: 0.13.0
>
>
> Calling {{arrow::py::is_table}} with a null pointer causes a segmentation
> fault; this should be caught.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ARROW-4822) [C++/Python] pyarrow.Table.equals segmentation fault on None
[
https://issues.apache.org/jira/browse/ARROW-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn updated ARROW-4822:
---
Description: Calling {{pyarrow.Table.equals}} with {{None}} causes a
segmentation fault; this should be caught. (was: Calling
{{arrow::py::is_table}} with a null pointer causes a segmentation fault; this
should be caught.)
> [C++/Python] pyarrow.Table.equals segmentation fault on None
>
>
> Key: ARROW-4822
> URL: https://issues.apache.org/jira/browse/ARROW-4822
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, Python
>Affects Versions: 0.12.1
>Reporter: Andreas
>Assignee: Uwe L. Korn
>Priority: Trivial
> Fix For: 0.13.0
>
>
> Calling {{pyarrow.Table.equals}} with {{None}} causes a segmentation fault;
> this should be caught.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARROW-4747) [C++/PyPy] Add docker image to test against PyPy nightlies
[
https://issues.apache.org/jira/browse/ARROW-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16789661#comment-16789661
]
Uwe L. Korn commented on ARROW-4747:
Have a look at
[https://github.com/apache/arrow/blob/fd5e22158a7bf9f717db78b45579bc611374b007/docker-compose.yml#L146]
and
[https://github.com/apache/arrow/blob/fd5e22158a7bf9f717db78b45579bc611374b007/cpp/Dockerfile.ubuntu-xenial]
These are base dockerfiles that build against the system libraries. We would
need to additional flags to the CMake command to redirect it to using PyPy
nightlies instead of the system Python. Additionally, we also need to download
the PyPy nightly first in the Dockerfile.
Note that these files stem from the PR
[https://github.com/apache/arrow/pull/3688] and may not yet work on master.
> [C++/PyPy] Add docker image to test against PyPy nightlies
> --
>
> Key: ARROW-4747
> URL: https://issues.apache.org/jira/browse/ARROW-4747
> Project: Apache Arrow
> Issue Type: Task
> Components: C++, Python
>Reporter: Uwe L. Korn
>Priority: Major
> Labels: pypy
>
> It seems
> (https://bitbucket.org/pypy/pypy/issues/2842/running-pyarrow-on-pypy-segfaults#comment-50670536)
> that we are close to being able to run with PyPy. At the moment, we don't
> actively work on supporting PyPy but this would be a good start on providing
> feedback at what is still missing.
> To have such an image, one would need to fork one of the current test setups
> in {{docker-compose.yml}} that build with system libraries (e.g.
> ubuntu-xenial or debian-testing) and exchange the system Python with the PyPy
> nightly builds from http://buildbot.pypy.org/nightly/trunk/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARROW-3735) [Python] Proper error handling in _ensure_type
[
https://issues.apache.org/jira/browse/ARROW-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16789684#comment-16789684
]
Uwe L. Korn commented on ARROW-3735:
This is fixed in master but I add an explicit test for it.
> [Python] Proper error handling in _ensure_type
> --
>
> Key: ARROW-3735
> URL: https://issues.apache.org/jira/browse/ARROW-3735
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Python
>Reporter: Krisztian Szucs
>Assignee: Krisztian Szucs
>Priority: Major
> Fix For: 0.13.0
>
>
> We have multiple _ensure_type like functions, the in defined in array.pxi
> bypasses None which causes segfault in the following example:
> {code}
> pa.array([1, 2, 3]).cast(None)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ARROW-3735) [Python] Proper error handling in _ensure_type
[
https://issues.apache.org/jira/browse/ARROW-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn reassigned ARROW-3735:
--
Assignee: Uwe L. Korn (was: Krisztian Szucs)
> [Python] Proper error handling in _ensure_type
> --
>
> Key: ARROW-3735
> URL: https://issues.apache.org/jira/browse/ARROW-3735
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Python
>Reporter: Krisztian Szucs
>Assignee: Uwe L. Korn
>Priority: Major
> Fix For: 0.13.0
>
>
> We have multiple _ensure_type like functions, the in defined in array.pxi
> bypasses None which causes segfault in the following example:
> {code}
> pa.array([1, 2, 3]).cast(None)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARROW-4828) [Python] manylinux1 docker-compose context should be python/manylinux1
Uwe L. Korn created ARROW-4828:
--
Summary: [Python] manylinux1 docker-compose context should be
python/manylinux1
Key: ARROW-4828
URL: https://issues.apache.org/jira/browse/ARROW-4828
Project: Apache Arrow
Issue Type: Bug
Components: Python
Reporter: Uwe L. Korn
Assignee: Uwe L. Korn
Currently it doesn't find the {{scripts}} folder on running {{docker-compose
build python-manylinux1}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARROW-3150) [Python] Ship Flight-enabled Python wheels
[
https://issues.apache.org/jira/browse/ARROW-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790401#comment-16790401
]
Uwe L. Korn commented on ARROW-3150:
Once the CMake refactor is through and Flight builds on Windows, it should not
be hard to add this to the wheels. We should as always start with the Linux
wheels as they have the most sophisticated build infrastructure (and thus
adding a feature is simpler and more reliable).
> [Python] Ship Flight-enabled Python wheels
> --
>
> Key: ARROW-3150
> URL: https://issues.apache.org/jira/browse/ARROW-3150
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, FlightRPC
>Reporter: Wes McKinney
>Assignee: Uwe L. Korn
>Priority: Major
> Labels: flight
> Fix For: 0.13.0
>
>
> This may involve statically-linking (or bundling where shared libs makes
> sense) the various required dependencies with {{libarrow_flight.so}} in the
> manylinux1 wheel build
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ARROW-4416) [CI] Build gandiva in cpp docker image
[ https://issues.apache.org/jira/browse/ARROW-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn updated ARROW-4416: --- Fix Version/s: (was: 0.13.0) > [CI] Build gandiva in cpp docker image > -- > > Key: ARROW-4416 > URL: https://issues.apache.org/jira/browse/ARROW-4416 > Project: Apache Arrow > Issue Type: Bug >Reporter: Krisztian Szucs >Assignee: Uwe L. Korn >Priority: Major > > Currently Gandiva is not built, for the sake of completeness enable it by > default. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARROW-4416) [CI] Build gandiva in cpp docker image
[ https://issues.apache.org/jira/browse/ARROW-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn closed ARROW-4416. -- Resolution: Duplicate > [CI] Build gandiva in cpp docker image > -- > > Key: ARROW-4416 > URL: https://issues.apache.org/jira/browse/ARROW-4416 > Project: Apache Arrow > Issue Type: Bug >Reporter: Krisztian Szucs >Assignee: Uwe L. Korn >Priority: Major > > Currently Gandiva is not built, for the sake of completeness enable it by > default. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ARROW-3486) [CI] Add gandiva to the docker-compose setup
[ https://issues.apache.org/jira/browse/ARROW-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn updated ARROW-3486: --- Fix Version/s: (was: 0.13.0) > [CI] Add gandiva to the docker-compose setup > > > Key: ARROW-3486 > URL: https://issues.apache.org/jira/browse/ARROW-3486 > Project: Apache Arrow > Issue Type: Improvement > Components: Continuous Integration >Reporter: Krisztian Szucs >Assignee: Uwe L. Korn >Priority: Major > Labels: docker, gandiva > > Similarly like the cpp build > https://github.com/apache/arrow/blob/master/docker-compose.yml#L33 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARROW-3486) [CI] Add gandiva to the docker-compose setup
[ https://issues.apache.org/jira/browse/ARROW-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn closed ARROW-3486. -- Resolution: Duplicate > [CI] Add gandiva to the docker-compose setup > > > Key: ARROW-3486 > URL: https://issues.apache.org/jira/browse/ARROW-3486 > Project: Apache Arrow > Issue Type: Improvement > Components: Continuous Integration >Reporter: Krisztian Szucs >Assignee: Uwe L. Korn >Priority: Major > Labels: docker, gandiva > > Similarly like the cpp build > https://github.com/apache/arrow/blob/master/docker-compose.yml#L33 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARROW-4620) [C#] Add unit tests for "Types" in arrow/csharp
[ https://issues.apache.org/jira/browse/ARROW-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn resolved ARROW-4620. Resolution: Fixed Issue resolved by pull request 3662 [https://github.com/apache/arrow/pull/3662] > [C#] Add unit tests for "Types" in arrow/csharp > --- > > Key: ARROW-4620 > URL: https://issues.apache.org/jira/browse/ARROW-4620 > Project: Apache Arrow > Issue Type: Task > Components: C# >Reporter: Prashanth Govindarajan >Priority: Major > Labels: pull-request-available, test > Fix For: 0.13.0 > > Time Spent: 6h 50m > Remaining Estimate: 0h > > Arrow/cpp has tests for "Types" under type-test.cc. Port all applicable tests > to the csharp implementation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ARROW-4620) [C#] Add unit tests for "Types" in arrow/csharp
[ https://issues.apache.org/jira/browse/ARROW-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn reassigned ARROW-4620: -- Assignee: Prashanth Govindarajan > [C#] Add unit tests for "Types" in arrow/csharp > --- > > Key: ARROW-4620 > URL: https://issues.apache.org/jira/browse/ARROW-4620 > Project: Apache Arrow > Issue Type: Task > Components: C# >Reporter: Prashanth Govindarajan >Assignee: Prashanth Govindarajan >Priority: Major > Labels: pull-request-available, test > Fix For: 0.13.0 > > Time Spent: 7h > Remaining Estimate: 0h > > Arrow/cpp has tests for "Types" under type-test.cc. Port all applicable tests > to the csharp implementation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-4840) [C++] Persist CMake options in generated header
Uwe L. Korn created ARROW-4840: -- Summary: [C++] Persist CMake options in generated header Key: ARROW-4840 URL: https://issues.apache.org/jira/browse/ARROW-4840 Project: Apache Arrow Issue Type: Improvement Components: C++ Reporter: Uwe L. Korn Assignee: Uwe L. Korn Fix For: 0.14.0 (do this after we merged the CMake refactor) We should export all compile-time options like ARROW_WITH_ZSTD or ARROW_PARQUET in a header file so that other libraries depending on Arrow C++ can also respect that in their builds. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-4841) [C++] Persist CMake options in generated CMake config
Uwe L. Korn created ARROW-4841:
--
Summary: [C++] Persist CMake options in generated CMake config
Key: ARROW-4841
URL: https://issues.apache.org/jira/browse/ARROW-4841
Project: Apache Arrow
Issue Type: Improvement
Components: C++, Packaging
Reporter: Uwe L. Korn
Assignee: Uwe L. Korn
Fix For: 0.14.0
(do this after we merged the CMake refactor)
We should persist all options set during the CMake run also in
{{arrowConfig.cmake}} so that CMake projects that depend on Arrow also can
determine what they are able to provide.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARROW-4842) [C++] Persist CMake options in pkg-config files
[
https://issues.apache.org/jira/browse/ARROW-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790718#comment-16790718
]
Uwe L. Korn commented on ARROW-4842:
[~kou] Does this make sense? I have seen this in CMake configs and headers but
never have seen available features defined in a pkg-config file.
> [C++] Persist CMake options in pkg-config files
> ---
>
> Key: ARROW-4842
> URL: https://issues.apache.org/jira/browse/ARROW-4842
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, Packaging
>Reporter: Uwe L. Korn
>Assignee: Uwe L. Korn
>Priority: Major
> Fix For: 0.14.0
>
>
> Persist options like ARROW_WITH_ZSTD in {{arrow.pc}} so libraries can
> determine which features are available.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARROW-4842) [C++] Persist CMake options in pkg-config files
Uwe L. Korn created ARROW-4842:
--
Summary: [C++] Persist CMake options in pkg-config files
Key: ARROW-4842
URL: https://issues.apache.org/jira/browse/ARROW-4842
Project: Apache Arrow
Issue Type: Improvement
Components: C++, Packaging
Reporter: Uwe L. Korn
Assignee: Uwe L. Korn
Fix For: 0.14.0
Persist options like ARROW_WITH_ZSTD in {{arrow.pc}} so libraries can determine
which features are available.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARROW-4844) Static libarrow is missing vendored libdouble-conversion
[
https://issues.apache.org/jira/browse/ARROW-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790984#comment-16790984
]
Uwe L. Korn commented on ARROW-4844:
[~jeroenooms] This is the expected behaviour. I guess what you need for the R
bindings is an optional to bundle ALL static dependencies of {{libarrow.a}}
into it? For the Python wheels, we built {{libarrow.so}} with all static
dependencies included and then set the RPATH of the Python modules to
{{$ORIGIN}} to always pick up the correct {{libarrow.so}}. If that would be
possible for R, this would be a preferable solution from the build system side
(and also from interop side as you then could use the same {{libarrow.so}} for
Python and R).
> Static libarrow is missing vendored libdouble-conversion
>
>
> Key: ARROW-4844
> URL: https://issues.apache.org/jira/browse/ARROW-4844
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
>Affects Versions: 0.12.1
>Reporter: Jeroen
>Priority: Major
>
> When trying to statically link the R bindings to libarrow.a, I get linking
> errors which suggest that libdouble-conversion.a was not properly embedded in
> libarrow.a. This problem happens on both MacOS and Windows.
> Here is the arrow build log:
> https://ci.appveyor.com/project/jeroen/rtools-packages/builds/23015303/job/mtgl6rvfde502iu7
> {code}
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
>
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../lib/libarrow.a(cast.cc.obj):(.text+0x1c77c):
> undefined reference to
> `double_conversion::StringToDoubleConverter::StringToDouble(char const*, int,
> int*) const'
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
>
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../lib/libarrow.a(converter.cc.obj):(.text+0x5fda):
> undefined reference to
> `double_conversion::StringToDoubleConverter::StringToDouble(char const*, int,
> int*) const'
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
>
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../lib/libarrow.a(converter.cc.obj):(.text+0x6097):
> undefined reference to
> `double_conversion::StringToDoubleConverter::StringToDouble(char const*, int,
> int*) const'
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
>
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../lib/libarrow.a(converter.cc.obj):(.text+0x6589):
> undefined reference to
> `double_conversion::StringToDoubleConverter::StringToFloat(char const*, int,
> int*) const'
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
>
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../lib/libarrow.a(converter.cc.obj):(.text+0x6647):
> undefined reference to
> `double_conversion::StringToDoubleConverter::StringToFloat(char const*, int,
> int*) const'
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ARROW-4844) Static libarrow is missing vendored libdouble-conversion
[
https://issues.apache.org/jira/browse/ARROW-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn reassigned ARROW-4844:
--
Assignee: Uwe L. Korn
> Static libarrow is missing vendored libdouble-conversion
>
>
> Key: ARROW-4844
> URL: https://issues.apache.org/jira/browse/ARROW-4844
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
>Affects Versions: 0.12.1
>Reporter: Jeroen
>Assignee: Uwe L. Korn
>Priority: Major
>
> When trying to statically link the R bindings to libarrow.a, I get linking
> errors which suggest that libdouble-conversion.a was not properly embedded in
> libarrow.a. This problem happens on both MacOS and Windows.
> Here is the arrow build log:
> https://ci.appveyor.com/project/jeroen/rtools-packages/builds/23015303/job/mtgl6rvfde502iu7
> {code}
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
>
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../lib/libarrow.a(cast.cc.obj):(.text+0x1c77c):
> undefined reference to
> `double_conversion::StringToDoubleConverter::StringToDouble(char const*, int,
> int*) const'
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
>
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../lib/libarrow.a(converter.cc.obj):(.text+0x5fda):
> undefined reference to
> `double_conversion::StringToDoubleConverter::StringToDouble(char const*, int,
> int*) const'
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
>
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../lib/libarrow.a(converter.cc.obj):(.text+0x6097):
> undefined reference to
> `double_conversion::StringToDoubleConverter::StringToDouble(char const*, int,
> int*) const'
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
>
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../lib/libarrow.a(converter.cc.obj):(.text+0x6589):
> undefined reference to
> `double_conversion::StringToDoubleConverter::StringToFloat(char const*, int,
> int*) const'
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
>
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../lib/libarrow.a(converter.cc.obj):(.text+0x6647):
> undefined reference to
> `double_conversion::StringToDoubleConverter::StringToFloat(char const*, int,
> int*) const'
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARROW-4844) Static libarrow is missing vendored libdouble-conversion
[
https://issues.apache.org/jira/browse/ARROW-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791011#comment-16791011
]
Uwe L. Korn commented on ARROW-4844:
To solve this, it is probably best to build the {{libarrow.a}} for R then with
{{ARROW_DEPENDENCY_SOURCE=BUNDLED}} (see
[https://github.com/apache/arrow/pull/3688)] and add a new flag
{{ARROW_WHOLE_ARCHIVE}} that adds {{--whole-archive}} on the linker. I can have
a look after 3688 is merged.
> Static libarrow is missing vendored libdouble-conversion
>
>
> Key: ARROW-4844
> URL: https://issues.apache.org/jira/browse/ARROW-4844
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
>Affects Versions: 0.12.1
>Reporter: Jeroen
>Priority: Major
>
> When trying to statically link the R bindings to libarrow.a, I get linking
> errors which suggest that libdouble-conversion.a was not properly embedded in
> libarrow.a. This problem happens on both MacOS and Windows.
> Here is the arrow build log:
> https://ci.appveyor.com/project/jeroen/rtools-packages/builds/23015303/job/mtgl6rvfde502iu7
> {code}
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
>
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../lib/libarrow.a(cast.cc.obj):(.text+0x1c77c):
> undefined reference to
> `double_conversion::StringToDoubleConverter::StringToDouble(char const*, int,
> int*) const'
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
>
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../lib/libarrow.a(converter.cc.obj):(.text+0x5fda):
> undefined reference to
> `double_conversion::StringToDoubleConverter::StringToDouble(char const*, int,
> int*) const'
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
>
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../lib/libarrow.a(converter.cc.obj):(.text+0x6097):
> undefined reference to
> `double_conversion::StringToDoubleConverter::StringToDouble(char const*, int,
> int*) const'
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
>
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../lib/libarrow.a(converter.cc.obj):(.text+0x6589):
> undefined reference to
> `double_conversion::StringToDoubleConverter::StringToFloat(char const*, int,
> int*) const'
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
>
> C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../lib/libarrow.a(converter.cc.obj):(.text+0x6647):
> undefined reference to
> `double_conversion::StringToDoubleConverter::StringToFloat(char const*, int,
> int*) const'
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARROW-4849) [C++] Add docker-compose entry for testing Ubuntu Bionic build with system packages
Uwe L. Korn created ARROW-4849: -- Summary: [C++] Add docker-compose entry for testing Ubuntu Bionic build with system packages Key: ARROW-4849 URL: https://issues.apache.org/jira/browse/ARROW-4849 Project: Apache Arrow Issue Type: Improvement Components: C++, Packaging Reporter: Uwe L. Korn Assignee: Uwe L. Korn Fix For: 0.13.0 To better support people on Ubuntu and also show the missing things to get Arrow packaged into Fedora, add an entry to the docker-compose.yml that builds on Ubuntu -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ARROW-4842) [C++] Persist CMake options in pkg-config files
[
https://issues.apache.org/jira/browse/ARROW-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791551#comment-16791551
]
Uwe L. Korn commented on ARROW-4842:
Thanks for this input, will close this then as WONTFIX.
> [C++] Persist CMake options in pkg-config files
> ---
>
> Key: ARROW-4842
> URL: https://issues.apache.org/jira/browse/ARROW-4842
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, Packaging
>Reporter: Uwe L. Korn
>Assignee: Uwe L. Korn
>Priority: Major
> Fix For: 0.14.0
>
>
> Persist options like ARROW_WITH_ZSTD in {{arrow.pc}} so libraries can
> determine which features are available.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (ARROW-4842) [C++] Persist CMake options in pkg-config files
[
https://issues.apache.org/jira/browse/ARROW-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn closed ARROW-4842.
--
Resolution: Won't Fix
Fix Version/s: (was: 0.14.0)
> [C++] Persist CMake options in pkg-config files
> ---
>
> Key: ARROW-4842
> URL: https://issues.apache.org/jira/browse/ARROW-4842
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, Packaging
>Reporter: Uwe L. Korn
>Assignee: Uwe L. Korn
>Priority: Major
>
> Persist options like ARROW_WITH_ZSTD in {{arrow.pc}} so libraries can
> determine which features are available.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARROW-4857) [C++/Python/CI] docker-compose in manylinux1 crossbow jobs too old
Uwe L. Korn created ARROW-4857:
--
Summary: [C++/Python/CI] docker-compose in manylinux1 crossbow
jobs too old
Key: ARROW-4857
URL: https://issues.apache.org/jira/browse/ARROW-4857
Project: Apache Arrow
Issue Type: Bug
Components: C++, Continuous Integration, Packaging, Python
Reporter: Uwe L. Korn
Assignee: Uwe L. Korn
Fix For: 0.13.0
Nightlies are failing with {{Version in "./docker-compose.yml" is
unsupported.}}
https://travis-ci.org/kszucs/crossbow/builds/505676630?utm_source=github_status&utm_medium=notification
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ARROW-4776) [C++] DictionaryBuilder should support bootstrapping from an existing dict type
[ https://issues.apache.org/jira/browse/ARROW-4776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn reassigned ARROW-4776: -- Assignee: Benjamin Kietzman > [C++] DictionaryBuilder should support bootstrapping from an existing dict > type > --- > > Key: ARROW-4776 > URL: https://issues.apache.org/jira/browse/ARROW-4776 > Project: Apache Arrow > Issue Type: Improvement > Components: C++ >Reporter: Francois Saint-Jacques >Assignee: Benjamin Kietzman >Priority: Minor > Labels: pull-request-available > Fix For: 0.13.0 > > Time Spent: 50m > Remaining Estimate: 0h > > This would mean adding a new DictionaryBuilder constructor that receives a > dictionary type and performs a lazy deep copy if there's any modification. > We'll have to investigate how this translate in API ergonomics. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARROW-4776) [C++] DictionaryBuilder should support bootstrapping from an existing dict type
[ https://issues.apache.org/jira/browse/ARROW-4776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn resolved ARROW-4776. Resolution: Fixed Fix Version/s: (was: 0.14.0) 0.13.0 Issue resolved by pull request 3867 [https://github.com/apache/arrow/pull/3867] > [C++] DictionaryBuilder should support bootstrapping from an existing dict > type > --- > > Key: ARROW-4776 > URL: https://issues.apache.org/jira/browse/ARROW-4776 > Project: Apache Arrow > Issue Type: Improvement > Components: C++ >Reporter: Francois Saint-Jacques >Priority: Minor > Labels: pull-request-available > Fix For: 0.13.0 > > Time Spent: 40m > Remaining Estimate: 0h > > This would mean adding a new DictionaryBuilder constructor that receives a > dictionary type and performs a lazy deep copy if there's any modification. > We'll have to investigate how this translate in API ergonomics. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-4866) [C++] zstd ExternalProject failing on Windows
Uwe L. Korn created ARROW-4866: -- Summary: [C++] zstd ExternalProject failing on Windows Key: ARROW-4866 URL: https://issues.apache.org/jira/browse/ARROW-4866 Project: Apache Arrow Issue Type: Bug Components: C++, Packaging Reporter: Uwe L. Korn Fix For: 0.13.0 After [https://github.com/apache/arrow/pull/3885|https://github.com/apache/arrow/pull/3885,] the zstd ExternalProject is failing in the Windows builds, see [https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/23063072/job/bd0gom16atlkddtx] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ARROW-4857) [C++/Python/CI] docker-compose in manylinux1 crossbow jobs too old
[
https://issues.apache.org/jira/browse/ARROW-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792757#comment-16792757
]
Uwe L. Korn commented on ARROW-4857:
Resolved in PR https://github.com/apache/arrow/pull/3897
> [C++/Python/CI] docker-compose in manylinux1 crossbow jobs too old
> --
>
> Key: ARROW-4857
> URL: https://issues.apache.org/jira/browse/ARROW-4857
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, Continuous Integration, Packaging, Python
>Reporter: Uwe L. Korn
>Assignee: Uwe L. Korn
>Priority: Major
> Fix For: 0.13.0
>
>
> Nightlies are failing with {{Version in "./docker-compose.yml" is
> unsupported.}}
> https://travis-ci.org/kszucs/crossbow/builds/505676630?utm_source=github_status&utm_medium=notification
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ARROW-4383) [C++] Use the CMake's standard find features
[
https://issues.apache.org/jira/browse/ARROW-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn resolved ARROW-4383.
Resolution: Fixed
Assignee: Uwe L. Korn
Fix Version/s: (was: 0.14.0)
0.13.0
Resolved by PR https://github.com/apache/arrow/pull/3688
> [C++] Use the CMake's standard find features
>
>
> Key: ARROW-4383
> URL: https://issues.apache.org/jira/browse/ARROW-4383
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
>Reporter: Kouhei Sutou
>Assignee: Uwe L. Korn
>Priority: Major
> Fix For: 0.13.0
>
>
> From https://github.com/apache/arrow/pull/3469#discussion_r250862542
> We implement our custom find codes to find libraries by
> {{find_library()}}/{{find_path()}} with {{NO_DEFAULT_PATH}}. So we need to
> handle {{lib64/}} (on Red Hat) and {{lib/x86_64-linux-gnu/}} (on Debian)
> paths manually.
> If we use the CMake's standard find features such as {{CMAKE_PREFIX_PATH}}
> https://cmake.org/cmake/help/v3.13/variable/CMAKE_PREFIX_PATH.html#variable:CMAKE_PREFIX_PATH
> , we can remove our custom find codes.
> CMake has package specific find path feature by {{ 3.12. It's equivalent of our {{ https://cmake.org/cmake/help/v3.12/command/find_library.html
> {quote}
> If called from within a find module loaded by
> {{find_package()}}, search prefixes unique to the current
> package being found. Specifically look in the {{_ROOT}} CMake
> variable and the {{_ROOT}} environment variable. The package
> root variables are maintained as a stack so if called from nested find
> modules, root paths from the parent’s find module will be searched after
> paths from the current module, i.e. {{_ROOT}},
> {{ENV\{_ROOT}}}, {{_ROOT}},
> {{ENV\{_ROOT}}}, etc.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ARROW-4609) [C++] Use google benchmark from toolchain
[ https://issues.apache.org/jira/browse/ARROW-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn resolved ARROW-4609. Resolution: Fixed Resolved by PR https://github.com/apache/arrow/pull/3688 > [C++] Use google benchmark from toolchain > - > > Key: ARROW-4609 > URL: https://issues.apache.org/jira/browse/ARROW-4609 > Project: Apache Arrow > Issue Type: Improvement > Components: C++, Packaging >Reporter: Uwe L. Korn >Assignee: Uwe L. Korn >Priority: Major > Labels: pull-request-available > Fix For: 0.13.0 > > Time Spent: 2h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARROW-4732) [C++] Add docker-compose entry for testing Debian Testing build with system packages
[ https://issues.apache.org/jira/browse/ARROW-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn resolved ARROW-4732. Resolution: Fixed Resolved by PR https://github.com/apache/arrow/pull/3688 > [C++] Add docker-compose entry for testing Debian Testing build with system > packages > > > Key: ARROW-4732 > URL: https://issues.apache.org/jira/browse/ARROW-4732 > Project: Apache Arrow > Issue Type: Improvement > Components: C++, Packaging >Reporter: Uwe L. Korn >Assignee: Uwe L. Korn >Priority: Major > Fix For: 0.13.0 > > > To better support people on Fedora and also show the missing things to get > Arrow packaged into Debian, add an entry to the docker-compose.yml that > builds on Debian Testing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARROW-4730) [C++] Add docker-compose entry for testing Fedora build with system packages
[ https://issues.apache.org/jira/browse/ARROW-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn resolved ARROW-4730. Resolution: Fixed Resolved by PR https://github.com/apache/arrow/pull/3688 > [C++] Add docker-compose entry for testing Fedora build with system packages > > > Key: ARROW-4730 > URL: https://issues.apache.org/jira/browse/ARROW-4730 > Project: Apache Arrow > Issue Type: Improvement > Components: C++, Packaging >Reporter: Uwe L. Korn >Assignee: Uwe L. Korn >Priority: Major > Fix For: 0.13.0 > > > To better support people on Fedora and also show the missing things to get > Arrow packaged into Fedora, add an entry to the docker-compose.yml that > builds on Fedora -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARROW-4733) [C++] Add CI entry that builds without the conda-forge toolchain but with system packages
[ https://issues.apache.org/jira/browse/ARROW-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn resolved ARROW-4733. Resolution: Fixed Resolved by PR https://github.com/apache/arrow/pull/3688 > [C++] Add CI entry that builds without the conda-forge toolchain but with > system packages > - > > Key: ARROW-4733 > URL: https://issues.apache.org/jira/browse/ARROW-4733 > Project: Apache Arrow > Issue Type: Improvement > Components: C++, Continuous Integration >Reporter: Uwe L. Korn >Assignee: Uwe L. Korn >Priority: Major > Fix For: 0.13.0 > > > Instead of using the conda-forge toolchain to provide parts of the > dependencies but then compile with a system compiler, utilise the system > packages to build and test the C++ implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARROW-4750) [C++] RapidJSON triggers Wclass-memaccess on GCC 8+
[
https://issues.apache.org/jira/browse/ARROW-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn resolved ARROW-4750.
Resolution: Fixed
Resolved by PR https://github.com/apache/arrow/pull/3688
> [C++] RapidJSON triggers Wclass-memaccess on GCC 8+
> ---
>
> Key: ARROW-4750
> URL: https://issues.apache.org/jira/browse/ARROW-4750
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
>Reporter: Uwe L. Korn
>Assignee: Uwe L. Korn
>Priority: Major
> Fix For: 0.13.0
>
>
> With GCC 8, we get build errors with RapidJSON due to {{-Wclass-memaccess}}.
> This is fixed in https://github.com/Tencent/rapidjson/pull/1323 . We should
> update our external project dependency to include this fix.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ARROW-4849) [C++] Add docker-compose entry for testing Ubuntu Bionic build with system packages
[ https://issues.apache.org/jira/browse/ARROW-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn resolved ARROW-4849. Resolution: Fixed Resolved by PR https://github.com/apache/arrow/pull/3688 > [C++] Add docker-compose entry for testing Ubuntu Bionic build with system > packages > --- > > Key: ARROW-4849 > URL: https://issues.apache.org/jira/browse/ARROW-4849 > Project: Apache Arrow > Issue Type: Improvement > Components: C++, Packaging >Reporter: Uwe L. Korn >Assignee: Uwe L. Korn >Priority: Major > Fix For: 0.13.0 > > > To better support people on Ubuntu and also show the missing things to get > Arrow packaged into Fedora, add an entry to the docker-compose.yml that > builds on Ubuntu -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARROW-4617) [C++] Support double-conversion<3.1
[
https://issues.apache.org/jira/browse/ARROW-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn resolved ARROW-4617.
Resolution: Fixed
Resolved by PR https://github.com/apache/arrow/pull/3688
> [C++] Support double-conversion<3.1
> ---
>
> Key: ARROW-4617
> URL: https://issues.apache.org/jira/browse/ARROW-4617
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, Packaging, R
>Reporter: Uwe L. Korn
>Assignee: Uwe L. Korn
>Priority: Major
> Fix For: 0.13.0
>
>
> At the moment, we require {{double-conversion>=3.1}} but distributions are
> all mostly on 2.1 or 3.0. We should support them
> Nice side-effect is that {{double-conversion}} is not good in updating their
> version number. So thus 3.0 report itself as 2.0.1 and 3.1.x as 3.0 in the
> CMake definitions. Thus we cannot rely on their version number reporting for
> detecting the version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ARROW-4857) [C++/Python/CI] docker-compose in manylinux1 crossbow jobs too old
[
https://issues.apache.org/jira/browse/ARROW-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn resolved ARROW-4857.
Resolution: Fixed
> [C++/Python/CI] docker-compose in manylinux1 crossbow jobs too old
> --
>
> Key: ARROW-4857
> URL: https://issues.apache.org/jira/browse/ARROW-4857
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, Continuous Integration, Packaging, Python
>Reporter: Uwe L. Korn
>Assignee: Uwe L. Korn
>Priority: Major
> Fix For: 0.13.0
>
>
> Nightlies are failing with {{Version in "./docker-compose.yml" is
> unsupported.}}
> https://travis-ci.org/kszucs/crossbow/builds/505676630?utm_source=github_status&utm_medium=notification
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ARROW-4614) [C++/CI] Activate flight build in ci/docker_build_cpp.sh
[ https://issues.apache.org/jira/browse/ARROW-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn resolved ARROW-4614. Resolution: Fixed Resolved by PR https://github.com/apache/arrow/pull/3688 > [C++/CI] Activate flight build in ci/docker_build_cpp.sh > > > Key: ARROW-4614 > URL: https://issues.apache.org/jira/browse/ARROW-4614 > Project: Apache Arrow > Issue Type: Improvement > Components: C++, Continuous Integration, FlightRPC >Reporter: Uwe L. Korn >Assignee: Uwe L. Korn >Priority: Major > Fix For: 0.13.0 > > > This is currently not build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARROW-4644) [C++/Docker] Build Gandiva in the docker containers
[ https://issues.apache.org/jira/browse/ARROW-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn resolved ARROW-4644. Resolution: Fixed Resolved by PR https://github.com/apache/arrow/pull/3688 > [C++/Docker] Build Gandiva in the docker containers > --- > > Key: ARROW-4644 > URL: https://issues.apache.org/jira/browse/ARROW-4644 > Project: Apache Arrow > Issue Type: Improvement > Components: C++ - Gandiva >Reporter: Krisztian Szucs >Assignee: Uwe L. Korn >Priority: Major > Labels: docker > Fix For: 0.13.0 > > > Install LLVM dependency and enable it: > https://github.com/apache/arrow/pull/3484/files#diff-1f2ebc25efb8f1e6646cbd31ce2f34f4R51 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARROW-4731) [C++] Add docker-compose entry for testing Ubuntu Xenial build with system packages
[ https://issues.apache.org/jira/browse/ARROW-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn resolved ARROW-4731. Resolution: Fixed Resolved by PR https://github.com/apache/arrow/pull/3688 > [C++] Add docker-compose entry for testing Ubuntu Xenial build with system > packages > --- > > Key: ARROW-4731 > URL: https://issues.apache.org/jira/browse/ARROW-4731 > Project: Apache Arrow > Issue Type: Improvement > Components: C++, Packaging >Reporter: Uwe L. Korn >Assignee: Uwe L. Korn >Priority: Major > Fix For: 0.13.0 > > > To better support people on Ubuntu and also show the missing things to get > Arrow packaged into Fedora, add an entry to the docker-compose.yml that > builds on Ubuntu -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARROW-4485) [CI] Determine maintenance approach to pinned conda-forge binutils package
[ https://issues.apache.org/jira/browse/ARROW-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn resolved ARROW-4485. Resolution: Fixed Fix Version/s: 0.13.0 Resolved by PR https://github.com/apache/arrow/pull/3688 > [CI] Determine maintenance approach to pinned conda-forge binutils package > -- > > Key: ARROW-4485 > URL: https://issues.apache.org/jira/browse/ARROW-4485 > Project: Apache Arrow > Issue Type: Improvement > Components: C++ >Reporter: Wes McKinney >Assignee: Uwe L. Korn >Priority: Major > Fix For: 0.13.0 > > > In ARROW-4469 https://github.com/apache/arrow/pull/3554 we pinned binutils > 2.31 because the 2.32 release broke builds on Ubuntu Xenial. We aren't sure > what will be our path going forward to rely on the conda-forge toolchain > because of this -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARROW-4760) [C++] protobuf 3.7 defines EXPECT_OK that clashes with Arrow's macro
[
https://issues.apache.org/jira/browse/ARROW-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn resolved ARROW-4760.
Resolution: Fixed
Resolved by PR https://github.com/apache/arrow/pull/3688
> [C++] protobuf 3.7 defines EXPECT_OK that clashes with Arrow's macro
>
>
> Key: ARROW-4760
> URL: https://issues.apache.org/jira/browse/ARROW-4760
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
>Reporter: Uwe L. Korn
>Assignee: Uwe L. Korn
>Priority: Major
> Fix For: 0.13.0
>
>
> This fails for me with the following error:
> {code:java}
> /home/travis/build/xhochy/arrow/cpp/src/arrow/flight/test-util.cc
> In file included from
> /home/travis/build/xhochy/arrow/cpp-toolchain/include/google/protobuf/util/type_resolver.h:39:0,
> from
> /home/travis/build/xhochy/arrow/cpp-toolchain/include/google/protobuf/util/json_util.h:37,
> from
> /home/travis/build/xhochy/arrow/cpp-toolchain/include/grpcpp/impl/codegen/config_protobuf.h:70,
> from
> /home/travis/build/xhochy/arrow/cpp/src/arrow/flight/customize_protobuf.h:23,
> from
> /home/travis/build/xhochy/arrow/cpp/src/arrow/flight/protocol-internal.h:20,
> from
> /home/travis/build/xhochy/arrow/cpp/src/arrow/flight/internal.h:23,
> from
> /home/travis/build/xhochy/arrow/cpp/src/arrow/flight/test-util.cc:35:
> /home/travis/build/xhochy/arrow/cpp-toolchain/include/google/protobuf/stubs/status.h:111:0:
> error: "EXPECT_OK" redefined [-Werror]
> #define EXPECT_OK(value) EXPECT_TRUE((value).ok())
>
> In file included from
> /home/travis/build/xhochy/arrow/cpp/src/arrow/ipc/test-common.h:35:0,
> from
> /home/travis/build/xhochy/arrow/cpp/src/arrow/flight/test-util.cc:30:
> /home/travis/build/xhochy/arrow/cpp/src/arrow/testing/gtest_util.h:80:0:
> note: this is the location of the previous definition
> #define EXPECT_OK(expr) \
>
> cc1plus: all warnings being treated as errors{code}
> I would workaround this by renaming our {{EXPECT_OK}} to {{ARROW_EXPECT_OK}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ARROW-4873) [C++] ARROW_DEPENDENCY_SOURCE should not be overridden to CONDA if ARROW_PACKAGE_PREFIX is set by user
[
https://issues.apache.org/jira/browse/ARROW-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn reassigned ARROW-4873:
--
Assignee: Uwe L. Korn (was: Wes McKinney)
> [C++] ARROW_DEPENDENCY_SOURCE should not be overridden to CONDA if
> ARROW_PACKAGE_PREFIX is set by user
> --
>
> Key: ARROW-4873
> URL: https://issues.apache.org/jira/browse/ARROW-4873
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
>Reporter: Wes McKinney
>Assignee: Uwe L. Korn
>Priority: Major
> Fix For: 0.13.0
>
>
> I use conda to manage Python dependencies but keep my C++ toolchain in a
> separate directory. This organizational scheme is incompatible with the new
> options after the CMake refactor
> I think if you pass {{-DARROW_PREFIX_PATH=$MY_CPP_TOOLCHAIN}} then this
> should not be overridden with {{$CONDA_PREFIX}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ARROW-4761) [C++] Support zstandard<1
[ https://issues.apache.org/jira/browse/ARROW-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn updated ARROW-4761: --- Fix Version/s: (was: 0.13.0) 0.14.0 > [C++] Support zstandard<1 > - > > Key: ARROW-4761 > URL: https://issues.apache.org/jira/browse/ARROW-4761 > Project: Apache Arrow > Issue Type: Improvement > Components: C++, Packaging >Reporter: Uwe L. Korn >Assignee: Uwe L. Korn >Priority: Major > Fix For: 0.14.0 > > > To support building with as many system packages as possible on Ubuntu, we > should support building with zstandard 0.5.1 which is the one available on > Ubuntu Xenial. Given the size of our current code for Zstandard, this seems > feasible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ARROW-4884) [C++] conda-forge thrift-cpp package not available via pkg-config or cmake
[
https://issues.apache.org/jira/browse/ARROW-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793470#comment-16793470
]
Uwe L. Korn commented on ARROW-4884:
Actually
[https://github.com/apache/arrow/blob/548e1949d527717d7821a4ab2f09ff7c39882152/cpp/cmake_modules/FindThrift.cmake#L65]
should print a small message indicating that {{pkg-config}} has not found
Thrift (this message only appears when you have {{pkg-config}} installed).
> [C++] conda-forge thrift-cpp package not available via pkg-config or cmake
> --
>
> Key: ARROW-4884
> URL: https://issues.apache.org/jira/browse/ARROW-4884
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
>Reporter: Wes McKinney
>Priority: Major
> Fix For: 0.14.0
>
>
> Artifact of CMake refactor
> I opened https://github.com/conda-forge/thrift-cpp-feedstock/issues/35 about
> investigating why Thrift does not export the correct files
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARROW-4879) [C++] cmake can't use conda's flatbuffers
[
https://issues.apache.org/jira/browse/ARROW-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793475#comment-16793475
]
Uwe L. Korn commented on ARROW-4879:
Opened an issue with Anaconda:
https://github.com/ContinuumIO/anaconda-issues/issues/10731
> [C++] cmake can't use conda's flatbuffers
> -
>
> Key: ARROW-4879
> URL: https://issues.apache.org/jira/browse/ARROW-4879
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
>Reporter: Benjamin Kietzman
>Assignee: Benjamin Kietzman
>Priority: Minor
> Fix For: 0.13.0
>
>
> I'm using conda's flatbuffers, but after the cmake refactor I get the
> following error:
> {code}
> $ uname --all
> Linux pop-os 4.18.0-15-generic #16pop0~18.04.1-Ubuntu SMP Thu Feb 21 16:15:23
> UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
> $ conda list | grep -E 'flatbuffers|cmake'
> cmake 3.12.2 h52cb24c_0
> flatbuffers 1.7.1hf484d3e_0
> $ cmake -DCMAKE_BUILD_TYPE=Release -DARROW_PARQUET=on
> -DBUILD_WARNING_LEVEL=CHECKIN -DCMAKE_EXPORT_COMPILE_COMMANDS=on -GNinja ../..
> ...
> -- Building using CMake version: 3.12.2
> -- The C compiler identification is Clang 7.0.1
> -- The CXX compiler identification is Clang 7.0.0
> -- Check for working C compiler:
> /home/bkietz/miniconda3/envs/pyarrow-dev/bin/clang-7
> -- Check for working C compiler:
> /home/bkietz/miniconda3/envs/pyarrow-dev/bin/clang-7 -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/clang++-7
> -- Check for working CXX compiler: /usr/bin/clang++-7 -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Arrow version: 0.13.0 (full: '0.13.0-SNAPSHOT')
> -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
> -- clang-tidy not found
> -- clang-format found at /usr/bin/clang-format-7
> -- infer not found
> -- Found PythonInterp: /home/bkietz/miniconda3/envs/pyarrow-dev/bin/python
> (found version "3.6.8")
> -- Found cpplint executable at /home/bkietz/arrow/cpp/build-support/cpplint.py
> -- Compiler command: env LANG=C /usr/bin/clang++-7 -v
> -- Compiler version: clang version 7.0.0-3~ubuntu0.18.04.1
> (tags/RELEASE_700/final)
> Target: x86_64-pc-linux-gnu
> Thread model: posix
> InstalledDir: /usr/bin
> Found candidate GCC installation: /usr/bin/../lib/gcc/i686-linux-gnu/8
> Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.8
> Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.8.5
> Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/7
> Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/7.3.0
> Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/8
> Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/8
> Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8
> Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8.5
> Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7
> Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7.3.0
> Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/8
> Selected GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/7.3.0
> Candidate multilib: .;@m64
> Selected multilib: .;@m64
> -- Compiler id: Clang
> Selected compiler clang 7.0
> -- Performing Test CXX_SUPPORTS_SSE4_2
> -- Performing Test CXX_SUPPORTS_SSE4_2 - Success
> -- Performing Test CXX_SUPPORTS_ALTIVEC
> -- Performing Test CXX_SUPPORTS_ALTIVEC - Success
> -- Performing Test CXX_SUPPORTS_ARMCRC
> -- Performing Test CXX_SUPPORTS_ARMCRC - Failed
> -- Arrow build warning level: CHECKIN
> Using ld linker
> Configured for RELEASE build (set with cmake
> -DCMAKE_BUILD_TYPE={release,debug,...})
> -- Build Type: RELEASE
> -- Using CONDA approach to find dependencies
> -- Using CONDA_PREFIX: /home/bkietz/miniconda3/envs/pyarrow-dev
> -- Setting (unset) dependency *_ROOT variables:
> /home/bkietz/miniconda3/envs/pyarrow-dev
> -- BOOST_VERSION: 1.67.0
> -- BROTLI_VERSION: v0.6.0
> -- BZIP2_VERSION: 1.0.6
> -- CARES_VERSION: 1.15.0
> -- DOUBLE_CONVERSION_VERSION: v3.1.1
> -- FLATBUFFERS_VERSION: v1.10.0
> -- GBENCHMARK_VERSION: v1.4.1
> -- GFLAGS_VERSION: v2.2.0
> -- GLOG_VERSION: v0.3.5
> -- GRPC_VERSION: v1.18.0
> -- GTEST_VERSION: 1.8.1
> -- JEMALLOC_VERSION: 17c897976c60b0e6e4f4a365c751027244dada7a
> -- LZ4_VERSION: v1.8.3
> -- ORC_VERSION: 1.5.4
> -- PROTOBUF_VERSION: v3.6.1
> -- RAPIDJSON_VERSION: 2bbd33b33217ff4a73434ebf10cdac41e2ef5e34
> -- RE2_VERSION: 2018-10-01
> --
[jira] [Created] (ARROW-4888) [C++/Python] Test build with conda's defaults channel
Uwe L. Korn created ARROW-4888:
--
Summary: [C++/Python] Test build with conda's defaults channel
Key: ARROW-4888
URL: https://issues.apache.org/jira/browse/ARROW-4888
Project: Apache Arrow
Issue Type: Bug
Components: C++, Packaging, Python
Reporter: Uwe L. Korn
Assignee: Uwe L. Korn
Fix For: 0.14.0
We mostly use {{conda-forge}} as the developers of Arrow but also have some
users that would build with packages from {{defaults}}. As the versions of
packages is a bit behind (and sometimes the contents are different), we should
also have a docker-test for this channel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ARROW-4888) [C++/Python] Test build with conda's defaults channel
[
https://issues.apache.org/jira/browse/ARROW-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn reassigned ARROW-4888:
--
Assignee: (was: Uwe L. Korn)
> [C++/Python] Test build with conda's defaults channel
> -
>
> Key: ARROW-4888
> URL: https://issues.apache.org/jira/browse/ARROW-4888
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, Packaging, Python
>Reporter: Uwe L. Korn
>Priority: Major
> Fix For: 0.14.0
>
>
> We mostly use {{conda-forge}} as the developers of Arrow but also have some
> users that would build with packages from {{defaults}}. As the versions of
> packages is a bit behind (and sometimes the contents are different), we
> should also have a docker-test for this channel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARROW-4879) [C++] cmake can't use conda's flatbuffers
[
https://issues.apache.org/jira/browse/ARROW-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793476#comment-16793476
]
Uwe L. Korn commented on ARROW-4879:
Also opened https://issues.apache.org/jira/browse/ARROW-4888 so that we test
building with defaults.
> [C++] cmake can't use conda's flatbuffers
> -
>
> Key: ARROW-4879
> URL: https://issues.apache.org/jira/browse/ARROW-4879
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
>Reporter: Benjamin Kietzman
>Assignee: Benjamin Kietzman
>Priority: Minor
> Fix For: 0.13.0
>
>
> I'm using conda's flatbuffers, but after the cmake refactor I get the
> following error:
> {code}
> $ uname --all
> Linux pop-os 4.18.0-15-generic #16pop0~18.04.1-Ubuntu SMP Thu Feb 21 16:15:23
> UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
> $ conda list | grep -E 'flatbuffers|cmake'
> cmake 3.12.2 h52cb24c_0
> flatbuffers 1.7.1hf484d3e_0
> $ cmake -DCMAKE_BUILD_TYPE=Release -DARROW_PARQUET=on
> -DBUILD_WARNING_LEVEL=CHECKIN -DCMAKE_EXPORT_COMPILE_COMMANDS=on -GNinja ../..
> ...
> -- Building using CMake version: 3.12.2
> -- The C compiler identification is Clang 7.0.1
> -- The CXX compiler identification is Clang 7.0.0
> -- Check for working C compiler:
> /home/bkietz/miniconda3/envs/pyarrow-dev/bin/clang-7
> -- Check for working C compiler:
> /home/bkietz/miniconda3/envs/pyarrow-dev/bin/clang-7 -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/clang++-7
> -- Check for working CXX compiler: /usr/bin/clang++-7 -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Arrow version: 0.13.0 (full: '0.13.0-SNAPSHOT')
> -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
> -- clang-tidy not found
> -- clang-format found at /usr/bin/clang-format-7
> -- infer not found
> -- Found PythonInterp: /home/bkietz/miniconda3/envs/pyarrow-dev/bin/python
> (found version "3.6.8")
> -- Found cpplint executable at /home/bkietz/arrow/cpp/build-support/cpplint.py
> -- Compiler command: env LANG=C /usr/bin/clang++-7 -v
> -- Compiler version: clang version 7.0.0-3~ubuntu0.18.04.1
> (tags/RELEASE_700/final)
> Target: x86_64-pc-linux-gnu
> Thread model: posix
> InstalledDir: /usr/bin
> Found candidate GCC installation: /usr/bin/../lib/gcc/i686-linux-gnu/8
> Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.8
> Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.8.5
> Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/7
> Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/7.3.0
> Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/8
> Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/8
> Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8
> Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8.5
> Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7
> Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7.3.0
> Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/8
> Selected GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/7.3.0
> Candidate multilib: .;@m64
> Selected multilib: .;@m64
> -- Compiler id: Clang
> Selected compiler clang 7.0
> -- Performing Test CXX_SUPPORTS_SSE4_2
> -- Performing Test CXX_SUPPORTS_SSE4_2 - Success
> -- Performing Test CXX_SUPPORTS_ALTIVEC
> -- Performing Test CXX_SUPPORTS_ALTIVEC - Success
> -- Performing Test CXX_SUPPORTS_ARMCRC
> -- Performing Test CXX_SUPPORTS_ARMCRC - Failed
> -- Arrow build warning level: CHECKIN
> Using ld linker
> Configured for RELEASE build (set with cmake
> -DCMAKE_BUILD_TYPE={release,debug,...})
> -- Build Type: RELEASE
> -- Using CONDA approach to find dependencies
> -- Using CONDA_PREFIX: /home/bkietz/miniconda3/envs/pyarrow-dev
> -- Setting (unset) dependency *_ROOT variables:
> /home/bkietz/miniconda3/envs/pyarrow-dev
> -- BOOST_VERSION: 1.67.0
> -- BROTLI_VERSION: v0.6.0
> -- BZIP2_VERSION: 1.0.6
> -- CARES_VERSION: 1.15.0
> -- DOUBLE_CONVERSION_VERSION: v3.1.1
> -- FLATBUFFERS_VERSION: v1.10.0
> -- GBENCHMARK_VERSION: v1.4.1
> -- GFLAGS_VERSION: v2.2.0
> -- GLOG_VERSION: v0.3.5
> -- GRPC_VERSION: v1.18.0
> -- GTEST_VERSION: 1.8.1
> -- JEMALLOC_VERSION: 17c897976c60b0e6e4f4a365c751027244dada7a
> -- LZ4_VERSION: v1.8.3
> -- ORC_VERSION: 1.5.4
> -- PROTOBUF_VERSION: v3.6.1
> -- RAPIDJSON_VERSION: 2bbd33b33217ff4a73434ebf10cdac41e2ef5e34
> -- RE2_VERSION: 2018-1
[jira] [Created] (ARROW-4889) [C++] Add STATUS messages for Protobuf in CMake
Uwe L. Korn created ARROW-4889:
--
Summary: [C++] Add STATUS messages for Protobuf in CMake
Key: ARROW-4889
URL: https://issues.apache.org/jira/browse/ARROW-4889
Project: Apache Arrow
Issue Type: Improvement
Components: C++
Reporter: Uwe L. Korn
Assignee: Uwe L. Korn
Fix For: 0.13.0
With Protobuf it can easily happen that {{protoc}} and {{libprotobuf}}
mismatch. We should have some output about this in CMake to better debug this
when users report issues.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARROW-4891) [C++] ZLIB include directories not added
Uwe L. Korn created ARROW-4891: -- Summary: [C++] ZLIB include directories not added Key: ARROW-4891 URL: https://issues.apache.org/jira/browse/ARROW-4891 Project: Apache Arrow Issue Type: Improvement Components: C++ Reporter: Uwe L. Korn Assignee: Uwe L. Korn Fix For: 0.13.0 This causes a failing centos-7 build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-4893) [C++] conda packages should use $PREFIX inside of conda-build
Uwe L. Korn created ARROW-4893: -- Summary: [C++] conda packages should use $PREFIX inside of conda-build Key: ARROW-4893 URL: https://issues.apache.org/jira/browse/ARROW-4893 Project: Apache Arrow Issue Type: Improvement Components: C++, Packaging Reporter: Uwe L. Korn Assignee: Uwe L. Korn Fix For: 0.13.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-4898) [C++] Old versions of FindProtobuf.cmake use ALL-CAPS for variables
Uwe L. Korn created ARROW-4898:
--
Summary: [C++] Old versions of FindProtobuf.cmake use ALL-CAPS for
variables
Key: ARROW-4898
URL: https://issues.apache.org/jira/browse/ARROW-4898
Project: Apache Arrow
Issue Type: Improvement
Components: C++
Reporter: Uwe L. Korn
Assignee: Uwe L. Korn
Fix For: 0.13.0
We only need to handle {{PROTOBUF_PROTOC_LIBRARY}} vs
{{Protobuf_PROTOC_LIBRARY}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARROW-4902) [C++/Flight] Compilation fails due to unreachable code
Uwe L. Korn created ARROW-4902: -- Summary: [C++/Flight] Compilation fails due to unreachable code Key: ARROW-4902 URL: https://issues.apache.org/jira/browse/ARROW-4902 Project: Apache Arrow Issue Type: Improvement Components: C++, FlightRPC Reporter: Uwe L. Korn Assignee: Uwe L. Korn Fix For: 0.13.0 clang on OSX is quite picky, we can simply remove this code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARROW-4902) [C++/Flight] Compilation fails due to unreachable code
[ https://issues.apache.org/jira/browse/ARROW-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn closed ARROW-4902. -- Resolution: Won't Fix Fix Version/s: (was: 0.13.0) Clean build makes things okish again, closing as not so important. > [C++/Flight] Compilation fails due to unreachable code > --- > > Key: ARROW-4902 > URL: https://issues.apache.org/jira/browse/ARROW-4902 > Project: Apache Arrow > Issue Type: Improvement > Components: C++, FlightRPC >Reporter: Uwe L. Korn >Assignee: Uwe L. Korn >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > clang on OSX is quite picky, we can simply remove this code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-4903) [C++] Building tests using only static libs not possible
Uwe L. Korn created ARROW-4903: -- Summary: [C++] Building tests using only static libs not possible Key: ARROW-4903 URL: https://issues.apache.org/jira/browse/ARROW-4903 Project: Apache Arrow Issue Type: Bug Components: C++ Reporter: Uwe L. Korn Assignee: Uwe L. Korn Fix For: 0.13.0 We explicitly depend on shared libs in some tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-4904) [C++] Move implementations in arrow/ipc/test-common.h into libarrow_testing
Uwe L. Korn created ARROW-4904:
--
Summary: [C++] Move implementations in arrow/ipc/test-common.h
into libarrow_testing
Key: ARROW-4904
URL: https://issues.apache.org/jira/browse/ARROW-4904
Project: Apache Arrow
Issue Type: Task
Components: C++
Reporter: Uwe L. Korn
Fix For: 0.14.0
Instead of having these all defined as {{static inline}} we should move the
implementations into a testing support library.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARROW-4907) [CI] Add docker container to inspect docker context
Uwe L. Korn created ARROW-4907:
--
Summary: [CI] Add docker container to inspect docker context
Key: ARROW-4907
URL: https://issues.apache.org/jira/browse/ARROW-4907
Project: Apache Arrow
Issue Type: Task
Components: Continuous Integration
Reporter: Uwe L. Korn
Assignee: Uwe L. Korn
Fix For: 0.13.0
The larger the docker context the slower the docker build. Adding a small
container to inspect the context helps to curate a good {{.dockerignore}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARROW-4909) [CI] Use hadolint to lint Dockerfiles
Uwe L. Korn created ARROW-4909: -- Summary: [CI] Use hadolint to lint Dockerfiles Key: ARROW-4909 URL: https://issues.apache.org/jira/browse/ARROW-4909 Project: Apache Arrow Issue Type: Task Components: Continuous Integration Reporter: Uwe L. Korn Assignee: Uwe L. Korn Fix For: 0.13.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ARROW-4848) Static libparquet not compiled with -DARROW_STATIC on Windows
[ https://issues.apache.org/jira/browse/ARROW-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn reassigned ARROW-4848: -- Assignee: Uwe L. Korn > Static libparquet not compiled with -DARROW_STATIC on Windows > - > > Key: ARROW-4848 > URL: https://issues.apache.org/jira/browse/ARROW-4848 > Project: Apache Arrow > Issue Type: Bug > Components: C++ >Affects Versions: 0.12.1 >Reporter: Jeroen >Assignee: Uwe L. Korn >Priority: Major > > When trying to link the R bindings against static libparquet.a + libarrow.a > we get a lot of missing arrow symbol warnings from libparquet.a. I think the > problem is that libparquet.a was not compiled -DARROW_STATIC, and therefore > cannot be linked against libarrow.a. > When arrow cmake is configured with -DARROW_BUILD_SHARED=OFF I think it > should automatically use -DARROW_STATIC when compiling libparquet on Windows? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-4916) [C++] Add clang-format to pre-commit hook
Uwe L. Korn created ARROW-4916: -- Summary: [C++] Add clang-format to pre-commit hook Key: ARROW-4916 URL: https://issues.apache.org/jira/browse/ARROW-4916 Project: Apache Arrow Issue Type: Task Components: C++, Continuous Integration Reporter: Uwe L. Korn Assignee: Uwe L. Korn -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-4917) [C++] orc_ep fails in cpp-alpine docker
Uwe L. Korn created ARROW-4917:
--
Summary: [C++] orc_ep fails in cpp-alpine docker
Key: ARROW-4917
URL: https://issues.apache.org/jira/browse/ARROW-4917
Project: Apache Arrow
Issue Type: Bug
Components: C++
Reporter: Uwe L. Korn
Fix For: 0.13.0
Failure:
{code:java}
FAILED: c++/src/CMakeFiles/orc.dir/Timezone.cc.o
/usr/bin/g++ -Ic++/include -I/build/cpp/orc_ep-prefix/src/orc_ep/c++/include
-I/build/cpp/orc_ep-prefix/src/orc_ep/c++/src -Ic++/src -isystem
/build/cpp/snappy_ep/src/snappy_ep-install/include -isystem
c++/libs/thirdparty/zlib_ep-install/include -isystem
c++/libs/thirdparty/lz4_ep-install/include -isystem
/arrow/cpp/thirdparty/protobuf_ep-install/include -fdiagnostics-color=always
-ggdb -O0 -g -fPIC -std=c++11 -Wall -Wno-unknown-pragmas -Wconversion -Werror
-std=c++11 -Wall -Wno-unknown-pragmas -Wconversion -Werror -O0 -g -MD -MT
c++/src/CMakeFiles/orc.dir/Timezone.cc.o -MF
c++/src/CMakeFiles/orc.dir/Timezone.cc.o.d -o
c++/src/CMakeFiles/orc.dir/Timezone.cc.o -c
/build/cpp/orc_ep-prefix/src/orc_ep/c++/src/Timezone.cc
/build/cpp/orc_ep-prefix/src/orc_ep/c++/src/Timezone.cc: In member function
'void orc::TimezoneImpl::parseTimeVariants(const unsigned char*, uint64_t,
uint64_t, uint64_t, uint64_t)':
/build/cpp/orc_ep-prefix/src/orc_ep/c++/src/Timezone.cc:748:7: error: 'uint'
was not declared in this scope
uint nameStart = ptr[variantOffset + 6 * variant + 5];
^~~~
/build/cpp/orc_ep-prefix/src/orc_ep/c++/src/Timezone.cc:748:7: note: suggested
alternative: 'rint'
uint nameStart = ptr[variantOffset + 6 * variant + 5];
^~~~
rint
/build/cpp/orc_ep-prefix/src/orc_ep/c++/src/Timezone.cc:749:11: error:
'nameStart' was not declared in this scope
if (nameStart >= nameCount) {
^
/build/cpp/orc_ep-prefix/src/orc_ep/c++/src/Timezone.cc:749:11: note: suggested
alternative: 'nameCount'
if (nameStart >= nameCount) {
^
nameCount
/build/cpp/orc_ep-prefix/src/orc_ep/c++/src/Timezone.cc:756:59: error:
'nameStart' was not declared in this scope
+ nameOffset + nameStart);
^
/build/cpp/orc_ep-prefix/src/orc_ep/c++/src/Timezone.cc:756:59: note: suggested
alternative: 'nameCount'
+ nameOffset + nameStart);
^
nameCount{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARROW-4918) [C++] Add cmake-format to pre-commit
Uwe L. Korn created ARROW-4918: -- Summary: [C++] Add cmake-format to pre-commit Key: ARROW-4918 URL: https://issues.apache.org/jira/browse/ARROW-4918 Project: Apache Arrow Issue Type: Bug Components: C++, Continuous Integration Reporter: Uwe L. Korn Assignee: Uwe L. Korn -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ARROW-3759) [R] Build and test on Windows in Appveyor
[ https://issues.apache.org/jira/browse/ARROW-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794191#comment-16794191 ] Uwe L. Korn commented on ARROW-3759: To which of the CI entries would we add this or would we create a new one? > [R] Build and test on Windows in Appveyor > - > > Key: ARROW-3759 > URL: https://issues.apache.org/jira/browse/ARROW-3759 > Project: Apache Arrow > Issue Type: Improvement > Components: R >Reporter: Wes McKinney >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARROW-4867) [Python] Table.from_pandas() column order not respected
[
https://issues.apache.org/jira/browse/ARROW-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn resolved ARROW-4867.
Resolution: Fixed
Issue resolved by pull request 3930
[https://github.com/apache/arrow/pull/3930]
> [Python] Table.from_pandas() column order not respected
> ---
>
> Key: ARROW-4867
> URL: https://issues.apache.org/jira/browse/ARROW-4867
> Project: Apache Arrow
> Issue Type: Bug
> Components: Python
>Affects Versions: 0.12.1
>Reporter: Andreas
>Assignee: Wes McKinney
>Priority: Minor
> Labels: pull-request-available
> Fix For: 0.13.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Starting with 0.12, the order of the columns in {{Table.from_pandas}} is no
> longer identical to the order of the colums given in the {{columns}}
> argument. This used to be the case in previous versions.
> 0.12:
> {code:java}
> In [1]: pyarrow.Table.from_pandas(pd.DataFrame(dict(a=[1],b=[2])),
> columns=['b', 'a'])
> Out[1]:
> pyarrow.Table
> a: int64
> b: int64{code}
> 0.11:
> {code:java}
> In [1]: pyarrow.Table.from_pandas(pd.DataFrame(dict(a=[1],b=[2])),
> columns=['b', 'a'])
> Out[1]:
> pyarrow.Table
> b: int64
> a: int64{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ARROW-4922) [Packaging] Use system libraris for .deb and .rpm
[ https://issues.apache.org/jira/browse/ARROW-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn resolved ARROW-4922. Resolution: Fixed Issue resolved by pull request 3934 [https://github.com/apache/arrow/pull/3934] > [Packaging] Use system libraris for .deb and .rpm > - > > Key: ARROW-4922 > URL: https://issues.apache.org/jira/browse/ARROW-4922 > Project: Apache Arrow > Issue Type: Improvement > Components: Packaging >Reporter: Kouhei Sutou >Assignee: Kouhei Sutou >Priority: Major > Labels: pull-request-available > Fix For: 0.13.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ARROW-4900) mingw-w64 < 5 does not have __cpuidex
[ https://issues.apache.org/jira/browse/ARROW-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn reassigned ARROW-4900: -- Assignee: Jeroen > mingw-w64 < 5 does not have __cpuidex > - > > Key: ARROW-4900 > URL: https://issues.apache.org/jira/browse/ARROW-4900 > Project: Apache Arrow > Issue Type: Bug > Components: C++ >Reporter: Jeroen >Assignee: Jeroen >Priority: Major > Labels: pull-request-available > Fix For: 0.13.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The current R toolchain uses mingw-w64 runtime v3. Building libarrow fails > because arrow uses __cpuidex which was introduced in mingw-w64 runtime v5: > https://github.com/mingw-w64/mingw-w64/commit/8e921f2a87fb70564cbcf40676daee93ea0cae3a > We need a polyfill for this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
