Great honor for me. Thanks all!
Yibo
On 3/6/21 9:20 AM, Neal Richardson wrote:
Congrats Yibo!
Neal
On Fri, Mar 5, 2021 at 4:46 PM Nishit Kumar wrote:
Congratulations Yibo! Wishing you all the best, and looking forward to
your contributions in making Arrow a robust tool.
Cheers!
Nishit
Se
Are non-committers able to add/remove tags to PRs? Sounds like a good way
to increase visibility/searchability of PRs needing review, but it would
only work if everyone is authorized to modify tags.
Neal
On Sun, Mar 7, 2021 at 12:24 PM Wes McKinney wrote:
> This sounds like a nice idea as long
Hi,
Could you show outputs of the following command lines?
$ otool -L /usr/local/lib/libparquet-glib.400.dylib
$ otool -L /usr/local/lib/libparquet.400.dylib
I think that libparquet.400.dylib includes @rpath.
We can't use @rpath with GObject Introspection that is used
to generate Ruby bindings
I think we're definitely overdue in having Parquet integration tests,
not just in Arrow but data ecosystem wide. It's a bit unfortunate that
the extent of integration testing ends up being "let's see if it
works" and "if it breaks we'll fix it". Some implementations may write
files which can't be c
I took a look at the document. Basically you want to have two
different versions of the Arrow shared library loaded into the same
process, with some code linked to one library and some code linked to
another. This is very similar to the problem that Boost addresses with
the `bcp --namespace=$MY_PRI
This sounds like a nice idea as long as the bot doesn't generate too
much potentially spurious info (i.e. the "needs improvement" label
when it perhaps need not).
Note that the Spark community set up a pretty handy PR dashboard
https://spark-prs.appspot.com
It's open source: https://github.com/d
Let us bring up the matter with INFRA to see what can be done. Since
this is the sort of thing that happens a few times a week at most,
given the number of committers we have I don't think it's that much of
a nuisance all things considered. At this point we have spent more
time writing e-mails abou
The list of things you can do as a contributor is here:
https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
In any case, I'm not sure the request is to automatically give regular
users the contributor role, rather to let non-contributor people be
assigned issues (a
There have been some concrete issues with Jira spam / vandalism in the
past, and having individuals in the Contributor role increases the
amount of damage that they can do. For example, I believe if you have
the Contributor role you can delete issues and other sorts of
malfeasance. If they aren't i
We have the exact same problem in Apache Calcite. People get the impression
that “contributor” is some kind of achievement within the Apache hierarchy -
it’s not, it’s just a JIRA concept - and it creates friction for people who
want to contribute. (After all, I think we want people to log a JIR
Edit: this is documented here:
https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
Regards
Antoine.
Le 07/03/2021 à 11:11, Antoine Pitrou a écrit :
Hi Diana,
It looks like this is governed by the JIRA "permission scheme" for the
project. Which apparently we c
Arrow Build Report for Job nightly-2021-03-07-0
All tasks:
https://github.com/ursacomputing/crossbow/branches/all?query=nightly-2021-03-07-0
Failed Tasks:
- conda-linux-gcc-py39-aarch64:
URL:
https://github.com/ursacomputing/crossbow/branches/all?query=nightly-2021-03-07-0-drone-conda-linux
Hi Diana,
It looks like this is governed by the JIRA "permission scheme" for the
project. Which apparently we could request the JIRA administrators
(i.e. the Apache INFRA team).
However, before making such a change, we should already know what the
possible permission schemes are.
Regard
13 matches
Mail list logo
