[jira] [Created] (ARROW-15298) Linking error for debug build on Windows
Zois Tasoulas created ARROW-15298:
-
Summary: Linking error for debug build on Windows
Key: ARROW-15298
URL: https://issues.apache.org/jira/browse/ARROW-15298
Project: Apache Arrow
Issue Type: Bug
Environment: Windows 10
Reporter: Zois Tasoulas
I experienced a linking error while building the debug flavor of the project I
am working on, that links dynamically the arrow libraries, on Windows.
Specifically the error is described in [Linker Tools Warning
LNK4098|https://docs.microsoft.com/en-us/cpp/error-messages/tool-errors/linker-tools-warning-lnk4098?view=msvc-170].
The issue stems from the following CMake line,
[arrow/cpp/cmake_modules/SetupCxxFlags.cmake|https://github.com/apache/arrow/blob/8b440d1b5df4a0e58bcaa422b83e6d6ff1213b5f/cpp/cmake_modules/SetupCxxFlags.cmake#L643].
The solution that worked in my case was to explicitly mention which libraries
to exclude when building the release and debug flavor, following the table at
[Linker Tools Warning
LNK4098|https://docs.microsoft.com/en-us/cpp/error-messages/tool-errors/linker-tools-warning-lnk4098?view=msvc-170].
Specifically the aforementioned link to the Microsoft page describes in detail
which libraries to exclude when linking dynamically with C run-time, i.e.,
{code:bash}
NOT ARROW_USE_STATIC_CRT{code}
.
Additionally, for debug flavor builds, the /MDd or /MTd options might need to
be set explicitly. I pass that from my project's configuration but I think it
is not done explicitly within Arrow CMake files. Relevant link [Linker Tools
Error
LNK2001|https://docs.microsoft.com/en-us/cpp/error-messages/tool-errors/linker-tools-error-lnk2001?view=msvc-160],
read segment "If you link to the release mode libraries when building a debug
version [...]"
Apache Arrow ticket that introduced the aforementioned CMake line change and
dealt with the same issue: ARROW-4014
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (ARROW-15297) [C++] The write node options shouldn't require a schema
Weston Pace created ARROW-15297: --- Summary: [C++] The write node options shouldn't require a schema Key: ARROW-15297 URL: https://issues.apache.org/jira/browse/ARROW-15297 Project: Apache Arrow Issue Type: Sub-task Components: C++ Reporter: Weston Pace The schema should be the output schema of the input node. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ARROW-15296) [Dev][Go] Add Go staticcheck linting to CI lint job
Yibo Cai created ARROW-15296: Summary: [Dev][Go] Add Go staticcheck linting to CI lint job Key: ARROW-15296 URL: https://issues.apache.org/jira/browse/ARROW-15296 Project: Apache Arrow Issue Type: Improvement Components: Continuous Integration, Go Reporter: Yibo Cai Talked in PR https://github.com/apache/arrow/pull/12074 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ARROW-15295) [R] Add 6.0.0 to our old versions to check
Jonathan Keane created ARROW-15295: -- Summary: [R] Add 6.0.0 to our old versions to check Key: ARROW-15295 URL: https://issues.apache.org/jira/browse/ARROW-15295 Project: Apache Arrow Issue Type: Improvement Components: R Reporter: Jonathan Keane Assignee: Jonathan Keane -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ARROW-15294) [R] Remove arrow-without-arrow and other Solaris hacks
Neal Richardson created ARROW-15294: --- Summary: [R] Remove arrow-without-arrow and other Solaris hacks Key: ARROW-15294 URL: https://issues.apache.org/jira/browse/ARROW-15294 Project: Apache Arrow Issue Type: Improvement Components: R Reporter: Neal Richardson Fix For: 8.0.0 CRAN doesn't check on Solaris anymore so we can finally drop this. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ARROW-15293) [R] [CI] move arrow-r-nightly over to apache/arrow / crossbow
Jonathan Keane created ARROW-15293: -- Summary: [R] [CI] move arrow-r-nightly over to apache/arrow / crossbow Key: ARROW-15293 URL: https://issues.apache.org/jira/browse/ARROW-15293 Project: Apache Arrow Issue Type: Improvement Reporter: Jonathan Keane Assignee: Nicola Crane Move arrow-nightly CI to crossbow — currently there is [a separate repo|https://github.com/ursa-labs/arrow-r-nightly/] that builds our nightly binaries and hosts them (as well as hosts our distributed binaries, and builds nightly docs). We should move (some of) this under apache/arrow now that we can. Specifically, [the GHA that builds the binaries|https://github.com/ursa-labs/arrow-r-nightly/blob/master/.github/workflows/build-and-test-all.yml]. If we wanted to get fancy we could also use a parameterized/manually triggered GHA for our release builds. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ARROW-15292) [R] default to binary libarrow on Ubuntu/Redhat
Jonathan Keane created ARROW-15292: -- Summary: [R] default to binary libarrow on Ubuntu/Redhat Key: ARROW-15292 URL: https://issues.apache.org/jira/browse/ARROW-15292 Project: Apache Arrow Issue Type: Improvement Components: R Reporter: Jonathan Keane The V8 package uses binaries on those platforms: https://github.com/jeroen/V8/blob/16289554d548b9cdaba9cf0c71e35c7586d1a9d8/configure#L28-L35 Could we do this too? One thing that will complicate this is that we don't build our binary + host it somewhere on each build / with nightlies. So we will need to either _only_ do this on release numbers, or do something in CI to host binaries in the style we do with nightlies (or move those nightly builds into apache/arrow and use those...) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ARROW-15291) [C++][Python] Segfault in StructArray.to_numpy and to_pandas if it contains an ExtensionArray
quentin lhoest created ARROW-15291:
--
Summary: [C++][Python] Segfault in StructArray.to_numpy and
to_pandas if it contains an ExtensionArray
Key: ARROW-15291
URL: https://issues.apache.org/jira/browse/ARROW-15291
Project: Apache Arrow
Issue Type: Bug
Components: C++, Python
Affects Versions: 6.0.1
Environment: pyarrow 6.0.1, macbook pro
Reporter: quentin lhoest
Hi !
If you create a StructArray with an ExtensionArray in it, then both to_numpy
and to_pandas segfault in python:
{code:java}
import pyarrow as pa
class CustomType(pa.PyExtensionType):
def __init__(self):
pa.PyExtensionType.__init__(self, pa.binary())
def __reduce__(self):
return CustomType, ()
arr = pa.ExtensionArray.from_storage(CustomType(), pa.array([b"foo"]))
pa.StructArray.from_arrays([arr], ["name"]).to_numpy(zero_copy_only=False)
{code}
Thanks in advance for the help !
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (ARROW-15290) Documentation pages for PyArrow have incorrect hyperlinks
Joshua Robinson created ARROW-15290: --- Summary: Documentation pages for PyArrow have incorrect hyperlinks Key: ARROW-15290 URL: https://issues.apache.org/jira/browse/ARROW-15290 Project: Apache Arrow Issue Type: Bug Reporter: Joshua Robinson API documentation for pyarrow has a few confusing "mis"links. As an example, on the page below, the link for "csv.ReadOptions" actually takes me to "json.ReadOptions." I'm filing a bug because the pages were similar enough that I initially just assumed the csv parsing had limited functionality instead of realizing I was looking in the wrong place. Example page: [https://arrow.apache.org/docs/python/generated/pyarrow.dataset.CsvFileFormat.html] where ReadOptions and ParseOptions incorrectly link me to the JSON versions instead of CSV versions. ConvertOptions is correct, though. I have no idea how widespread this issue is as I have only looked and noticed the issue on this one page linked above. -- This message was sent by Atlassian Jira (v8.20.1#820001)
