[jira] [Created] (ARROW-5774) [Java][Documentation] Document the need to checkout git submodules for flight
Micah Kornfield created ARROW-5774: -- Summary: [Java][Documentation] Document the need to checkout git submodules for flight Key: ARROW-5774 URL: https://issues.apache.org/jira/browse/ARROW-5774 Project: Apache Arrow Issue Type: Bug Components: Documentation, Java Reporter: Micah Kornfield Assignee: Micah Kornfield -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items
I'd like to squeeze https://issues.apache.org/jira/browse/ARROW-5773 into 0.14 if you'll allow. It's just documentation. I just put the PR up now: https://github.com/apache/arrow/pull/4736 Thanks, Neal On Thu, Jun 27, 2019 at 9:55 PM Sutou Kouhei wrote: > We can merge pull request that doesn't change pom.xml for > 0.14.0 until I finished ARROW-4301 and ARROW-5695. > > In <20190628.134059.632882213120446354@clear-code.com> > "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri, > 28 Jun 2019 13:40:59 +0900 (JST), > Sutou Kouhei wrote: > > > Thanks! > > > > I'm testing ARROW-4301 (00-prepare.sh) and ARROW-5695 > > (verify-release-candidate.sh). > > > > ARROW-4301: We need to build C++ with Gandiva and ORC in > > 00-prepare.sh. I'm working on this. > > > > ARROW-5695: I'll merge this when I confirmed all > > verification patterns are passed with master. I'm running. > > > > I'll create RC0 when I finished them. > > > > For ARROW-5579, please merge it after 0.14.0. I don't want > > to add more pom.xml changes for now. > > > > > > Thanks, > > -- > > kou > > > > In > > "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on > Thu, 27 Jun 2019 22:35:45 -0500, > > Wes McKinney wrote: > > > >> It looks like we're down to 4 open issues. The remaining items can be > >> merged at Kou's discretion. The one uncertain item is ARROW-5579 -- > >> shading Flatbuffers. It seems like it might not be prudent to rush in > >> a patch that might potentially cause problems > >> > >> On Thu, Jun 27, 2019 at 12:23 PM Wes McKinney > wrote: > >>> > >>> hi folks, > >>> > >>> There are still 10 issues in the 0.14.0 milestone: > >>> > >>> * ARROW-4301: [Java] Patch up, pending review / merge > >>> * ARROW-2104: [C++] Ready to merge pending CI > >>> * ARROW-5500: [R] Ready to merge pending review > >>> * ARROW-5718: [R] Pending review -- may not be necessary for release > >>> * ARROW-5415: [R] No patch yet, but I believe Neal is working on it > >>> * ARROW-5511: [Python] Conda packages with Flight -- Krisztian is > >>> working on this in PR now > >>> * ARROW-5695: Patch in review / pending merge > >>> * ARROW-5579: Shading Java Flatbuffers: Pending review > >>> * ARROW-5138: I am looking at this now-ish to determine if a fix is in > >>> scope for the release > >>> * ARROW-5497: Publishing R / JS / Java docs -- not essential before > >>> release candidate can be cut > >>> > >>> Is there anything else? > >>> > >>> Based on these outstanding patches I would guess it's going to be > >>> another 12-24 hours from now before an RC can be cut > >>> > >>> I will also spend some time working on the blog post today > >>> > >>> On Mon, Jun 24, 2019 at 9:46 PM Neal Richardson > >>> wrote: > >>> > > >>> > I've got one of the blockers, > >>> > https://issues.apache.org/jira/browse/ARROW-5497, about the > non-sphinx > >>> > language doc building. I'll spend some time on it this week. It > should get > >>> > done before we're wrapped up with 0.14, but if I get held up, it > doesn't > >>> > need to block making RC0. > >>> > > >>> > In other news, in order to facilitate one of the post-release tasks, > I've > >>> > started a google doc for the release announcement blog post: > >>> > > https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj > >>> > . While we could wait to deal with the release announcement until > after the > >>> > release happens, doing it early can be a good exercise: it can reveal > >>> > details and polishing that are important to realizing the value of > the > >>> > features in the release. Plus, it shouldn't take long and we can > just get > >>> > it out of the way. > >>> > > >>> > For anyone who is a maintainer/stakeholder of one of the languages or > >>> > components of the project, please fill in the "notes" section for > your > >>> > component. Others could try to infer what's in the release based on > the > >>> > commit messages, but sometimes it's hard to tell what the sum of the > parts > >>> > is from that. > >>> > > >>> > Thanks, > >>> > Neal > >>> > > >>> > > >>> > On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney > wrote: > >>> > > >>> > > hi Kou, > >>> > > > >>> > > Thank you for volunteering to be the release manager. I think many > of > >>> > > the issues marked as Blocker on > >>> > > > >>> > > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release > >>> > > > >>> > > are being actively worked on. I'll follow up with individuals > directly > >>> > > and try to help get patches merged so we can be ready to release > >>> > > ideally before Friday in Japan (end of workday Thursday in the > USA). > >>> > > In certain cases (e.g. ARROW-5335) we may have to accept a > suboptimal > >>> > > solution and do more work for the next release. > >>> > > > >>> > > Thanks > >>> > > Wes > >>> > > > >>> > > On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei > wrote: > >>> > > > > >>> > > > Hi, > >>> > > > > >>> > > > Nobody
[jira] [Created] (ARROW-5773) [R] Clean up documentation before release
Neal Richardson created ARROW-5773: -- Summary: [R] Clean up documentation before release Key: ARROW-5773 URL: https://issues.apache.org/jira/browse/ARROW-5773 Project: Apache Arrow Issue Type: Improvement Reporter: Neal Richardson Assignee: Neal Richardson Fix For: 0.14.0 The R package documentation is lackluster. Try to polish the docs for at least the key end-user functions and add enough examples so that CRAN won't use that as an excuse to reject. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-5772) [GLib][Plasma][CUDA] Plasma::Client#refer_object test is failed
Sutou Kouhei created ARROW-5772:
---
Summary: [GLib][Plasma][CUDA] Plasma::Client#refer_object test is
failed
Key: ARROW-5772
URL: https://issues.apache.org/jira/browse/ARROW-5772
Project: Apache Arrow
Issue Type: Test
Components: GLib
Affects Versions: 0.14.0
Reporter: Sutou Kouhei
Assignee: Sutou Kouhei
Fix For: 1.0.0
{noformat}
/home/kou/work/cpp/arrow.kou/c_glib/test/plasma/test-plasma-client.rb:75:in
`block (2 levels) in '
/tmp/local/lib/ruby/gems/2.7.0/gems/gobject-introspection-3.3.6/lib/gobject-introspection/loader.rb:533:in
`block in define_method'
/tmp/local/lib/ruby/gems/2.7.0/gems/gobject-introspection-3.3.6/lib/gobject-introspection/loader.rb:616:in
`invoke'
/tmp/local/lib/ruby/gems/2.7.0/gems/gobject-introspection-3.3.6/lib/gobject-introspection/loader.rb:616:in
`invoke'
Error: test: options: GPU device(TestPlasmaClient::#create):
Arrow::Error::Io: [plasma][client][refer-object]: IOError: Cuda Driver API
call in ../src/arrow/gpu/cuda_context.cc at line 156 failed with code 208:
cuIpcOpenMemHandle(, *handle, CU_IPC_MEM_LAZY_ENABLE_PEER_ACCESS)
In ../src/arrow/gpu/cuda_context.cc, line 341, code:
impl_->OpenIpcBuffer(ipc_handle, )
In ../src/plasma/client.cc, line 586, code:
context->OpenIpcBuffer(*object->ipc_handle, _handle->ptr)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items
We can merge pull request that doesn't change pom.xml for 0.14.0 until I finished ARROW-4301 and ARROW-5695. In <20190628.134059.632882213120446354@clear-code.com> "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri, 28 Jun 2019 13:40:59 +0900 (JST), Sutou Kouhei wrote: > Thanks! > > I'm testing ARROW-4301 (00-prepare.sh) and ARROW-5695 > (verify-release-candidate.sh). > > ARROW-4301: We need to build C++ with Gandiva and ORC in > 00-prepare.sh. I'm working on this. > > ARROW-5695: I'll merge this when I confirmed all > verification patterns are passed with master. I'm running. > > I'll create RC0 when I finished them. > > For ARROW-5579, please merge it after 0.14.0. I don't want > to add more pom.xml changes for now. > > > Thanks, > -- > kou > > In > "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Thu, 27 > Jun 2019 22:35:45 -0500, > Wes McKinney wrote: > >> It looks like we're down to 4 open issues. The remaining items can be >> merged at Kou's discretion. The one uncertain item is ARROW-5579 -- >> shading Flatbuffers. It seems like it might not be prudent to rush in >> a patch that might potentially cause problems >> >> On Thu, Jun 27, 2019 at 12:23 PM Wes McKinney wrote: >>> >>> hi folks, >>> >>> There are still 10 issues in the 0.14.0 milestone: >>> >>> * ARROW-4301: [Java] Patch up, pending review / merge >>> * ARROW-2104: [C++] Ready to merge pending CI >>> * ARROW-5500: [R] Ready to merge pending review >>> * ARROW-5718: [R] Pending review -- may not be necessary for release >>> * ARROW-5415: [R] No patch yet, but I believe Neal is working on it >>> * ARROW-5511: [Python] Conda packages with Flight -- Krisztian is >>> working on this in PR now >>> * ARROW-5695: Patch in review / pending merge >>> * ARROW-5579: Shading Java Flatbuffers: Pending review >>> * ARROW-5138: I am looking at this now-ish to determine if a fix is in >>> scope for the release >>> * ARROW-5497: Publishing R / JS / Java docs -- not essential before >>> release candidate can be cut >>> >>> Is there anything else? >>> >>> Based on these outstanding patches I would guess it's going to be >>> another 12-24 hours from now before an RC can be cut >>> >>> I will also spend some time working on the blog post today >>> >>> On Mon, Jun 24, 2019 at 9:46 PM Neal Richardson >>> wrote: >>> > >>> > I've got one of the blockers, >>> > https://issues.apache.org/jira/browse/ARROW-5497, about the non-sphinx >>> > language doc building. I'll spend some time on it this week. It should get >>> > done before we're wrapped up with 0.14, but if I get held up, it doesn't >>> > need to block making RC0. >>> > >>> > In other news, in order to facilitate one of the post-release tasks, I've >>> > started a google doc for the release announcement blog post: >>> > https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj >>> > . While we could wait to deal with the release announcement until after >>> > the >>> > release happens, doing it early can be a good exercise: it can reveal >>> > details and polishing that are important to realizing the value of the >>> > features in the release. Plus, it shouldn't take long and we can just get >>> > it out of the way. >>> > >>> > For anyone who is a maintainer/stakeholder of one of the languages or >>> > components of the project, please fill in the "notes" section for your >>> > component. Others could try to infer what's in the release based on the >>> > commit messages, but sometimes it's hard to tell what the sum of the parts >>> > is from that. >>> > >>> > Thanks, >>> > Neal >>> > >>> > >>> > On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney wrote: >>> > >>> > > hi Kou, >>> > > >>> > > Thank you for volunteering to be the release manager. I think many of >>> > > the issues marked as Blocker on >>> > > >>> > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release >>> > > >>> > > are being actively worked on. I'll follow up with individuals directly >>> > > and try to help get patches merged so we can be ready to release >>> > > ideally before Friday in Japan (end of workday Thursday in the USA). >>> > > In certain cases (e.g. ARROW-5335) we may have to accept a suboptimal >>> > > solution and do more work for the next release. >>> > > >>> > > Thanks >>> > > Wes >>> > > >>> > > On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei >>> > > wrote: >>> > > > >>> > > > Hi, >>> > > > >>> > > > Nobody says "I want to be a release manager". So I'll be the >>> > > > release manager for 0.14.0. >>> > > > >>> > > > I'm working on and assisting some release related issues: >>> > > > >>> > > > * ARROW-5054 [C++][Release] Test Flight in >>> > > > verify-release-candidate.sh >>> > > > https://issues.apache.org/jira/browse/ARROW-5054 >>> > > > >>> > > > * ARROW-5695 [C#][Release] Run sourcelink test in >>> > > verify-release-candidate.sh >>> > > >
Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items
Thanks! I'm testing ARROW-4301 (00-prepare.sh) and ARROW-5695 (verify-release-candidate.sh). ARROW-4301: We need to build C++ with Gandiva and ORC in 00-prepare.sh. I'm working on this. ARROW-5695: I'll merge this when I confirmed all verification patterns are passed with master. I'm running. I'll create RC0 when I finished them. For ARROW-5579, please merge it after 0.14.0. I don't want to add more pom.xml changes for now. Thanks, -- kou In "Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items" on Thu, 27 Jun 2019 22:35:45 -0500, Wes McKinney wrote: > It looks like we're down to 4 open issues. The remaining items can be > merged at Kou's discretion. The one uncertain item is ARROW-5579 -- > shading Flatbuffers. It seems like it might not be prudent to rush in > a patch that might potentially cause problems > > On Thu, Jun 27, 2019 at 12:23 PM Wes McKinney wrote: >> >> hi folks, >> >> There are still 10 issues in the 0.14.0 milestone: >> >> * ARROW-4301: [Java] Patch up, pending review / merge >> * ARROW-2104: [C++] Ready to merge pending CI >> * ARROW-5500: [R] Ready to merge pending review >> * ARROW-5718: [R] Pending review -- may not be necessary for release >> * ARROW-5415: [R] No patch yet, but I believe Neal is working on it >> * ARROW-5511: [Python] Conda packages with Flight -- Krisztian is >> working on this in PR now >> * ARROW-5695: Patch in review / pending merge >> * ARROW-5579: Shading Java Flatbuffers: Pending review >> * ARROW-5138: I am looking at this now-ish to determine if a fix is in >> scope for the release >> * ARROW-5497: Publishing R / JS / Java docs -- not essential before >> release candidate can be cut >> >> Is there anything else? >> >> Based on these outstanding patches I would guess it's going to be >> another 12-24 hours from now before an RC can be cut >> >> I will also spend some time working on the blog post today >> >> On Mon, Jun 24, 2019 at 9:46 PM Neal Richardson >> wrote: >> > >> > I've got one of the blockers, >> > https://issues.apache.org/jira/browse/ARROW-5497, about the non-sphinx >> > language doc building. I'll spend some time on it this week. It should get >> > done before we're wrapped up with 0.14, but if I get held up, it doesn't >> > need to block making RC0. >> > >> > In other news, in order to facilitate one of the post-release tasks, I've >> > started a google doc for the release announcement blog post: >> > https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj >> > . While we could wait to deal with the release announcement until after the >> > release happens, doing it early can be a good exercise: it can reveal >> > details and polishing that are important to realizing the value of the >> > features in the release. Plus, it shouldn't take long and we can just get >> > it out of the way. >> > >> > For anyone who is a maintainer/stakeholder of one of the languages or >> > components of the project, please fill in the "notes" section for your >> > component. Others could try to infer what's in the release based on the >> > commit messages, but sometimes it's hard to tell what the sum of the parts >> > is from that. >> > >> > Thanks, >> > Neal >> > >> > >> > On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney wrote: >> > >> > > hi Kou, >> > > >> > > Thank you for volunteering to be the release manager. I think many of >> > > the issues marked as Blocker on >> > > >> > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release >> > > >> > > are being actively worked on. I'll follow up with individuals directly >> > > and try to help get patches merged so we can be ready to release >> > > ideally before Friday in Japan (end of workday Thursday in the USA). >> > > In certain cases (e.g. ARROW-5335) we may have to accept a suboptimal >> > > solution and do more work for the next release. >> > > >> > > Thanks >> > > Wes >> > > >> > > On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei wrote: >> > > > >> > > > Hi, >> > > > >> > > > Nobody says "I want to be a release manager". So I'll be the >> > > > release manager for 0.14.0. >> > > > >> > > > I'm working on and assisting some release related issues: >> > > > >> > > > * ARROW-5054 [C++][Release] Test Flight in >> > > > verify-release-candidate.sh >> > > > https://issues.apache.org/jira/browse/ARROW-5054 >> > > > >> > > > * ARROW-5695 [C#][Release] Run sourcelink test in >> > > verify-release-candidate.sh >> > > > https://issues.apache.org/jira/browse/ARROW-5695 >> > > > >> > > > * ARROW-4020 [Release] Remove source artifacts from dev dist system >> > > after release vote passes >> > > > https://issues.apache.org/jira/browse/ARROW-4020 >> > > > >> > > > I marked all of them as Blocker. >> > > > >> > > > It'll take a few days to complete them. >> > > > >> > > > I want to create RC0 when they are completed. Could someone >> > > > work on other Blocker issues while I work on the above >> > > > issues? >> >
[jira] [Created] (ARROW-5771) [Python] Docker python-nopandas job fails
Wes McKinney created ARROW-5771:
---
Summary: [Python] Docker python-nopandas job fails
Key: ARROW-5771
URL: https://issues.apache.org/jira/browse/ARROW-5771
Project: Apache Arrow
Issue Type: Bug
Components: Python
Reporter: Wes McKinney
Assignee: Wes McKinney
Fix For: 0.14.0
{code}
=== ERRORS
_ ERROR collecting
opt/conda/lib/python3.7/site-packages/pyarrow/tests/test_array.py __
ImportError while importing test module
'/opt/conda/lib/python3.7/site-packages/pyarrow/tests/test_array.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
opt/conda/lib/python3.7/site-packages/pyarrow/tests/test_array.py:35: in
import pyarrow.tests.strategies as past
opt/conda/lib/python3.7/site-packages/pyarrow/tests/strategies.py:18: in
import pytz
E ModuleNotFoundError: No module named 'pytz'
_ ERROR collecting
opt/conda/lib/python3.7/site-packages/pyarrow/tests/test_convert_builtin.py _
ImportError while importing test module
'/opt/conda/lib/python3.7/site-packages/pyarrow/tests/test_convert_builtin.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
opt/conda/lib/python3.7/site-packages/pyarrow/tests/test_convert_builtin.py:31:
in
import pytz
E ModuleNotFoundError: No module named 'pytz'
_ ERROR collecting
opt/conda/lib/python3.7/site-packages/pyarrow/tests/test_pandas.py _
ImportError while importing test module
'/opt/conda/lib/python3.7/site-packages/pyarrow/tests/test_pandas.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
opt/conda/lib/python3.7/site-packages/pyarrow/tests/test_pandas.py:29: in
import hypothesis.extra.pytz as tzst
opt/conda/lib/python3.7/site-packages/hypothesis/extra/pytz.py:34: in
import pytz
E ModuleNotFoundError: No module named 'pytz'
___ ERROR collecting
opt/conda/lib/python3.7/site-packages/pyarrow/tests/test_strategies.py ___
ImportError while importing test module
'/opt/conda/lib/python3.7/site-packages/pyarrow/tests/test_strategies.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
opt/conda/lib/python3.7/site-packages/pyarrow/tests/test_strategies.py:21: in
import pyarrow.tests.strategies as past
opt/conda/lib/python3.7/site-packages/pyarrow/tests/strategies.py:18: in
import pytz
E ModuleNotFoundError: No module named 'pytz'
_ ERROR collecting
opt/conda/lib/python3.7/site-packages/pyarrow/tests/test_types.py __
ImportError while importing test module
'/opt/conda/lib/python3.7/site-packages/pyarrow/tests/test_types.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
opt/conda/lib/python3.7/site-packages/pyarrow/tests/test_types.py:28: in
import pyarrow.tests.strategies as past
opt/conda/lib/python3.7/site-packages/pyarrow/tests/strategies.py:18: in
import pytz
E ModuleNotFoundError: No module named 'pytz'
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: [DISCUSS] Making the Arrow 0.14 release, outstanding items
It looks like we're down to 4 open issues. The remaining items can be merged at Kou's discretion. The one uncertain item is ARROW-5579 -- shading Flatbuffers. It seems like it might not be prudent to rush in a patch that might potentially cause problems On Thu, Jun 27, 2019 at 12:23 PM Wes McKinney wrote: > > hi folks, > > There are still 10 issues in the 0.14.0 milestone: > > * ARROW-4301: [Java] Patch up, pending review / merge > * ARROW-2104: [C++] Ready to merge pending CI > * ARROW-5500: [R] Ready to merge pending review > * ARROW-5718: [R] Pending review -- may not be necessary for release > * ARROW-5415: [R] No patch yet, but I believe Neal is working on it > * ARROW-5511: [Python] Conda packages with Flight -- Krisztian is > working on this in PR now > * ARROW-5695: Patch in review / pending merge > * ARROW-5579: Shading Java Flatbuffers: Pending review > * ARROW-5138: I am looking at this now-ish to determine if a fix is in > scope for the release > * ARROW-5497: Publishing R / JS / Java docs -- not essential before > release candidate can be cut > > Is there anything else? > > Based on these outstanding patches I would guess it's going to be > another 12-24 hours from now before an RC can be cut > > I will also spend some time working on the blog post today > > On Mon, Jun 24, 2019 at 9:46 PM Neal Richardson > wrote: > > > > I've got one of the blockers, > > https://issues.apache.org/jira/browse/ARROW-5497, about the non-sphinx > > language doc building. I'll spend some time on it this week. It should get > > done before we're wrapped up with 0.14, but if I get held up, it doesn't > > need to block making RC0. > > > > In other news, in order to facilitate one of the post-release tasks, I've > > started a google doc for the release announcement blog post: > > https://docs.google.com/document/d/1ljkW5tBh7cDfPRg_z6YY-1cbXfXxpfpRUlSatbV8128/edit#heading=h.vhz2t4ep6pkj > > . While we could wait to deal with the release announcement until after the > > release happens, doing it early can be a good exercise: it can reveal > > details and polishing that are important to realizing the value of the > > features in the release. Plus, it shouldn't take long and we can just get > > it out of the way. > > > > For anyone who is a maintainer/stakeholder of one of the languages or > > components of the project, please fill in the "notes" section for your > > component. Others could try to infer what's in the release based on the > > commit messages, but sometimes it's hard to tell what the sum of the parts > > is from that. > > > > Thanks, > > Neal > > > > > > On Mon, Jun 24, 2019 at 3:05 PM Wes McKinney wrote: > > > > > hi Kou, > > > > > > Thank you for volunteering to be the release manager. I think many of > > > the issues marked as Blocker on > > > > > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release > > > > > > are being actively worked on. I'll follow up with individuals directly > > > and try to help get patches merged so we can be ready to release > > > ideally before Friday in Japan (end of workday Thursday in the USA). > > > In certain cases (e.g. ARROW-5335) we may have to accept a suboptimal > > > solution and do more work for the next release. > > > > > > Thanks > > > Wes > > > > > > On Mon, Jun 24, 2019 at 4:27 PM Sutou Kouhei wrote: > > > > > > > > Hi, > > > > > > > > Nobody says "I want to be a release manager". So I'll be the > > > > release manager for 0.14.0. > > > > > > > > I'm working on and assisting some release related issues: > > > > > > > > * ARROW-5054 [C++][Release] Test Flight in verify-release-candidate.sh > > > > https://issues.apache.org/jira/browse/ARROW-5054 > > > > > > > > * ARROW-5695 [C#][Release] Run sourcelink test in > > > verify-release-candidate.sh > > > > https://issues.apache.org/jira/browse/ARROW-5695 > > > > > > > > * ARROW-4020 [Release] Remove source artifacts from dev dist system > > > after release vote passes > > > > https://issues.apache.org/jira/browse/ARROW-4020 > > > > > > > > I marked all of them as Blocker. > > > > > > > > It'll take a few days to complete them. > > > > > > > > I want to create RC0 when they are completed. Could someone > > > > work on other Blocker issues while I work on the above > > > > issues? > > > > > > > > > > > > Thanks, > > > > -- > > > > kou > > > > > > > > In > > > > "[DISCUSS] Making the Arrow 0.14 release, outstanding items" on Fri, > > > 21 Jun 2019 14:58:54 -0500, > > > > Wes McKinney wrote: > > > > > > > > > hi folks, > > > > > > > > > > It seems like we are on the home stretch for the 0.14 release as we > > > > > have been working intensely to stabilize builds and packaging jobs > > > > > this week and last > > > > > > > > > > See status page at > > > > > > > > > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release > > > > > > > > > > I note that there are 64 open issues still, not all of which are > > > > > absolutely necessary to be able to release.
[jira] [Created] (ARROW-5770) Fix -Wpessimizing-move in result.h
Micah Kornfield created ARROW-5770: -- Summary: Fix -Wpessimizing-move in result.h Key: ARROW-5770 URL: https://issues.apache.org/jira/browse/ARROW-5770 Project: Apache Arrow Issue Type: Bug Reporter: Micah Kornfield Assignee: Micah Kornfield -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [Discuss][Java][Typical use cases for dictionary encoding string vectors]
@Wes McKinney, I see your comments. Thank you so much. I agree with you that the schema and dictionary should be separated. However, according to the current Java implementation, the dictionary is attached to the schema, so a refactoring is required. BTW, a somewhat related problem is that the data schema is not immutable even if we remove dictionary from it. As data are inserted to the batch, the schema may change. A problem related to this is found in https://issues.apache.org/jira/browse/ARROW-5658 Do you think that violates the IPC protocol? Best, Liya Fan On Fri, Jun 28, 2019 at 7:36 AM Wes McKinney wrote: > hi Liya, > > I left a couple of comments in the document. You might look at what we > have developed in C++ and JavaSript which is more mature and widely > used in those languages than what currently exists in Java. > > In particular, I strongly encourage you to avoid creating a coupling > between the Schema (which indicates the "index type" and the > "dictionary type") and the Data (which contains the "dictionary > indices" and the "dictionary values"). If you do this, then it is > nearly impossible to account for dictionary changes in a stream of > data, which is already supported in the IPC protocol, see > > > https://github.com/apache/arrow/blob/master/docs/source/format/IPC.rst#dictionary-batches > > The protocol does not permit dictionaries to change order altogether, > but I think it should. I just opened > https://issues.apache.org/jira/browse/ARROW-5767 > > We made this mistake early in the C++ library and found it difficult > to have to reconciled dictionaries produced by different threads of > execution. See ARROW-3144 and the patch I wrote in this > release cycle which addressed this design flaw. > > Thanks > Wes > > On Wed, Jun 12, 2019 at 5:33 AM Fan Liya wrote: > > > > @Micah Kornfield Thanks a lot for your comments. > > > > In the doc, we identify 3 problems for the current dictionary encoding > use > > case (there can be more, so please give your valuable suggestions): > > > > 1. there should be a convenient way to provide access to both > > encoded/decoded data. > > 2. the constructor for the schema with dictionary is misleading. > > 3. we should provide a way to do the encoding/decoding during > > serialization/deserialization, so the encoding/decoding can be > transparent > > to the user. > > > > The current PR provides a solution for problem 2, and it is a relatively > > small change, so we think we can merge this PR first. > > > > Solutions for problem 1 and 3 should be chosen carefully so as not to > > affect existing APIs. So more discussions/designs for problems 1 and 3 > are > > desired. > > Do you think it reasonable? > > > > Best, > > Liya Fan > > > > > > > > On Wed, Jun 12, 2019 at 4:01 PM Micah Kornfield > > wrote: > > > > > Hi Liya Fan, > > > Thanks you for doing this. I need to take a closer look at the PR in > > > question and the dictionary encoding code but this seems like it is on > the > > > right track. > > > > > > Could other java contributors with more familiarity in the space look > over > > > the document to make sure it makes sense to them? > > > > > > Thanks, > > > Micah > > > > > > On Mon, Jun 10, 2019 at 2:23 AM Fan Liya wrote: > > > > > > > Hi all, > > > > > > > > This is concerning issue ARROW-3396. > > > > > > > > I have summarized the problem (please see if my understanding is > > > correct), > > > > and proposed some solutions to it. Please give your valuable > feedback. > > > > For details, please see: > > > > > > > > > > > > > > > > https://docs.google.com/document/d/1Y2E6RbZkUj3SwuEJrlEjaeIPmCA1SIsi9wmbJmVlB2I/edit?usp=sharing > > > > > > > > Thank you in advance. > > > > > > > > Best, > > > > Liya Fan > > > > > > > >
Re: 0.14.0: Java org.apache.arrow.flight.TestTls is failed via dev/release/00-prepare.sh
Thanks! I also get the same feedback from lidavidm on JIRA. I'll create a pull request to ensure setting up test data. In "Re: 0.14.0: Java org.apache.arrow.flight.TestTls is failed via dev/release/00-prepare.sh" on Thu, 27 Jun 2019 18:17:06 -0700, Micah Kornfield wrote: > It's an environment problem. The arrow testing repo needs to be checked > out and an environment variable set. I'll try to have a PR out to fix > this tonight > > On Thursday, June 27, 2019, Sutou Kouhei wrote: > >> Hi, >> >> I'm trying dev/release/00-prepare.sh that is the first >> script to create RC. >> >> It fails with OpenJDK 8 by Flight test. I'm not sure whether >> this is my environment problem or not. Could Java developers >> take a look this? >> >> JIRA: https://issues.apache.org/jira/browse/ARROW-5769 >> >> Error message: >> >> [INFO] [INFO] Running org.apache.arrow.flight.TestTls >> [INFO] [ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time >> elapsed: 0.005 s <<< FAILURE! - in org.apache.arrow.flight.TestTls >> [INFO] [ERROR] connectTls(org.apache.arrow.flight.TestTls) Time elapsed: >> 0.004 s <<< ERROR! >> [INFO] java.lang.RuntimeException: java.io.FileNotFoundException: >> /home/kou/work/cpp/arrow.pravindra/java/flight/../../testing/data/flight/cert0.pem >> (No such file or directory) >> [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:105) >> [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) >> [INFO] at org.apache.arrow.flight.TestTls.connectTls(TestTls.java:44) >> [INFO] Caused by: java.io.FileNotFoundException: /home/kou/work/cpp/arrow. >> pravindra/java/flight/../../testing/data/flight/cert0.pem (No such file >> or directory) >> [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:102) >> [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) >> [INFO] at org.apache.arrow.flight.TestTls.connectTls(TestTls.java:44) >> [INFO] >> [INFO] [ERROR] rejectInvalidCert(org.apache.arrow.flight.TestTls) Time >> elapsed: 0 s <<< ERROR! >> [INFO] java.lang.Exception: Unexpected exception, >> expected >> but was >> [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:105) >> [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) >> [INFO] at org.apache.arrow.flight.TestTls.rejectInvalidCert( >> TestTls.java:62) >> [INFO] Caused by: java.io.FileNotFoundException: /home/kou/work/cpp/arrow. >> pravindra/java/flight/../../testing/data/flight/cert0.pem (No such file >> or directory) >> [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:102) >> [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) >> [INFO] at org.apache.arrow.flight.TestTls.rejectInvalidCert( >> TestTls.java:62) >> [INFO] >> [INFO] [ERROR] rejectHostname(org.apache.arrow.flight.TestTls) Time >> elapsed: 0.001 s <<< ERROR! >> [INFO] java.lang.Exception: Unexpected exception, >> expected >> but was >> [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:105) >> [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) >> [INFO] at org.apache.arrow.flight.TestTls.rejectHostname(TestTls.java:78) >> [INFO] Caused by: java.io.FileNotFoundException: /home/kou/work/cpp/arrow. >> pravindra/java/flight/../../testing/data/flight/cert0.pem (No such file >> or directory) >> [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:102) >> [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) >> [INFO] at org.apache.arrow.flight.TestTls.rejectHostname(TestTls.java:78) >> [INFO] >> [INFO] [INFO] Running org.apache.arrow.flight.TestServerOptions >> [INFO] [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time >> elapsed: 0.114 s - in org.apache.arrow.flight.TestServerOptions >> [INFO] [INFO] >> [INFO] [INFO] Results: >> [INFO] [INFO] >> [INFO] [ERROR] Errors: >> [INFO] [ERROR] TestTls.connectTls:44->test:98->lambda$test$3:105 >> Runtime java.io.FileNotFound... >> [INFO] [ERROR] TestTls.rejectHostname » Unexpected exception, >> expected> [INFO] [ERROR] TestTls.rejectInvalidCert » Unexpected exception, >> expected> [INFO] [INFO] >> [INFO] [ERROR] Tests run: 27, Failures: 0, Errors: 3, Skipped: 10 >> >> >> Thanks, >> -- >> kou >> >> >>
Re: 0.14.0: Java org.apache.arrow.flight.TestTls is failed via dev/release/00-prepare.sh
It's an environment problem. The arrow testing repo needs to be checked out and an environment variable set. I'll try to have a PR out to fix this tonight On Thursday, June 27, 2019, Sutou Kouhei wrote: > Hi, > > I'm trying dev/release/00-prepare.sh that is the first > script to create RC. > > It fails with OpenJDK 8 by Flight test. I'm not sure whether > this is my environment problem or not. Could Java developers > take a look this? > > JIRA: https://issues.apache.org/jira/browse/ARROW-5769 > > Error message: > > [INFO] [INFO] Running org.apache.arrow.flight.TestTls > [INFO] [ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time > elapsed: 0.005 s <<< FAILURE! - in org.apache.arrow.flight.TestTls > [INFO] [ERROR] connectTls(org.apache.arrow.flight.TestTls) Time elapsed: > 0.004 s <<< ERROR! > [INFO] java.lang.RuntimeException: java.io.FileNotFoundException: > /home/kou/work/cpp/arrow.pravindra/java/flight/../../testing/data/flight/cert0.pem > (No such file or directory) > [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:105) > [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) > [INFO] at org.apache.arrow.flight.TestTls.connectTls(TestTls.java:44) > [INFO] Caused by: java.io.FileNotFoundException: /home/kou/work/cpp/arrow. > pravindra/java/flight/../../testing/data/flight/cert0.pem (No such file > or directory) > [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:102) > [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) > [INFO] at org.apache.arrow.flight.TestTls.connectTls(TestTls.java:44) > [INFO] > [INFO] [ERROR] rejectInvalidCert(org.apache.arrow.flight.TestTls) Time > elapsed: 0 s <<< ERROR! > [INFO] java.lang.Exception: Unexpected exception, > expected > but was > [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:105) > [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) > [INFO] at org.apache.arrow.flight.TestTls.rejectInvalidCert( > TestTls.java:62) > [INFO] Caused by: java.io.FileNotFoundException: /home/kou/work/cpp/arrow. > pravindra/java/flight/../../testing/data/flight/cert0.pem (No such file > or directory) > [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:102) > [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) > [INFO] at org.apache.arrow.flight.TestTls.rejectInvalidCert( > TestTls.java:62) > [INFO] > [INFO] [ERROR] rejectHostname(org.apache.arrow.flight.TestTls) Time > elapsed: 0.001 s <<< ERROR! > [INFO] java.lang.Exception: Unexpected exception, > expected > but was > [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:105) > [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) > [INFO] at org.apache.arrow.flight.TestTls.rejectHostname(TestTls.java:78) > [INFO] Caused by: java.io.FileNotFoundException: /home/kou/work/cpp/arrow. > pravindra/java/flight/../../testing/data/flight/cert0.pem (No such file > or directory) > [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:102) > [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) > [INFO] at org.apache.arrow.flight.TestTls.rejectHostname(TestTls.java:78) > [INFO] > [INFO] [INFO] Running org.apache.arrow.flight.TestServerOptions > [INFO] [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time > elapsed: 0.114 s - in org.apache.arrow.flight.TestServerOptions > [INFO] [INFO] > [INFO] [INFO] Results: > [INFO] [INFO] > [INFO] [ERROR] Errors: > [INFO] [ERROR] TestTls.connectTls:44->test:98->lambda$test$3:105 > Runtime java.io.FileNotFound... > [INFO] [ERROR] TestTls.rejectHostname » Unexpected exception, > expected [INFO] [ERROR] TestTls.rejectInvalidCert » Unexpected exception, > expected [INFO] [INFO] > [INFO] [ERROR] Tests run: 27, Failures: 0, Errors: 3, Skipped: 10 > > > Thanks, > -- > kou > > >
0.14.0: Java org.apache.arrow.flight.TestTls is failed via dev/release/00-prepare.sh
Hi, I'm trying dev/release/00-prepare.sh that is the first script to create RC. It fails with OpenJDK 8 by Flight test. I'm not sure whether this is my environment problem or not. Could Java developers take a look this? JIRA: https://issues.apache.org/jira/browse/ARROW-5769 Error message: [INFO] [INFO] Running org.apache.arrow.flight.TestTls [INFO] [ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.005 s <<< FAILURE! - in org.apache.arrow.flight.TestTls [INFO] [ERROR] connectTls(org.apache.arrow.flight.TestTls) Time elapsed: 0.004 s <<< ERROR! [INFO] java.lang.RuntimeException: java.io.FileNotFoundException: /home/kou/work/cpp/arrow.pravindra/java/flight/../../testing/data/flight/cert0.pem (No such file or directory) [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:105) [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) [INFO] at org.apache.arrow.flight.TestTls.connectTls(TestTls.java:44) [INFO] Caused by: java.io.FileNotFoundException: /home/kou/work/cpp/arrow.pravindra/java/flight/../../testing/data/flight/cert0.pem (No such file or directory) [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:102) [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) [INFO] at org.apache.arrow.flight.TestTls.connectTls(TestTls.java:44) [INFO] [INFO] [ERROR] rejectInvalidCert(org.apache.arrow.flight.TestTls) Time elapsed: 0 s <<< ERROR! [INFO] java.lang.Exception: Unexpected exception, expected but was [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:105) [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) [INFO] at org.apache.arrow.flight.TestTls.rejectInvalidCert(TestTls.java:62) [INFO] Caused by: java.io.FileNotFoundException: /home/kou/work/cpp/arrow.pravindra/java/flight/../../testing/data/flight/cert0.pem (No such file or directory) [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:102) [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) [INFO] at org.apache.arrow.flight.TestTls.rejectInvalidCert(TestTls.java:62) [INFO] [INFO] [ERROR] rejectHostname(org.apache.arrow.flight.TestTls) Time elapsed: 0.001 s <<< ERROR! [INFO] java.lang.Exception: Unexpected exception, expected but was [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:105) [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) [INFO] at org.apache.arrow.flight.TestTls.rejectHostname(TestTls.java:78) [INFO] Caused by: java.io.FileNotFoundException: /home/kou/work/cpp/arrow.pravindra/java/flight/../../testing/data/flight/cert0.pem (No such file or directory) [INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:102) [INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98) [INFO] at org.apache.arrow.flight.TestTls.rejectHostname(TestTls.java:78) [INFO] [INFO] [INFO] Running org.apache.arrow.flight.TestServerOptions [INFO] [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.114 s - in org.apache.arrow.flight.TestServerOptions [INFO] [INFO] [INFO] [INFO] Results: [INFO] [INFO] [INFO] [ERROR] Errors: [INFO] [ERROR] TestTls.connectTls:44->test:98->lambda$test$3:105 Runtime java.io.FileNotFound... [INFO] [ERROR] TestTls.rejectHostname » Unexpected exception, expected
Re: 0.14.0: C++ TestDictionary.Validate is crashed with release build
Thanks!!! In "Re: 0.14.0: C++ TestDictionary.Validate is crashed with release build" on Thu, 27 Jun 2019 17:07:27 -0500, Wes McKinney wrote: > Patch here: https://github.com/apache/arrow/pull/4730 > > We aren't testing release builds of the C++ project at all in Travis > CI. The longer build times probably pose a problem anyway, so I have > set up a docker-compose build so we can add this to Ursabot to prevent > this from happening in the future > > On Thu, Jun 27, 2019 at 4:49 PM Wes McKinney wrote: >> >> hi Kou, >> >> I'm taking a look now. >> >> - Wes >> >> On Thu, Jun 27, 2019 at 4:47 PM Sutou Kouhei wrote: >> > >> > Hi, >> > >> > I'm testing dev/release/verify-release-candidate.sh that is >> > a script to verify RC. >> > >> > I found that TestDictionary.Validate C++ test is crashed >> > with release build. Note that this isn't crashed with debug >> > build. >> > >> > Could C++ developers take a look this? >> > >> > JIRA: https://issues.apache.org/jira/browse/ARROW-5765 >> > This includes CMake options I used to reproduce this. >> > >> > Backtrace: >> > >> > (gdb) bt >> > #0 0x776b3bba in >> > arrow::DictionaryArray::DictionaryArray(std::shared_ptr >> > const&, std::shared_ptr const&, >> > std::shared_ptr const&) () >> >from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow.so.14 >> > #1 0x557ba6c3 in arrow::TestDictionary_Validate_Test::TestBody() >> > () >> > #2 0x77fa725a in void >> > testing::internal::HandleExceptionsInMethodIfSupported> > void>(testing::Test*, void (testing::Test::*)(), char const*) () >> >from >> > /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 >> > #3 0x77f9db5a in testing::Test::Run() () >> >from >> > /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 >> > #4 0x77f9dca8 in testing::TestInfo::Run() () >> >from >> > /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 >> > #5 0x77f9dd85 in testing::TestCase::Run() () >> >from >> > /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 >> > #6 0x77f9e29c in testing::internal::UnitTestImpl::RunAllTests() () >> >from >> > /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 >> > #7 0x77fa776a in bool >> > testing::internal::HandleExceptionsInMethodIfSupported> > bool>(testing::internal::UnitTestImpl*, bool >> > (testing::internal::UnitTestImpl::*)(), char const*) () >> >from >> > /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 >> > #8 0x77f9e3cc in testing::UnitTest::Run() () >> >from >> > /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 >> > #9 0x5568eb90 in main () >> > >> > >> > Thanks, >> > -- >> > kou
[jira] [Created] (ARROW-5769) [Java] org.apache.arrow.flight.TestTls is failed via dev/release/00-prepare.sh
Sutou Kouhei created ARROW-5769:
---
Summary: [Java] org.apache.arrow.flight.TestTls is failed via
dev/release/00-prepare.sh
Key: ARROW-5769
URL: https://issues.apache.org/jira/browse/ARROW-5769
Project: Apache Arrow
Issue Type: Test
Components: Java
Reporter: Sutou Kouhei
Fix For: 0.14.0
Details:
{noformat}
[INFO] [INFO] Running org.apache.arrow.flight.TestTls
[INFO] [ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed:
0.005 s <<< FAILURE! - in org.apache.arrow.flight.TestTls
[INFO] [ERROR] connectTls(org.apache.arrow.flight.TestTls) Time elapsed: 0.004
s <<< ERROR!
[INFO] java.lang.RuntimeException: java.io.FileNotFoundException:
/home/kou/work/cpp/arrow.pravindra/java/flight/../../testing/data/flight/cert0.pem
(No such file or directory)
[INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:105)
[INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98)
[INFO] at org.apache.arrow.flight.TestTls.connectTls(TestTls.java:44)
[INFO] Caused by: java.io.FileNotFoundException:
/home/kou/work/cpp/arrow.pravindra/java/flight/../../testing/data/flight/cert0.pem
(No such file or directory)
[INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:102)
[INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98)
[INFO] at org.apache.arrow.flight.TestTls.connectTls(TestTls.java:44)
[INFO]
[INFO] [ERROR] rejectInvalidCert(org.apache.arrow.flight.TestTls) Time
elapsed: 0 s <<< ERROR!
[INFO] java.lang.Exception: Unexpected exception,
expected but was
[INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:105)
[INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98)
[INFO] at org.apache.arrow.flight.TestTls.rejectInvalidCert(TestTls.java:62)
[INFO] Caused by: java.io.FileNotFoundException:
/home/kou/work/cpp/arrow.pravindra/java/flight/../../testing/data/flight/cert0.pem
(No such file or directory)
[INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:102)
[INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98)
[INFO] at org.apache.arrow.flight.TestTls.rejectInvalidCert(TestTls.java:62)
[INFO]
[INFO] [ERROR] rejectHostname(org.apache.arrow.flight.TestTls) Time elapsed:
0.001 s <<< ERROR!
[INFO] java.lang.Exception: Unexpected exception,
expected but was
[INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:105)
[INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98)
[INFO] at org.apache.arrow.flight.TestTls.rejectHostname(TestTls.java:78)
[INFO] Caused by: java.io.FileNotFoundException:
/home/kou/work/cpp/arrow.pravindra/java/flight/../../testing/data/flight/cert0.pem
(No such file or directory)
[INFO] at org.apache.arrow.flight.TestTls.lambda$test$3(TestTls.java:102)
[INFO] at org.apache.arrow.flight.TestTls.test(TestTls.java:98)
[INFO] at org.apache.arrow.flight.TestTls.rejectHostname(TestTls.java:78)
[INFO]
[INFO] [INFO] Running org.apache.arrow.flight.TestServerOptions
[INFO] [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
0.114 s - in org.apache.arrow.flight.TestServerOptions
[INFO] [INFO]
[INFO] [INFO] Results:
[INFO] [INFO]
[INFO] [ERROR] Errors:
[INFO] [ERROR] TestTls.connectTls:44->test:98->lambda$test$3:105 Runtime
java.io.FileNotFound...
[INFO] [ERROR] TestTls.rejectHostname » Unexpected exception,
expected
[jira] [Created] (ARROW-5768) [Release] There are needless newlines at the end of CHANGELOG.md
Sutou Kouhei created ARROW-5768: --- Summary: [Release] There are needless newlines at the end of CHANGELOG.md Key: ARROW-5768 URL: https://issues.apache.org/jira/browse/ARROW-5768 Project: Apache Arrow Issue Type: Improvement Components: Developer Tools Reporter: Sutou Kouhei Assignee: Sutou Kouhei Fix For: 0.14.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [ANNOUNCE] New Arrow committer: Praveen Kumar
Congrats Praveen! Sent from my iPhone > On 28-Jun-2019, at 1:55 AM, Wes McKinney wrote: > > On behalf of the Arrow PMC I'm happy to announce that Praveen has > accepted an invitation to become an Arrow committer! > > Welcome, and thank you for your contributions!
Re: [Discuss][Java][Typical use cases for dictionary encoding string vectors]
hi Liya, I left a couple of comments in the document. You might look at what we have developed in C++ and JavaSript which is more mature and widely used in those languages than what currently exists in Java. In particular, I strongly encourage you to avoid creating a coupling between the Schema (which indicates the "index type" and the "dictionary type") and the Data (which contains the "dictionary indices" and the "dictionary values"). If you do this, then it is nearly impossible to account for dictionary changes in a stream of data, which is already supported in the IPC protocol, see https://github.com/apache/arrow/blob/master/docs/source/format/IPC.rst#dictionary-batches The protocol does not permit dictionaries to change order altogether, but I think it should. I just opened https://issues.apache.org/jira/browse/ARROW-5767 We made this mistake early in the C++ library and found it difficult to have to reconciled dictionaries produced by different threads of execution. See ARROW-3144 and the patch I wrote in this release cycle which addressed this design flaw. Thanks Wes On Wed, Jun 12, 2019 at 5:33 AM Fan Liya wrote: > > @Micah Kornfield Thanks a lot for your comments. > > In the doc, we identify 3 problems for the current dictionary encoding use > case (there can be more, so please give your valuable suggestions): > > 1. there should be a convenient way to provide access to both > encoded/decoded data. > 2. the constructor for the schema with dictionary is misleading. > 3. we should provide a way to do the encoding/decoding during > serialization/deserialization, so the encoding/decoding can be transparent > to the user. > > The current PR provides a solution for problem 2, and it is a relatively > small change, so we think we can merge this PR first. > > Solutions for problem 1 and 3 should be chosen carefully so as not to > affect existing APIs. So more discussions/designs for problems 1 and 3 are > desired. > Do you think it reasonable? > > Best, > Liya Fan > > > > On Wed, Jun 12, 2019 at 4:01 PM Micah Kornfield > wrote: > > > Hi Liya Fan, > > Thanks you for doing this. I need to take a closer look at the PR in > > question and the dictionary encoding code but this seems like it is on the > > right track. > > > > Could other java contributors with more familiarity in the space look over > > the document to make sure it makes sense to them? > > > > Thanks, > > Micah > > > > On Mon, Jun 10, 2019 at 2:23 AM Fan Liya wrote: > > > > > Hi all, > > > > > > This is concerning issue ARROW-3396. > > > > > > I have summarized the problem (please see if my understanding is > > correct), > > > and proposed some solutions to it. Please give your valuable feedback. > > > For details, please see: > > > > > > > > > > > https://docs.google.com/document/d/1Y2E6RbZkUj3SwuEJrlEjaeIPmCA1SIsi9wmbJmVlB2I/edit?usp=sharing > > > > > > Thank you in advance. > > > > > > Best, > > > Liya Fan > > > > >
[jira] [Created] (ARROW-5767) [Format] Permit dictionary replacements in IPC protocol
Wes McKinney created ARROW-5767:
---
Summary: [Format] Permit dictionary replacements in IPC protocol
Key: ARROW-5767
URL: https://issues.apache.org/jira/browse/ARROW-5767
Project: Apache Arrow
Issue Type: New Feature
Components: Format
Reporter: Wes McKinney
Fix For: 1.0.0
We permit dictionaries to grow using the {{isDelta}} property in the IPC
protocol. I think it should be allowed for the same dictionary ID to appear in
an IPC protocol stream but with {{isDelta=false}}. This would indicate that the
dictionary in that message is to replace any prior-observed ones in subsequent
record batches.
For example, we might have dictionary batches in a stream:
{code}
id: 0 isDelta: false values: [a, b, c]
id: 0 isDelta: true values [d]
id 0 isDelta: false values [c, a, b]
{code}
Such data could easily be produced by a stream producer that is creating
dictionaries in different execution threads.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: 0.14.0: C++ TestDictionary.Validate is crashed with release build
Patch here: https://github.com/apache/arrow/pull/4730 We aren't testing release builds of the C++ project at all in Travis CI. The longer build times probably pose a problem anyway, so I have set up a docker-compose build so we can add this to Ursabot to prevent this from happening in the future On Thu, Jun 27, 2019 at 4:49 PM Wes McKinney wrote: > > hi Kou, > > I'm taking a look now. > > - Wes > > On Thu, Jun 27, 2019 at 4:47 PM Sutou Kouhei wrote: > > > > Hi, > > > > I'm testing dev/release/verify-release-candidate.sh that is > > a script to verify RC. > > > > I found that TestDictionary.Validate C++ test is crashed > > with release build. Note that this isn't crashed with debug > > build. > > > > Could C++ developers take a look this? > > > > JIRA: https://issues.apache.org/jira/browse/ARROW-5765 > > This includes CMake options I used to reproduce this. > > > > Backtrace: > > > > (gdb) bt > > #0 0x776b3bba in > > arrow::DictionaryArray::DictionaryArray(std::shared_ptr > > const&, std::shared_ptr const&, std::shared_ptr > > const&) () > >from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow.so.14 > > #1 0x557ba6c3 in arrow::TestDictionary_Validate_Test::TestBody() () > > #2 0x77fa725a in void > > testing::internal::HandleExceptionsInMethodIfSupported > void>(testing::Test*, void (testing::Test::*)(), char const*) () > >from > > /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 > > #3 0x77f9db5a in testing::Test::Run() () > >from > > /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 > > #4 0x77f9dca8 in testing::TestInfo::Run() () > >from > > /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 > > #5 0x77f9dd85 in testing::TestCase::Run() () > >from > > /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 > > #6 0x77f9e29c in testing::internal::UnitTestImpl::RunAllTests() () > >from > > /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 > > #7 0x77fa776a in bool > > testing::internal::HandleExceptionsInMethodIfSupported > bool>(testing::internal::UnitTestImpl*, bool > > (testing::internal::UnitTestImpl::*)(), char const*) () > >from > > /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 > > #8 0x77f9e3cc in testing::UnitTest::Run() () > >from > > /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 > > #9 0x5568eb90 in main () > > > > > > Thanks, > > -- > > kou
Re: 0.14.0: C++ TestDictionary.Validate is crashed with release build
hi Kou, I'm taking a look now. - Wes On Thu, Jun 27, 2019 at 4:47 PM Sutou Kouhei wrote: > > Hi, > > I'm testing dev/release/verify-release-candidate.sh that is > a script to verify RC. > > I found that TestDictionary.Validate C++ test is crashed > with release build. Note that this isn't crashed with debug > build. > > Could C++ developers take a look this? > > JIRA: https://issues.apache.org/jira/browse/ARROW-5765 > This includes CMake options I used to reproduce this. > > Backtrace: > > (gdb) bt > #0 0x776b3bba in > arrow::DictionaryArray::DictionaryArray(std::shared_ptr > const&, std::shared_ptr const&, std::shared_ptr > const&) () >from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow.so.14 > #1 0x557ba6c3 in arrow::TestDictionary_Validate_Test::TestBody() () > #2 0x77fa725a in void > testing::internal::HandleExceptionsInMethodIfSupported void>(testing::Test*, void (testing::Test::*)(), char const*) () >from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 > #3 0x77f9db5a in testing::Test::Run() () >from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 > #4 0x77f9dca8 in testing::TestInfo::Run() () >from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 > #5 0x77f9dd85 in testing::TestCase::Run() () >from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 > #6 0x77f9e29c in testing::internal::UnitTestImpl::RunAllTests() () >from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 > #7 0x77fa776a in bool > testing::internal::HandleExceptionsInMethodIfSupported bool>(testing::internal::UnitTestImpl*, bool > (testing::internal::UnitTestImpl::*)(), char const*) () >from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 > #8 0x77f9e3cc in testing::UnitTest::Run() () >from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 > #9 0x5568eb90 in main () > > > Thanks, > -- > kou
0.14.0: C++ TestDictionary.Validate is crashed with release build
Hi, I'm testing dev/release/verify-release-candidate.sh that is a script to verify RC. I found that TestDictionary.Validate C++ test is crashed with release build. Note that this isn't crashed with debug build. Could C++ developers take a look this? JIRA: https://issues.apache.org/jira/browse/ARROW-5765 This includes CMake options I used to reproduce this. Backtrace: (gdb) bt #0 0x776b3bba in arrow::DictionaryArray::DictionaryArray(std::shared_ptr const&, std::shared_ptr const&, std::shared_ptr const&) () from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow.so.14 #1 0x557ba6c3 in arrow::TestDictionary_Validate_Test::TestBody() () #2 0x77fa725a in void testing::internal::HandleExceptionsInMethodIfSupported(testing::Test*, void (testing::Test::*)(), char const*) () from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 #3 0x77f9db5a in testing::Test::Run() () from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 #4 0x77f9dca8 in testing::TestInfo::Run() () from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 #5 0x77f9dd85 in testing::TestCase::Run() () from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 #6 0x77f9e29c in testing::internal::UnitTestImpl::RunAllTests() () from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 #7 0x77fa776a in bool testing::internal::HandleExceptionsInMethodIfSupported(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) () from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 #8 0x77f9e3cc in testing::UnitTest::Run() () from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14 #9 0x5568eb90 in main () Thanks, -- kou
[jira] [Created] (ARROW-5766) [Python] Unpin jpype1 version
Wes McKinney created ARROW-5766: --- Summary: [Python] Unpin jpype1 version Key: ARROW-5766 URL: https://issues.apache.org/jira/browse/ARROW-5766 Project: Apache Arrow Issue Type: Improvement Components: Python Reporter: Wes McKinney Fix For: 1.0.0 According to the discussion in https://github.com/conda-forge/jpype1-feedstock/issues/8 htere are some changes that we must make to our code to stay on the released version of jpype1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-5765) [C++] TestDictionary.Validate test is crashed with release build
Sutou Kouhei created ARROW-5765:
---
Summary: [C++] TestDictionary.Validate test is crashed with
release build
Key: ARROW-5765
URL: https://issues.apache.org/jira/browse/ARROW-5765
Project: Apache Arrow
Issue Type: Bug
Components: C++
Reporter: Sutou Kouhei
Fix For: 0.14.0
Here is a backtrace:
{noformat}
(gdb) bt
#0 0x776b3bba in
arrow::DictionaryArray::DictionaryArray(std::shared_ptr
const&, std::shared_ptr const&, std::shared_ptr
const&) ()
from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow.so.14
#1 0x557ba6c3 in arrow::TestDictionary_Validate_Test::TestBody() ()
#2 0x77fa725a in void
testing::internal::HandleExceptionsInMethodIfSupported(testing::Test*, void (testing::Test::*)(), char const*) ()
from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14
#3 0x77f9db5a in testing::Test::Run() ()
from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14
#4 0x77f9dca8 in testing::TestInfo::Run() ()
from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14
#5 0x77f9dd85 in testing::TestCase::Run() ()
from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14
#6 0x77f9e29c in testing::internal::UnitTestImpl::RunAllTests() ()
from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14
#7 0x77fa776a in bool
testing::internal::HandleExceptionsInMethodIfSupported(testing::internal::UnitTestImpl*, bool
(testing::internal::UnitTestImpl::*)(), char const*) ()
from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14
#8 0x77f9e3cc in testing::UnitTest::Run() ()
from /home/kou/work/cpp/arrow.kou/cpp/build/release/libarrow_testing.so.14
#9 0x5568eb90 in main ()
{noformat}
It's not occurred with debug build.
Here are CMake options I used:
{noformat}
rm -rf build
mkdir -p build
cd build
CUDA_TOOLKIT_ROOT=/usr \
cmake .. \
-G Ninja \
-DCMAKE_INSTALL_PREFIX=/tmp/local \
-DCMAKE_BUILD_TYPE=release \
-DARROW_PYTHON=on \
-DPythonInterp_FIND_VERSION=on \
-DPythonInterp_FIND_VERSION_MAJOR=3 \
-DARROW_PLASMA=on \
-DARROW_CUDA=on \
-DARROW_EXTRA_ERROR_CONTEXT=on \
-DARROW_ORC=on \
-DARROW_PARQUET=on \
-DARROW_GANDIVA=on \
-DARROW_BUILD_TESTS=on \
-DARROW_FLIGHT=on
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: 0.14.0: Javadoc failed with OpenJDK 11
hi Kou, I think that JDK8 is still treated as the "main production JDK version" but based on https://blogs.oracle.com/java-platform-group/end-of-public-updates-is-a-process%2c-not-an-event it seems like the project should cease JDK8 support at some point in the next 18 months (or sooner). I think it is OK to make the release using JDK8 I will let the Java stakeholders comment about what they want to do. There are still a few patches that need to be merged until the RC0 so there is a bit of time yet. Hopefully we can have everything resolved within the next 12 hours Thanks, Wes On Thu, Jun 27, 2019 at 4:24 PM Sutou Kouhei wrote: > > Hi, > > I'm trying to run dev/release/00-prepare.sh that is the > first script to create RC. > > It fails with OpenJDK 11 by the following Javadoc error: > > [ERROR] Exit code: 1 - javadoc: error - The code being documented uses > modules but the packages defined in http://docs.oracle.com/javase/8/docs/api/ > are in the unnamed module. > > "-source 8" javadoc option can suppress the error but I'm > not sure what should we do. > > See also: https://issues.apache.org/jira/browse/ARROW-5764 > > I found that OpenJDK 8 doesn't cause the error. So I can go > ahead with OpenJDK 8. But I want feedback from Java > developers to know we should use OpenJDK 8 for release. > > > Thanks, > -- > kou
0.14.0: Javadoc failed with OpenJDK 11
Hi, I'm trying to run dev/release/00-prepare.sh that is the first script to create RC. It fails with OpenJDK 11 by the following Javadoc error: [ERROR] Exit code: 1 - javadoc: error - The code being documented uses modules but the packages defined in http://docs.oracle.com/javase/8/docs/api/ are in the unnamed module. "-source 8" javadoc option can suppress the error but I'm not sure what should we do. See also: https://issues.apache.org/jira/browse/ARROW-5764 I found that OpenJDK 8 doesn't cause the error. So I can go ahead with OpenJDK 8. But I want feedback from Java developers to know we should use OpenJDK 8 for release. Thanks, -- kou
[jira] [Created] (ARROW-5764) [Java] Failed to build document with OpenJDK 11
Sutou Kouhei created ARROW-5764:
---
Summary: [Java] Failed to build document with OpenJDK 11
Key: ARROW-5764
URL: https://issues.apache.org/jira/browse/ARROW-5764
Project: Apache Arrow
Issue Type: Bug
Components: Java
Reporter: Sutou Kouhei
Fix For: 0.14.0
It reports the following error:
{noformat}
[ERROR] Exit code: 1 - javadoc: error - The code being documented uses modules
but the packages defined in http://docs.oracle.com/javase/8/docs/api/ are in
the unnamed module.
{noformat}
See also: https://travis-ci.org/kou/arrow/jobs/551254733#L1453
This branch just enables Javadoc with OpenJDK 11:
https://github.com/kou/arrow/commit/1eeded4b9d18d474721733751f57392cee766004.diff
{noformat}
diff --git a/.travis.yml b/.travis.yml
index 5dc901561e8..1d6ba86dc2d 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -225,6 +225,7 @@ matrix:
- if [ $ARROW_CI_JAVA_AFFECTED != "1" ]; then exit; fi
script:
- $TRAVIS_BUILD_DIR/ci/travis_script_java.sh
+- $TRAVIS_BUILD_DIR/ci/travis_script_javadoc.sh
- name: "Integration w/ OpenJDK 8, conda-forge toolchain"
language: java
os: linux
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: [ANNOUNCE] New Arrow committer: Praveen Kumar
Congratulations Praveen! On Thu, Jun 27, 2019 at 1:35 PM Micah Kornfield wrote: > Congrats Praveen! > > On Thursday, June 27, 2019, Wes McKinney wrote: > > > On behalf of the Arrow PMC I'm happy to announce that Praveen has > > accepted an invitation to become an Arrow committer! > > > > Welcome, and thank you for your contributions! > > >
Re: [ANNOUNCE] New Arrow committer: Praveen Kumar
Congrats Praveen! On Thursday, June 27, 2019, Wes McKinney wrote: > On behalf of the Arrow PMC I'm happy to announce that Praveen has > accepted an invitation to become an Arrow committer! > > Welcome, and thank you for your contributions! >
[ANNOUNCE] New Arrow committer: Praveen Kumar
On behalf of the Arrow PMC I'm happy to announce that Praveen has accepted an invitation to become an Arrow committer! Welcome, and thank you for your contributions!
[jira] [Created] (ARROW-5763) [JS] enable integration tests for MapVector
Benjamin Kietzman created ARROW-5763: Summary: [JS] enable integration tests for MapVector Key: ARROW-5763 URL: https://issues.apache.org/jira/browse/ARROW-5763 Project: Apache Arrow Issue Type: New Feature Components: JavaScript Reporter: Benjamin Kietzman As of 0.14, C++ and Java support Map arrays those implementations pass integration tests. JS has a MapVector and some unit tests for it, but it should be tested against other implementations as well -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-5762) [Integration][JS] Integration Tests for MapType
Bryan Cutler created ARROW-5762:
---
Summary: [Integration][JS] Integration Tests for MapType
Key: ARROW-5762
URL: https://issues.apache.org/jira/browse/ARROW-5762
Project: Apache Arrow
Issue Type: Improvement
Components: Integration, JavaScript
Reporter: Bryan Cutler
ARROW-1279 enabled integration tests for MapType between Java and C++, but
JavaScript had to be disabled for the map case due to an error. Once this is
fixed, {{generate_map_case}} could be moved under {{generate_nested_case}} with
the other nested types.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARROW-5761) [R] Improve autosplice cpp code
Neal Richardson created ARROW-5761: -- Summary: [R] Improve autosplice cpp code Key: ARROW-5761 URL: https://issues.apache.org/jira/browse/ARROW-5761 Project: Apache Arrow Issue Type: Improvement Reporter: Neal Richardson Assignee: Romain François Followup to ARROW-5178. See discussion on [https://github.com/apache/arrow/pull/4704]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-5759) Suspend CI builds for draft pull requests on GitHub
Prudhvi Porandla created ARROW-5759: --- Summary: Suspend CI builds for draft pull requests on GitHub Key: ARROW-5759 URL: https://issues.apache.org/jira/browse/ARROW-5759 Project: Apache Arrow Issue Type: Task Components: Continuous Integration Reporter: Prudhvi Porandla CI should be disabled for draft pull requests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-5758) [C++][Gandiva] Support casting decimals to varchar and vice versa
Prudhvi Porandla created ARROW-5758: --- Summary: [C++][Gandiva] Support casting decimals to varchar and vice versa Key: ARROW-5758 URL: https://issues.apache.org/jira/browse/ARROW-5758 Project: Apache Arrow Issue Type: Task Components: C++ - Gandiva Reporter: Prudhvi Porandla Assignee: Prudhvi Porandla Add castDecimal(varchar), castVarchar(Decimal) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-5757) [Python] Stop supporting Python 2.7
Antoine Pitrou created ARROW-5757: - Summary: [Python] Stop supporting Python 2.7 Key: ARROW-5757 URL: https://issues.apache.org/jira/browse/ARROW-5757 Project: Apache Arrow Issue Type: Task Components: Python Reporter: Antoine Pitrou By the end of 2019 many scientific Python projects will stop supporting Python 2 altogether: https://python3statement.org/ We'll certainly support Python 2 in Arrow 1.0 but we could perhaps drop support in 1.1. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-5756) [Python] Remove manylinux1 support
Antoine Pitrou created ARROW-5756: - Summary: [Python] Remove manylinux1 support Key: ARROW-5756 URL: https://issues.apache.org/jira/browse/ARROW-5756 Project: Apache Arrow Issue Type: Task Components: Packaging, Python Reporter: Antoine Pitrou We should decide when we want to stop producing manylinux1 packages. Installing manylinux2010 packages requires a recent pip (and, obviously, a not-too-antiquated system, but I think that's less of a problem for us). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARROW-5755) [Rust] [Parquet] Add derived clone for Type
Renjie Liu created ARROW-5755: - Summary: [Rust] [Parquet] Add derived clone for Type Key: ARROW-5755 URL: https://issues.apache.org/jira/browse/ARROW-5755 Project: Apache Arrow Issue Type: New Feature Reporter: Renjie Liu Assignee: Renjie Liu Add clone for Type -- This message was sent by Atlassian JIRA (v7.6.3#76005)
