[jira] [Created] (ARROW-6349) ArrowInvalid: Negative ndarray strides not supported

2019-08-24 Thread YUTING ZHANG (Jira)
YUTING ZHANG created ARROW-6349:
---

 Summary: ArrowInvalid: Negative ndarray strides not supported
 Key: ARROW-6349
 URL: https://issues.apache.org/jira/browse/ARROW-6349
 Project: Apache Arrow
  Issue Type: Bug
 Environment: Ubuntu 16.04, python 3.6.6, numpy 1.14.6, pyarrow 0.11.1
Reporter: YUTING ZHANG


When indexing a np.ndarray with negative stride, arrow cannot serialize it. 
However, this could be a common use case for reversing along an axis. 

 

Code:
{code:java}
import pyarrow
import numpy as np
a=np.zeros([500,600,3])
b=a[:,:,::-1]
pyarrow.serialize(b)
{code}
 

Error:
{code:java}
ArrowInvalid Traceback (most recent call last)
 in ()
> 1 pyarrow.serialize(b)
~/anaconda3/envs/mxnet_p36/lib/python3.6/site-packages/pyarrow/serialization.pxi
 in pyarrow.lib.serialize()
~/anaconda3/envs/mxnet_p36/lib/python3.6/site-packages/pyarrow/error.pxi in 
pyarrow.lib.check_status()
ArrowInvalid: Negative ndarray strides not supported
{code}
 

 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (ARROW-6348) R arrow::read_csv_arrow error on macos

2019-08-24 Thread hugh marera (Jira)
hugh marera created ARROW-6348:
--

 Summary: R arrow::read_csv_arrow error on macos
 Key: ARROW-6348
 URL: https://issues.apache.org/jira/browse/ARROW-6348
 Project: Apache Arrow
  Issue Type: Bug
Reporter: hugh marera


{quote}I am not sure if the arrow::read_csv_arrow() error below is a bug or a 
feature?

 

data("iris")
 write.csv(iris, "iris.csv")
 test <- arrow::read_csv_arrow("iris.csv")
 Error in read_delim_arrow(file = "iris.csv", delim = ",") :
 could not find function "read_delim_arrow"
 test <- arrow::read_delim_arrow("iris.csv")
 sessionInfo()
 R version 3.6.1 (2019-07-05)
 Platform: x86_64-apple-darwin18.6.0 (64-bit)
 Running under: macOS Mojave 10.14.6
{quote}
Matrix products: default
 BLAS: 
/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
 LAPACK: /usr/local/Cellar/openblas/0.3.7/lib/libopenblasp-r0.3.7.dylib

locale:
 [1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8

attached base packages:
 [1] stats graphics grDevices utils datasets
 [6] methods base

loaded via a namespace (and not attached):
 [1] tidyselect_0.2.5 bit_1.1-14 compiler_3.6.1
 [4] magrittr_1.5 assertthat_0.2.1 R6_2.4.0
 [7] tools_3.6.1 fs_1.3.1 glue_1.3.1
 [10] Rcpp_1.0.2 bit64_0.9-7 arrow_0.14.1.1
 [13] rlang_0.4.0 purrr_0.3.2



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


Re: Assigning Issues to New Users

2019-08-24 Thread Wes McKinney
Sounds good to me. I'll start adding committers by and by to the Admin role

On Fri, Aug 23, 2019 at 8:59 PM Jacques Nadeau  wrote:
>
> Let's add committers as admins on jira. I don't see any downsides to that.
>
> On Fri, Aug 23, 2019, 9:42 PM Wes McKinney  wrote:
>
> > hi Paddy,
> >
> > I just added andyscho to the "Contributor" role on JIRA so you can
> > assign them the issue now.
> >
> > You need to be a JIRA administrator on the "Arrow" project to alter
> > roles -- currently only PMC members are admins. I am not opposed to
> > letting all committers be Admin on JIRA, but we have never formally
> > discussed it.
> >
> > - Wes
> >
> > On Fri, Aug 23, 2019 at 9:50 AM paddy horan 
> > wrote:
> > >
> > > Hi All,
> > >
> > > I was going to merge a PR last night when I noticed that it was still
> > unassigned, I believe it is best practice to make sure all issues are
> > assigned on JIRA before merging the corresponding PR?
> > >
> > > However, I cannot assign the issue to the user, I believe that I need to
> > change his permissions but I don't seem to be able to do this.
> > >
> > > In short:
> > >  - is it important to ensure that all issues are assigned on JIRA before
> > merging the corresponding PR?
> > >  - can someone with the correct permissions change the settings of the
> > user below so that issues can be assigned please?
> > >
> > > User:
> > https://issues.apache.org/jira/secure/ViewProfile.jspa?name=andyscho
> > >
> > > Thanks,
> > > Paddy
> >


[jira] [Created] (ARROW-6347) [GLib] Add garrow_array_diff()

2019-08-24 Thread Yosuke Shiro (Jira)
Yosuke Shiro created ARROW-6347:
---

 Summary: [GLib] Add garrow_array_diff()
 Key: ARROW-6347
 URL: https://issues.apache.org/jira/browse/ARROW-6347
 Project: Apache Arrow
  Issue Type: New Feature
  Components: GLib
Reporter: Yosuke Shiro
Assignee: Yosuke Shiro






--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (ARROW-6346) [GLib] Add garrow_array_view()

2019-08-24 Thread Yosuke Shiro (Jira)
Yosuke Shiro created ARROW-6346:
---

 Summary: [GLib] Add garrow_array_view()
 Key: ARROW-6346
 URL: https://issues.apache.org/jira/browse/ARROW-6346
 Project: Apache Arrow
  Issue Type: New Feature
  Components: GLib
Reporter: Yosuke Shiro
Assignee: Yosuke Shiro






--
This message was sent by Atlassian Jira
(v8.3.2#803003)


Re: [DISCUSSION] Automatically adding a the URL of the corresponding JIRA ticket as a comment in GitHub pull-request

2019-08-24 Thread Wes McKinney
Seems like a nice idea to me. We could also prompt contributors to
open a JIRA and prefix to the PR title if they have not already.

The ursabot process is already getting notified about all pull
requests so the implementation there may not be that difficult. Note
that parts of the ursabot codebase are a slight IP quagmire due to
derivative works from Buildbot (which is GPLv2) -- we don't need to
distribute this code with any Arrow releases but keep in mind that
such code can't be brought under ASF governance.

On Fri, Aug 23, 2019 at 10:53 PM Kenta Murata  wrote:
>
> I frequently do the following little bit bothersome steps for opening
> JIRA tickets when I watch a GitHub pull-request:
>
> 1. Select the "ARROW-" text in the title and copy it
> 2. Open JIRA if I haven't open it
> 3. Select a ticket to open it
> 4. Alter the URL by pasting text that copied at the step-1
> 5. Hit the enter key
>
> I think it is better if these steps become easier.
>
> We already have a mechanism to inject a GitHub pull-request URL into
> the corresponding JIRA ticket. How about making the similar mechanism
> for the reverse link?  I guess it is possible to automate making a
> comment of JIRA ticket URL to the pull-request when the "ARROW-"
> text is injected in the title field by using GitHub Actions.
>
> I consulted this idea to Kou, he said ursabot may be appropriate to
> implement such the feature.  And he promote me to ask to Krisztian
> about this.
>
> Krisztian, what do you think this automation?
>
> Regards,
> Kenta Murata


[jira] [Created] (ARROW-6344) [C++][Gandiva] substring does not handle multibyte characters

2019-08-24 Thread Prudhvi Porandla (Jira)
Prudhvi Porandla created ARROW-6344:
---

 Summary: [C++][Gandiva] substring does not handle multibyte 
characters
 Key: ARROW-6344
 URL: https://issues.apache.org/jira/browse/ARROW-6344
 Project: Apache Arrow
  Issue Type: Bug
Reporter: Prudhvi Porandla
Assignee: Prudhvi Porandla






--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (ARROW-6343) [Java] [Vector] Fix allocation helper

2019-08-24 Thread Praveen Kumar Desabandu (Jira)
Praveen Kumar Desabandu created ARROW-6343:
--

 Summary: [Java] [Vector] Fix allocation helper
 Key: ARROW-6343
 URL: https://issues.apache.org/jira/browse/ARROW-6343
 Project: Apache Arrow
  Issue Type: Bug
Reporter: Praveen Kumar Desabandu
Assignee: Praveen Kumar Desabandu


Allocation helper, not passing around value count for varchar vectors.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)