[jira] [Created] (ARROW-8744) [Rust] ParquetIterator's next method should be safe to call even after reached end of iteration

2020-05-08 Thread QP Hou (Jira)
QP Hou created ARROW-8744:
-

 Summary: [Rust] ParquetIterator's next method should be safe to 
call even after reached end of iteration
 Key: ARROW-8744
 URL: https://issues.apache.org/jira/browse/ARROW-8744
 Project: Apache Arrow
  Issue Type: Improvement
Reporter: QP Hou
Assignee: QP Hou


Once reached end of iteration, calling next on ParquetIterator will result in 
an error. This is inconvenient in two ways:
* when shared between multiple threads, only one of the thread will be able to 
terminate without error
* sender for response_rx cannot terminate the iteration early and free up 
resources, instead, it needs to always wait for signal from request_tx before 
closing up the connection



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ARROW-8744) [Rust] ParquetIterator's next method should be safe to call even after reached end of iteration

2020-05-08 Thread QP Hou (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

QP Hou updated ARROW-8744:
--
Component/s: Rust - DataFusion
   Priority: Minor  (was: Major)

> [Rust] ParquetIterator's next method should be safe to call even after 
> reached end of iteration
> ---
>
> Key: ARROW-8744
> URL: https://issues.apache.org/jira/browse/ARROW-8744
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: Rust - DataFusion
>Reporter: QP Hou
>Assignee: QP Hou
>Priority: Minor
>
> Once reached end of iteration, calling next on ParquetIterator will result in 
> an error. This is inconvenient in two ways:
> * when shared between multiple threads, only one of the thread will be able 
> to terminate without error
> * sender for response_rx cannot terminate the iteration early and free up 
> resources, instead, it needs to always wait for signal from request_tx before 
> closing up the connection



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (ARROW-8743) [C++][CI] Add a test job on s390x

2020-05-08 Thread Kouhei Sutou (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kouhei Sutou resolved ARROW-8743.
-
Fix Version/s: 1.0.0
   Resolution: Fixed

Issue resolved by pull request 7131
[https://github.com/apache/arrow/pull/7131]

> [C++][CI] Add a test job on s390x
> -
>
> Key: ARROW-8743
> URL: https://issues.apache.org/jira/browse/ARROW-8743
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: C++, Continuous Integration
>Reporter: Kouhei Sutou
>Assignee: Kouhei Sutou
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.0.0
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ARROW-3509) [C++] Inconsistent child accessor naming

2020-05-08 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated ARROW-3509:
--
Labels: pull-request-available  (was: )

> [C++] Inconsistent child accessor naming
> 
>
> Key: ARROW-3509
> URL: https://issues.apache.org/jira/browse/ARROW-3509
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: C++
>Reporter: Krisztian Szucs
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> {code}
> UnionArray::child
> StructArray::field
> DataType::child
> StructType::child
> Schema::field
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ARROW-8743) [C++][CI] Add a test job on s390x

2020-05-08 Thread Kouhei Sutou (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kouhei Sutou updated ARROW-8743:

Summary: [C++][CI] Add a test job on s390x  (was: [C++][CI] Add a job on 
s390x)

> [C++][CI] Add a test job on s390x
> -
>
> Key: ARROW-8743
> URL: https://issues.apache.org/jira/browse/ARROW-8743
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: C++, Continuous Integration
>Reporter: Kouhei Sutou
>Assignee: Kouhei Sutou
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ARROW-8743) [C++][CI] Add a test job on s390x

2020-05-08 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated ARROW-8743:
--
Labels: pull-request-available  (was: )

> [C++][CI] Add a test job on s390x
> -
>
> Key: ARROW-8743
> URL: https://issues.apache.org/jira/browse/ARROW-8743
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: C++, Continuous Integration
>Reporter: Kouhei Sutou
>Assignee: Kouhei Sutou
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ARROW-8743) [C++][CI] Add a job on s390x

2020-05-08 Thread Kouhei Sutou (Jira)
Kouhei Sutou created ARROW-8743:
---

 Summary: [C++][CI] Add a job on s390x
 Key: ARROW-8743
 URL: https://issues.apache.org/jira/browse/ARROW-8743
 Project: Apache Arrow
  Issue Type: Improvement
  Components: C++, Continuous Integration
Reporter: Kouhei Sutou
Assignee: Kouhei Sutou






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (ARROW-8724) [Packaging][deb][RPM] Use directory in host as build directory

2020-05-08 Thread Kouhei Sutou (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kouhei Sutou resolved ARROW-8724.
-
Fix Version/s: 1.0.0
   Resolution: Fixed

Issue resolved by pull request 7118
[https://github.com/apache/arrow/pull/7118]

> [Packaging][deb][RPM] Use directory in host as build directory
> --
>
> Key: ARROW-8724
> URL: https://issues.apache.org/jira/browse/ARROW-8724
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: Packaging
>Reporter: Kouhei Sutou
>Assignee: Kouhei Sutou
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.0.0
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (ARROW-8727) [C++] Do not require struct-initialization of StringConverter to parse strings to other types

2020-05-08 Thread Ben Kietzman (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ben Kietzman reassigned ARROW-8727:
---

Assignee: Wes McKinney

> [C++] Do not require struct-initialization of StringConverter to parse 
> strings to other types
> 
>
> Key: ARROW-8727
> URL: https://issues.apache.org/jira/browse/ARROW-8727
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: C++
>Reporter: Wes McKinney
>Assignee: Wes McKinney
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.0.0
>
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> I ran into this issue while working on refactoring kernels. 
> {{StringConverter}} must be initialized to be able to support parametric 
> types like Timestamp, but this produces an awkwardness and possibly a 
> performance penalty (I haven't measured yet) in inlined functions. 
> In any case, I'm refactoring everything to be static non-stateful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (ARROW-8727) [C++] Do not require struct-initialization of StringConverter to parse strings to other types

2020-05-08 Thread Ben Kietzman (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ben Kietzman resolved ARROW-8727.
-
Resolution: Fixed

Issue resolved by pull request 7120
[https://github.com/apache/arrow/pull/7120]

> [C++] Do not require struct-initialization of StringConverter to parse 
> strings to other types
> 
>
> Key: ARROW-8727
> URL: https://issues.apache.org/jira/browse/ARROW-8727
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: C++
>Reporter: Wes McKinney
>Assignee: Wes McKinney
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.0.0
>
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> I ran into this issue while working on refactoring kernels. 
> {{StringConverter}} must be initialized to be able to support parametric 
> types like Timestamp, but this produces an awkwardness and possibly a 
> performance penalty (I haven't measured yet) in inlined functions. 
> In any case, I'm refactoring everything to be static non-stateful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ARROW-8742) [C++][Python] Add flight client support for Mutual TLS

2020-05-08 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated ARROW-8742:
--
Labels: pull-request-available  (was: )

> [C++][Python] Add flight client support for Mutual TLS
> --
>
> Key: ARROW-8742
> URL: https://issues.apache.org/jira/browse/ARROW-8742
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: C++, Python
>Reporter: Erin Ryan
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> For security sake, our team is trying to implement the GRPC option for mutual 
> TLS for a python flight client. Both C++ and Python need edits for this 
> implementation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ARROW-8742) [C++][Python] Add flight client support for Mutual TLS

2020-05-08 Thread Erin Ryan (Jira)
Erin Ryan created ARROW-8742:


 Summary: [C++][Python] Add flight client support for Mutual TLS
 Key: ARROW-8742
 URL: https://issues.apache.org/jira/browse/ARROW-8742
 Project: Apache Arrow
  Issue Type: Improvement
  Components: C++, Python
Reporter: Erin Ryan


For security sake, our team is trying to implement the GRPC option for mutual 
TLS for a python flight client. Both C++ and Python need edits for this 
implementation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (ARROW-5875) [FlightRPC] Test RPC features in integration tests

2020-05-08 Thread Wes McKinney (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wes McKinney resolved ARROW-5875.
-
Resolution: Fixed

Issue resolved by pull request 6617
[https://github.com/apache/arrow/pull/6617]

> [FlightRPC] Test RPC features in integration tests
> --
>
> Key: ARROW-5875
> URL: https://issues.apache.org/jira/browse/ARROW-5875
> Project: Apache Arrow
>  Issue Type: Test
>  Components: FlightRPC, Integration
>Affects Versions: 0.14.0
>Reporter: David Li
>Assignee: David Li
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.0.0
>
>  Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> We should test not just wire-format compatibility, but feature-compatibility 
> in Flight integration tests. This may mean adding a separate suite of tests 
> to the integration script.
> Features that should be tested include:
>  * Authentication
>  * Error & error code propagation
>  * Cancellation
>  * Flow control/backpressure



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (ARROW-5875) [FlightRPC] Test RPC features in integration tests

2020-05-08 Thread Wes McKinney (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wes McKinney reassigned ARROW-5875:
---

Assignee: David Li

> [FlightRPC] Test RPC features in integration tests
> --
>
> Key: ARROW-5875
> URL: https://issues.apache.org/jira/browse/ARROW-5875
> Project: Apache Arrow
>  Issue Type: Test
>  Components: FlightRPC, Integration
>Affects Versions: 0.14.0
>Reporter: David Li
>Assignee: David Li
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.0.0
>
>  Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> We should test not just wire-format compatibility, but feature-compatibility 
> in Flight integration tests. This may mean adding a separate suite of tests 
> to the integration script.
> Features that should be tested include:
>  * Authentication
>  * Error & error code propagation
>  * Cancellation
>  * Flow control/backpressure



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ARROW-5875) [FlightRPC] Test RPC features in integration tests

2020-05-08 Thread Wes McKinney (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wes McKinney updated ARROW-5875:

Fix Version/s: (was: 2.0.0)
   1.0.0

> [FlightRPC] Test RPC features in integration tests
> --
>
> Key: ARROW-5875
> URL: https://issues.apache.org/jira/browse/ARROW-5875
> Project: Apache Arrow
>  Issue Type: Test
>  Components: FlightRPC, Integration
>Affects Versions: 0.14.0
>Reporter: David Li
>Assignee: David Li
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.0.0
>
>  Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> We should test not just wire-format compatibility, but feature-compatibility 
> in Flight integration tests. This may mean adding a separate suite of tests 
> to the integration script.
> Features that should be tested include:
>  * Authentication
>  * Error & error code propagation
>  * Cancellation
>  * Flow control/backpressure



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (ARROW-1614) [C++] Add a Tensor logical value type with constant dimensions, implemented using ExtensionType

2020-05-08 Thread Christian Hudon (Jira)


[ 
https://issues.apache.org/jira/browse/ARROW-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17102790#comment-17102790
 ] 

Christian Hudon commented on ARROW-1614:


[~jorisvandenbossche] Thanks for all the doc pointers. I think I'll start with 
a Python prototype, then, as that'll be a lot faster to experiment with. Once 
we're good with the results of that, I'll port it to C++.

> [C++] Add a Tensor logical value type with constant dimensions, implemented 
> using ExtensionType
> ---
>
> Key: ARROW-1614
> URL: https://issues.apache.org/jira/browse/ARROW-1614
> Project: Apache Arrow
>  Issue Type: New Feature
>  Components: C++, Format
>Reporter: Wes McKinney
>Priority: Major
>
> In an Arrow table, we would like to add support for a column that has values 
> cells each containing a tensor value, with all tensors having the same 
> dimensions. These would be stored as a binary value, plus some metadata to 
> store type and shape/strides.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ARROW-8741) [Python][Packaging] Keep VS2015 with bundled dependencies for the windows wheels

2020-05-08 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated ARROW-8741:
--
Labels: pull-request-available  (was: )

> [Python][Packaging] Keep VS2015 with bundled dependencies for the windows 
> wheels
> 
>
> Key: ARROW-8741
> URL: https://issues.apache.org/jira/browse/ARROW-8741
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: Packaging
>Reporter: Krisztian Szucs
>Assignee: Krisztian Szucs
>Priority: Major
>  Labels: pull-request-available
> Fix For: 0.17.1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The windows wheels needs to be fixed for the release.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ARROW-8741) [Python][Packaging] Keep VS2015 with bundled dependencies for the windows wheels

2020-05-08 Thread Krisztian Szucs (Jira)
Krisztian Szucs created ARROW-8741:
--

 Summary: [Python][Packaging] Keep VS2015 with bundled dependencies 
for the windows wheels
 Key: ARROW-8741
 URL: https://issues.apache.org/jira/browse/ARROW-8741
 Project: Apache Arrow
  Issue Type: Improvement
  Components: Packaging
Reporter: Krisztian Szucs
Assignee: Krisztian Szucs
 Fix For: 0.17.1


The windows wheels needs to be fixed for the release.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (ARROW-8739) [Java] Standardise Logger naming

2020-05-08 Thread Wes McKinney (Jira)


[ 
https://issues.apache.org/jira/browse/ARROW-8739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17102663#comment-17102663
 ] 

Wes McKinney commented on ARROW-8739:
-

If you would please add "[$COMPONENT]" to the issue title

> [Java] Standardise Logger naming
> 
>
> Key: ARROW-8739
> URL: https://issues.apache.org/jira/browse/ARROW-8739
> Project: Apache Arrow
>  Issue Type: Task
>  Components: Java
>Reporter: Ryan Murray
>Priority: Minor
>
> As per: https://github.com/apache/arrow/pull/7100#discussion_r421884919
> We use LOGGER and logger interchangeably and should choose one



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ARROW-8738) [Java] Investigate adding a getUnsafe method to vectors

2020-05-08 Thread Wes McKinney (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wes McKinney updated ARROW-8738:

Summary: [Java] Investigate adding a getUnsafe method to vectors  (was: 
Investigate adding a getUnsafe method to vectors)

> [Java] Investigate adding a getUnsafe method to vectors
> ---
>
> Key: ARROW-8738
> URL: https://issues.apache.org/jira/browse/ARROW-8738
> Project: Apache Arrow
>  Issue Type: Task
>  Components: Java
>Reporter: Ryan Murray
>Priority: Major
>
> As per: https://github.com/apache/arrow/pull/7095#issuecomment-625579459



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ARROW-8739) [Java] Standardise Logger naming

2020-05-08 Thread Wes McKinney (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wes McKinney updated ARROW-8739:

Summary: [Java] Standardise Logger naming  (was: Standardise Logger naming)

> [Java] Standardise Logger naming
> 
>
> Key: ARROW-8739
> URL: https://issues.apache.org/jira/browse/ARROW-8739
> Project: Apache Arrow
>  Issue Type: Task
>  Components: Java
>Reporter: Ryan Murray
>Priority: Minor
>
> As per: https://github.com/apache/arrow/pull/7100#discussion_r421884919
> We use LOGGER and logger interchangeably and should choose one



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ARROW-8636) [C++][Plasma] plasma client delete (of objectid) causes an exception and abort

2020-05-08 Thread Wes McKinney (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wes McKinney updated ARROW-8636:

Summary: [C++][Plasma] plasma client delete (of objectid) causes an 
exception and abort  (was: plasma client delete (of objectid) causes an 
exception and abort)

> [C++][Plasma] plasma client delete (of objectid) causes an exception and abort
> --
>
> Key: ARROW-8636
> URL: https://issues.apache.org/jira/browse/ARROW-8636
> Project: Apache Arrow
>  Issue Type: Bug
>  Components: C++
>Reporter: Abe Mammen
>Priority: Major
>
> Built from this git repo.
> for cpp:
> {quote}{quote}ARROW_CHECK_OK(client.Delete(vector\{objectId}));
> get:
> {quote}Check failed: _s.ok() Operation failed: 
> client.Delete(vector\{objectId})
> Bad status: IOError: Encountered unexpected EOF
> 0 libarrow.18.0.0.dylib 0x0001070ed3c4 
> _ZN5arrow4util7CerrLog14PrintBackTraceEv + 52
> 1 libarrow.18.0.0.dylib 0x0001070ed2e2 _ZN5arrow4util7CerrLogD2Ev + 98
> 2 libarrow.18.0.0.dylib 0x0001070ed245 _ZN5arrow4util7CerrLogD1Ev + 21
> 3 libarrow.18.0.0.dylib 0x0001070ed26c _ZN5arrow4util7CerrLogD0Ev + 28
> 4 libarrow.18.0.0.dylib 0x0001070ed152 _ZN5arrow4util8ArrowLogD2Ev + 82
> 5 libarrow.18.0.0.dylib 0x0001070ed185 _ZN5arrow4util8ArrowLogD1Ev + 21
> 6 purge_plasma_messages 0x00010431fe91 main + 2369
> 7 libdyld.dylib 0x7fff6650b7fd start + 1
> 8 ??? 0x0001 0x0 + 1
> Abort trap: 6
> and kills the plasma-store-server.
> {quote}{quote}{quote}
> What could I be doing wrong? Here is the code:
> #include
> #include 
> #include 
> using namespace std;
> using namespace plasma;
> int main(int argc, char** argv)
> {
> // Start up and connect a Plasma client.
> PlasmaClient client;
> ARROW_CHECK_OK(client.Connect("/tmp/plasma_store"));
> std::unordered_map objectTable;
> ARROW_CHECK_OK(client.List());
> cout << "# of objects = " << objectTable.size() << endl;
> for (auto it = objectTable.begin(); it != objectTable.end(); ++it) {
> ObjectID objectId = it->first;
> auto objectEntry = it->second.get();
> string idString = objectId.binary();
> cout << "object id = " << idString <<
> ", device = " << objectEntry->device_num <<
> ", data_size = " << objectEntry->data_size <<
> ", metadata_size = " << objectEntry->metadata_size <<
> ", ref_count = " << objectEntry->ref_count <<
> endl;
> ARROW_CHECK_OK(client.Delete(vector\{objectId}));
> }
> ARROW_CHECK_OK(client.Disconnect());
> }



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (ARROW-8740) [CI] Fix archery option in pandas master cron test

2020-05-08 Thread Krisztian Szucs (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krisztian Szucs resolved ARROW-8740.

Resolution: Fixed

Issue resolved by pull request 7113
[https://github.com/apache/arrow/pull/7113]

> [CI] Fix archery option in pandas master cron test
> --
>
> Key: ARROW-8740
> URL: https://issues.apache.org/jira/browse/ARROW-8740
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: Continuous Integration
>Reporter: Krisztian Szucs
>Assignee: Krisztian Szucs
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 1.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The --no-cache-leaf option was renamed to --no-leaf-cache.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (ARROW-8422) [Rust] [Parquet] Implement function to convert Arrow schema to Parquet schema

2020-05-08 Thread Neville Dipale (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neville Dipale resolved ARROW-8422.
---
Fix Version/s: 1.0.0
   Resolution: Fixed

Issue resolved by pull request 7090
[https://github.com/apache/arrow/pull/7090]

> [Rust] [Parquet] Implement function to convert Arrow schema to Parquet schema
> -
>
> Key: ARROW-8422
> URL: https://issues.apache.org/jira/browse/ARROW-8422
> Project: Apache Arrow
>  Issue Type: Sub-task
>  Components: Rust
>Reporter: Andy Grove
>Assignee: Neville Dipale
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.0.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Implement function to convert Arrow schema to Parquet schema



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ARROW-8740) [CI] Fix archery option in pandas master cron test

2020-05-08 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated ARROW-8740:
--
Labels: pull-request-available  (was: )

> [CI] Fix archery option in pandas master cron test
> --
>
> Key: ARROW-8740
> URL: https://issues.apache.org/jira/browse/ARROW-8740
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: Continuous Integration
>Reporter: Krisztian Szucs
>Assignee: Krisztian Szucs
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 1.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The --no-cache-leaf option was renamed to --no-leaf-cache.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ARROW-8740) [CI] Fix archery option in pandas master cron test

2020-05-08 Thread Krisztian Szucs (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krisztian Szucs updated ARROW-8740:
---
Description: The --no-cache-leaf option was renamed to --no-leaf-cache.

> [CI] Fix archery option in pandas master cron test
> --
>
> Key: ARROW-8740
> URL: https://issues.apache.org/jira/browse/ARROW-8740
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: Continuous Integration
>Reporter: Krisztian Szucs
>Assignee: Krisztian Szucs
>Priority: Minor
> Fix For: 1.0.0
>
>
> The --no-cache-leaf option was renamed to --no-leaf-cache.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ARROW-8740) [CI] Fix archery option in pandas master cron test

2020-05-08 Thread Krisztian Szucs (Jira)
Krisztian Szucs created ARROW-8740:
--

 Summary: [CI] Fix archery option in pandas master cron test
 Key: ARROW-8740
 URL: https://issues.apache.org/jira/browse/ARROW-8740
 Project: Apache Arrow
  Issue Type: Improvement
  Components: Continuous Integration
Reporter: Krisztian Szucs
Assignee: Krisztian Szucs
 Fix For: 1.0.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (ARROW-8643) [Python] Tests with pandas master failing due to freq assertion

2020-05-08 Thread Krisztian Szucs (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krisztian Szucs resolved ARROW-8643.

Fix Version/s: 1.0.0
   Resolution: Fixed

Issue resolved by pull request 7124
[https://github.com/apache/arrow/pull/7124]

> [Python] Tests with pandas master failing due to freq assertion 
> 
>
> Key: ARROW-8643
> URL: https://issues.apache.org/jira/browse/ARROW-8643
> Project: Apache Arrow
>  Issue Type: Test
>  Components: Python
>Reporter: Joris Van den Bossche
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.0.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Nightly pandas master tests are failing, eg 
> https://circleci.com/gh/ursa-labs/crossbow/11858?utm_campaign=vcs-integration-link_medium=referral_source=github-build-link
> This is caused by a change in pandas, see 
> https://github.com/pandas-dev/pandas/pull/33815#issuecomment-620820134



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (ARROW-8643) [Python] Tests with pandas master failing due to freq assertion

2020-05-08 Thread Krisztian Szucs (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krisztian Szucs reassigned ARROW-8643:
--

Assignee: Joris Van den Bossche

> [Python] Tests with pandas master failing due to freq assertion 
> 
>
> Key: ARROW-8643
> URL: https://issues.apache.org/jira/browse/ARROW-8643
> Project: Apache Arrow
>  Issue Type: Test
>  Components: Python
>Reporter: Joris Van den Bossche
>Assignee: Joris Van den Bossche
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.0.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Nightly pandas master tests are failing, eg 
> https://circleci.com/gh/ursa-labs/crossbow/11858?utm_campaign=vcs-integration-link_medium=referral_source=github-build-link
> This is caused by a change in pandas, see 
> https://github.com/pandas-dev/pandas/pull/33815#issuecomment-620820134



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (ARROW-8722) [Dev] "archery docker run -e" doesn't work

2020-05-08 Thread Krisztian Szucs (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krisztian Szucs resolved ARROW-8722.

Fix Version/s: 1.0.0
   Resolution: Fixed

Issue resolved by pull request 7128
[https://github.com/apache/arrow/pull/7128]

> [Dev] "archery docker run -e" doesn't work
> --
>
> Key: ARROW-8722
> URL: https://issues.apache.org/jira/browse/ARROW-8722
> Project: Apache Arrow
>  Issue Type: Bug
>  Components: Developer Tools
>Reporter: Kouhei Sutou
>Assignee: Krisztian Szucs
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.0.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> {noformat}
> $ archery docker run --dry-run -e ARROW_GANDIVA=OFF ubuntu-cpp   
> docker-compose pull --ignore-pull-failures ubuntu-cpp
> docker-compose build ubuntu-cpp
> docker-compose run --rm ubuntu-cpp
> {noformat}
> {{docker-compose run}} doesn't have {{-e ARROW_GANDIVA=OFF}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (ARROW-8730) [Rust] Use slice instead of for function arguments

2020-05-08 Thread Neville Dipale (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neville Dipale resolved ARROW-8730.
---
Resolution: Fixed

Issue resolved by pull request 7125
[https://github.com/apache/arrow/pull/7125]

> [Rust] Use slice instead of  for function arguments
> ---
>
> Key: ARROW-8730
> URL: https://issues.apache.org/jira/browse/ARROW-8730
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: Rust
>Reporter: Andy Grove
>Assignee: Andy Grove
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.0.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> It is best practice to use slice instead of  for function arguments



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ARROW-8739) Standardise Logger naming

2020-05-08 Thread Ryan Murray (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Murray updated ARROW-8739:
---
Priority: Minor  (was: Major)

> Standardise Logger naming
> -
>
> Key: ARROW-8739
> URL: https://issues.apache.org/jira/browse/ARROW-8739
> Project: Apache Arrow
>  Issue Type: Task
>  Components: Java
>Reporter: Ryan Murray
>Priority: Minor
>
> As per: https://github.com/apache/arrow/pull/7100#discussion_r421884919
> We use LOGGER and logger interchangeably and should choose one



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ARROW-8739) Standardise Logger naming

2020-05-08 Thread Ryan Murray (Jira)
Ryan Murray created ARROW-8739:
--

 Summary: Standardise Logger naming
 Key: ARROW-8739
 URL: https://issues.apache.org/jira/browse/ARROW-8739
 Project: Apache Arrow
  Issue Type: Task
  Components: Java
Reporter: Ryan Murray


As per: https://github.com/apache/arrow/pull/7100#discussion_r421884919

We use LOGGER and logger interchangeably and should choose one



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ARROW-8738) Investigate adding a getUnsafe method to vectors

2020-05-08 Thread Ryan Murray (Jira)
Ryan Murray created ARROW-8738:
--

 Summary: Investigate adding a getUnsafe method to vectors
 Key: ARROW-8738
 URL: https://issues.apache.org/jira/browse/ARROW-8738
 Project: Apache Arrow
  Issue Type: Task
  Components: Java
Reporter: Ryan Murray


As per: https://github.com/apache/arrow/pull/7095#issuecomment-625579459



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ARROW-8722) [Dev] "archery docker run -e" doesn't work

2020-05-08 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated ARROW-8722:
--
Labels: pull-request-available  (was: )

> [Dev] "archery docker run -e" doesn't work
> --
>
> Key: ARROW-8722
> URL: https://issues.apache.org/jira/browse/ARROW-8722
> Project: Apache Arrow
>  Issue Type: Bug
>  Components: Developer Tools
>Reporter: Kouhei Sutou
>Assignee: Krisztian Szucs
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> {noformat}
> $ archery docker run --dry-run -e ARROW_GANDIVA=OFF ubuntu-cpp   
> docker-compose pull --ignore-pull-failures ubuntu-cpp
> docker-compose build ubuntu-cpp
> docker-compose run --rm ubuntu-cpp
> {noformat}
> {{docker-compose run}} doesn't have {{-e ARROW_GANDIVA=OFF}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (ARROW-8553) [C++] Reimplement BitmapAnd using Bitmap::VisitWords

2020-05-08 Thread Yibo Cai (Jira)


[ 
https://issues.apache.org/jira/browse/ARROW-8553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17102412#comment-17102412
 ] 

Yibo Cai commented on ARROW-8553:
-

Did a quick test, performance improvement is promising with VisitWords(>10x).

There's one issue need to address. Would like to hear your comments [~apitrou], 
[~bkietz]
VisitWords calls visitor on each word, but bits in first word is unknown to 
visitor, it may be less than a full word size. See 
[code|https://github.com/apache/arrow/blob/6002ec388840de5622e39af85abdc57a29b2/cpp/src/arrow/util/bit_util.h#L960].
It makes it hard to use VisitWords to handle bitmap operations (and, or, ...), 
as I don't how many valid bits to write to output buffer for first word, and 
bit offset of later words cannot be determined. VisitWords returns bit length 
of first word, but it's too late, all visitors are already finished.

I recommend adding a parameter "valid bits" to visitor function, which tells 
how many bits are valid in current word. Only first and last word may be not 
full size.
What's your opinion? Or are there better ways? Thanks.

> [C++] Reimplement BitmapAnd using Bitmap::VisitWords
> 
>
> Key: ARROW-8553
> URL: https://issues.apache.org/jira/browse/ARROW-8553
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: C++
>Affects Versions: 0.17.0
>Reporter: Antoine Pitrou
>Assignee: Yibo Cai
>Priority: Major
>
> Currently, {{BitmapAnd}} uses a bit-by-bit loop for unaligned inputs. Using 
> {{Bitmap::VisitWords}} instead would probably yield a manyfold performance 
> increase.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)