I am also +1 for this change.
- It's a simple change that doesn't require a lot of effort and
disruption to the code base.
- If we follow the links from the article Michael posted, the term
"master" in git does not originate from "master record" but rather from
master/slave.
- We make our
Hi all,
I'm a Calcite user and longtime mailing list lurker :) I'd like to
share our experience from Apache NiFi, we started such a discussion
for NiFi based on existing discussions from Apache Yetus and Apache
Accumulo [1]. Our own discussion continued (please see the linked
email thread) but I
As a Chinsese, I didn’t understand quite well why the word “master” can be
“slavery”. I often see it as the similiar meaning as “main”, it seems to take
some time to adapt to new term “main” because I believe most of the developers
got used to the word “master”.
> I think this is a relatively
The Apache Jenkins build system has built Calcite-Master (build #1860)
Status: Failure
Check console output at https://builds.apache.org/job/Calcite-Master/1860/ to
view the results.
Actually, the argument that the term "master" in git didn't originate
from master/slave is not true. See the article I linked earlier. In
any case, I don't think the change hurts anyone other than a brief
annoyance when we all have to change our branch name and if it makes
the project more
> It’s probably derived from “master” as in the “gold master” [1] which is
> the mix from which a sound engineer would cut a record or CD. And who knows
> where that term came from?
>
Of course! Dictionaries are clear, see
https://www.merriam-webster.com/dictionary/master or
Rui Wang created CALCITE-4146:
-
Summary: Implement EMIT AFTER WATERMARK
Key: CALCITE-4146
URL: https://issues.apache.org/jira/browse/CALCITE-4146
Project: Calcite
Issue Type: Sub-task
I agree with you. It’s probably derived from “master” as in the “gold master”
[1] which is the mix from which a sound engineer would cut a record or CD. And
who knows where that term came from?
But in the end, the origin of the term is irrelevant. The current name is, or
may be, unwelcoming to
It's not a term related to slavery, it has much broader meaning than "slave
owner", but any argument is probably vain.
On Tue, 28 Jul 2020 at 19:43, Julian Hyde wrote:
> I am in favor of renaming ‘master’ to ‘main’. To most people it doesn’t
> make any difference. To some, such as potential
I can’t quite tell whether Andreas wants to connect to Calcite via JDBC, or
have Calcite’s adapter connect to a JDBC source.
For the former, there is not much variation in connect string parameters
available. Any of the parameters can be put into the “info” map or included as
part of the URL.
I am in favor of renaming ‘master’ to ‘main’. To most people it doesn’t make
any difference. To some, such as potential members currently outside the
community, it makes the project more welcoming.
Very little effort or disruption is required. We’ve identified a potential
source of friction,
Hi all,
You can find some background on this discussion at the link below [0].
This is a topic that has come up regularly among D folks at the ASF.
The short summary is that the term "master" when referring to a git
branch is a reference to terminology related to slavery. I'm
suggesting main
1) The options specified in the connection string are unique to the
specific adapter being used.
2) Unfortunately, I don't believe such a summary exists. (Although
there is documentation on what can be in the model JSON file.)
3) Configuring with the connecting string is fine where possible, but
Danny Chen created CALCITE-4145:
---
Summary: Exception when query from UDF field with structured type
Key: CALCITE-4145
URL: https://issues.apache.org/jira/browse/CALCITE-4145
Project: Calcite
Hi,
I'm new in the Calcite Community (hope this is the right place to ask this
kind of question).
It found the following options to configure Calcite JDBC clients so far:
This tutorial uses a JSON file:
jdbc:calcite:model=src/test/resources/model.json
15 matches
Mail list logo
