Re: Next Druid release version scheme

know they're painful for > users. I'm not suggesting we immediately get any more, or less, eager about > making breaking changes as part of dropping the "0.". Over time, though, > I'd like to see us get less eager about making breaking changes. > > On Wed, Jul 6, 2022 at 9

Re: Next Druid release version scheme

Would 24.0 and 25.0 each be regarded as major versions for the purposes of semantic versioning? If so, under the rules of semantic versioning, we *can* make breaking API changes but that doesn’t mean that we *should*. (For an example of a project that followed the letter of semantic versioning

Re: Druid-specific Calcite keywords

ot;ORDER BY APPROXIMATE " or "ORDER BY > APPROXIMATE". > > I had also wanted to look at adding a PARTITION BY keyword that controls > partitioning of query result sets. > > On Thu, Nov 4, 2021 at 11:48 PM Julian Hyde wrote: > >> Some specifics would be

Re: Druid-specific Calcite keywords

Some specifics would be useful. But in general, adding a new keyword (reserved or non-reserved) will require changes to the paser. Calcite allows (I won't say it makes it easy) for projects like Druid to create a derived parser by building a parser from the same parser template as Calcite's core

Re: 欢迎申报｜2021“科创中国”开源创新榜评选活动

Moderator’s note: as moderator, I allowed this message to dev@ even though it is in Chinese and seems to be a mass mailing, because it appears to be on topic (namely open source). The automatic translation of the first paragraph is as follows: Dear open source innovation ranking application

Re: Enabling dependabot in our github repository

I agree that PRs should not be committed immediately and unconditionally when the dependabot finds them. But if we defer, there is a concern that good PRs will be forgotten. How about making a particular person (say the release manager) or triggering event (say voting on an RC) responsible for

Re: Push-down of operations for SystemSchema tables

Jason, > I'm new to Calcite (and Druid) so if I have some terminology > incorrect, please point it out. From a Calcite perspective, I can tell you that your terminology (and ideas) seem spot on. I can’t say whether they make sense in Druid (or are easy to achieve). Julian > On May 13, 2021,

Re: Regarding sharing the official Druid Twitter account

r the tweets > follow the ASF branding policy. Committers will have to review those > tweets based on the guidelines we will make. Given that we usually > review ~10 PRs every day, reviewing a few extra tweets will not be a > big burden to the community. This will also become better as we

Re: Regarding sharing the official Druid Twitter account

Any PMC member who is willing could be the owner of the Twitter account. The PMC chair has a few extra responsibilities but no more rights/privileges than other PMC members. Are you suggesting that tweets from PMC members would have to go through the review process? That would, if anything,

Re: About maintaining the Helm's Chart of Apache Druid

This code was developed outside of the ASF, so it’s possible that we need to go through the IP clearance process [1]. Can a PMC member please figure out the answer to that question, and answer on this list. Has the Helm project given any indication whether they approve or disapprove of the

Re: Removing Druid support for JDK 8 and adding support for JDK 11

I have no objections to dropping support for JDK 8, but why only support JDK 11? What would it take to support JDK 11 and all newer JDKs? There's an analogy with starting and stopping a train. Once you have stopped a train (settled on a particular JDK release for a number of years) starting it is

Re: Druid not listed in Apache project list by category?

Have we registered a DOAP (description of a project) file [1] for Druid? That might be the problem. For comparison, Calcite has a DOAP [2] and its project page is much richer [3]. Julian [1] https://projects.apache.org/doap.html [2]

Re: Druid Namespacing Proposal

Reading the blog post, I was sorry to hear that "performance bottlenecks in the SQL parser” prevented you from making SQL your main interface to Druid. Can you tell us more about the issues? Is there a bug logged against Calcite or Druid? In the blog post, thanks for qualifying the Druid,

Re: Podling Druid Report Reminder - December 2019

Druid plans to graduate, so I hope there aren’t 3 items! My comment on the proposed report is that it doesn’t mention the graduation resolution. It should also say that why the resolution was previously shelved - IP issues that have now been resolved. Julian > On Dec 4, 2019, at 11:25 AM,

Re: Dec 2019 podling report draft

Does Druid intend to put a resolution to graduate on the agenda of the Dec 2019 board meeting? If so that should definitely be in the report. Julian > On Dec 3, 2019, at 11:49 PM, Jonathan Wei wrote: > > Updated the section about trademarks on the wiki to the following: > > The PPMC has

Re: [VOTE] Release Apache Druid (incubating) 0.16.0 [RC3]

ice with email? > > On Sun, Sep 15, 2019 at 8:34 PM Julian Hyde wrote: > >> Sorry for my rather terse -1 vote. I had assumed that we had been >> following the policy for a while, so when I noticed that we were not I >> assumed it was a mistake by the release manag

Re: [VOTE] Release Apache Druid (incubating) 0.16.0 [RC3]

4768da1ea08eba6efe635ced5abc3ad72d6c835e2c > > Thanks! > Clint > > On Sun, Sep 15, 2019 at 6:22 PM Julian Hyde wrote: > > > -1 > > > > The vote email must contain the checksums of the artifacts we are voting > > on. > > > > No need for a new RC;

Re: [VOTE] Release Apache Druid (incubating) 0.16.0 [RC3]

-1 The vote email must contain the checksums of the artifacts we are voting on. No need for a new RC; I change my vote if the release manager sends an email with the checksums. Julian On Fri, Sep 13, 2019 at 11:57 PM Clint Wylie wrote: > > Hi all, > > I have created a build for Apache Druid

Re: September 2019 Podling Report (Draft)

his process a > bit more. The process is described here > <https://community.apache.org/newcommitter.html#new-committer-process>. > Apart from that, I feel as well that Druid is nearing graduation. > > Cheers, Fokko Driesprong > > Op wo 4 sep. 2019 om 21:58 schreef Julian Hyde :

Re: September 2019 Podling Report (Draft)

It’s probably better to wait until they have accepted. It would be embarrassing if they declined. As every CFO knows, it’s good to defer the reporting of revenue… you have something positive in the bag to add to the next report. Julian > On Sep 3, 2019, at 8:40 PM, David Lim wrote: > >

Re: September 2019 Podling Report (Draft)

Looks good. Thanks for the shout-out. :) > On Sep 3, 2019, at 4:13 PM, Jonathan Wei wrote: > > Hi all, > > I've prepared the following podling report draft, and I am planning to > submit it before the deadline tomorrow. > > Please take a look and let me know if you have any feedback. > >

Re: Graduation

> On Jun 26, 2019, at 10:23 PM, Gian Merlino wrote: > Speaking for myself I would be happy to have any of you (Julian, > Jun, Taylor) if you're interested. It sounds like you might be, Julian, > which if so is great. Yes, I would be happy to serve on the PMC, if that is what the community wants.

Re: Stalebot for issues

I claim that features have a different lifecycle to bugs. There may not be a strong case for doing a particular feature today, but in a year, there may be a greater demand. If a bugs are not fixed, their importance usually declines over time. Are people able to vote for features in GitHub

Re: Graduation

Bouguerra * Xavier Léauté And here is the list of current committers: * Benedict Jin * Lijin Bin * Slim Bouguerra * Eric Tschetter * Charles Allen * Clint Wylie * David Lim * Dylan Wylie * Egor Ryashin * Fangjin Yang * Dayue Gao * Gian Merlino * Himanshu Gupta * Julian Hyde * Jihoon Son * Jonathan

Re: [VOTE] Release Apache Druid (incubating) 0.15.0 [RC2]

+1 (binding) Checked hashes and signatures, LICENSE, NOTICE, DISCLAIMER, README, ran RAT, compiled on Linux/JDK 8. Compared to git, there is one generated file in the src distribution, sql-function-doc.ts. Not sure whether this is intended to be in the src distribution. Julian > On Jun

Re: [ANNOUNCE] Apache Druid (incubating) 0.14.1 release

No reason to wait til next release; you can send to annou...@apache.org this release. On Sun, May 12, 2019 at 11:13 PM Clint Wylie wrote: > > Thanks Julian, I'll be sure to get these things fixed up before the next > release! > > On Sat, May 11, 2019 at 1:30 PM Julian Hyde wrot

Re: [ANNOUNCE] Apache Druid (incubating) 0.14.1 release

Thanks for being release manager and making the announcement, Clint. Most projects announce by sending to annou...@apache.org. This reaches a wider audience (I know several journalists and analysts who follow it). So it is useful to have an explanatory paragraph "Apache Druid (incubating) is

Re: deprecating the old repo

One trick that people sometimes use is to create a new branch called “obsolete” or similar, update the README in that branch to point to the new project location, and make that branch the default branch in GitHub. > On Apr 26, 2019, at 11:02 AM, Gian Merlino wrote: > > That makes sense to me.

Re: Code review

+1 As someone who reviews Druid release candidates but does not develop Druid code, I wish that “mvn test” would “just work”. I can imagine that first-time and occasional contributors are in a similar boat to me. I know this is not an easy thing to achieve, because the test suite also has to

Re: Running UNION ALL queries in parallel

Yes it does. Only ORDER BY causes order. Julian > On Apr 20, 2019, at 12:17, Gian Merlino wrote: > > Hey Julian, > > I think it'd be fine to issue the queries in parallel with a few > adjustments. We'd want to avoid buffering, meaning we'd want to allow query > results to be mixed together

Re: [ANNOUNCE] Apache Druid (incubating) 0.14.0 released

Congratulations on the release, everyone! The release notes [1] have some branding issues. The project’s name is “Apache Druid (incubating)”, but the notes call it “Druid” throughout; in fact they don’t mention “Apache” at all. It isn’t helped by the fact that the links point to druid.io

Re: [VOTE] Release Apache Druid (incubating) 0.14.0 [RC3]

+1 (binding) Checked hashes, LICENSE, NOTICE, copyright date, DISCLAIMER, built (skipping tests) on JDK 8 Ubuntu. Ran RAT. Checked that contents of src.tar.gz correspond to commit f169ada. Did not verify bin package other than checking hashes. Thanks for the nice clear build instructions in

Re: Policy for accepting new modules and large contributions. Protocol for removing modules

One line of this policy is problematic: > Be "endorsed" by at least two committers who are recently active in > Druid. (Read: supporting Druid is part of their job duty, at least > part-time.) It creates two tiers of committers. Sustainability is a concern for all code contributions. The

Re: [VOTE] Release Apache Druid (incubating) 0.14.0 [RC1]

-1 due to wrong copyright year in NOTICE file. Checked hashes, LICENSE, NOTICE, DISCLAIMER; compiled on Ubuntu JDK 8 (skipping tests); checked that file contents match git commit; ran apache-rat. Copyright year in NOTICE is 2018. I recommend that you obsolete

Re: [VOTE] Release Apache Druid (incubating) 0.14.0 [RC1]

My bad. I was looking apache-druid-0.13.0-incubating-rc1 when I should have been looking at 0.14.0-incubating-rc1. > On Mar 16, 2019, at 9:47 AM, Julian Hyde wrote: > > Jonathan, > > I’m reviewing now. The release seems to be signed by David Lim. Did David > make this r

Re: [VOTE] Release Apache Druid (incubating) 0.14.0 [RC1]

Jonathan, I’m reviewing now. The release seems to be signed by David Lim. Did David make this release? $ gpg --verify apache-druid-0.13.0-incubating-src.tar.gz{.asc,} gpg: Signature made Sat 20 Oct 2018 08:50:20 PM PDT gpg:using RSA key 58B5D669D2FFD83B37D88DF8BB64B3727183DE56

Re: [VOTE] Release Apache Druid (incubating) 0.14.0 [RC1]

Hey Don, Your comments are most welcome, but I’d like to make a point of order. In Apache, vote threads are strictly business - voting +1 or -1 in the release, with reasons why. If you have something to discuss about the content of the release (or otherwise), it’s best to start a new thread.

Incubator report

Hi Druid PPMC, The March incubator report is due tomorrow. Is someone working on it? Julian https://wiki.apache.org/incubator/March2019

Re: Datasketches

I don’t know how a project can formally track another project, but individuals certainly can. If any Druid committers are ASF members then they could volunteer to help as mentors of the Data Sketches podling. If any Druid committers are past or current contributors to the DataSketches they

Re: TeamCity having problems

he/incubator-druid/pull/7118, > under "Inspections: pull requests (Druid)". > > On Fri, Feb 22, 2019 at 10:17 AM Julian Hyde wrote: > >> What is TeamCity? How does Druid use it? Is it accessible to all Druid >> contributors? Are all Druid contributors requir

Re: Knowledge sharing between Druid developers via technical talks

I like that idea. I always wish that meetups were more about the community of contributors (people writing code, answering questions, writing documentation, and pushing the product to new places). But sadly meetups are usually organized by marketing departments. Some conferences (e.g. Hadoop

Re: TeamCity having problems

What is TeamCity? How does Druid use it? Is it accessible to all Druid contributors? Are all Druid contributors required to use it? Is its use documented somewhere? (I searched https://www.google.com/search?q=apache+druid+teamcity but

Re: LICENSE question

That sounds right. What is the license of these files? Julian > On Feb 8, 2019, at 11:17 AM, Jonathan Wei wrote: > > Hi mentors, > > I am updating Druid's LICENSE and NOTICE file for our next release, and had > a question on handling some our dependencies. > > We have a web console ( >

Re: Forbiddenapis Plugin

I’ve seen a similar problem in Calcite, which also uses forbiddenApis. It only seems to occurs in a “bad build”; when you do “mvn clean” the problems disappear. My hypothesis is that the code is generated by javac, for example for the messages from “assert”, or when concatenating string

Re: Off list major development

at you want to >>>>>> address before hand anyway isn't ? >>>>>> >>>>> >>>>> Sorry for the confusion, I said it's "not overbearing", I think it's >>> fine. >>>>> >>>>> What are the

Re: Off list major development

the discretion of Druid committers > > Some of it is subjective, but it has been in place for a while, so it's at > least something we are relatively familiar with. > > On Mon, Jan 7, 2019 at 11:32 AM Julian Hyde wrote: > >> Small contributions don’t need any design review,

Re: Off list major development

mpatibility/ plans to upgrades) public API >>>> changes, >>>>> configuration changes, algorithm, and so on >>>>> - Expected benefits and drawbacks >>>>> - Rationale and alternatives >>>>> - Estimate Time to Deli

Re: Off list major development

writing POCs to help guide the review process this naturally will be a >>> Pull >>>> request with actual code. >>>> >>>> *Now the most important thing is that we need to agree that any work >> that >>>> does not align with this formal

Re: Off list major development

Slim, I agree with your points that offline development is bad for community. But I don’t think you need much mentor help. You have raised valid issues and the Druid community needs to decide what its development practices should be. Julian > On Jan 2, 2019, at 10:29 AM, Slim Bouguerra

Re: Mentoring Apache Druid

Ping! Do we want an additional mentor or not? > On Dec 17, 2018, at 1:01 PM, Julian Hyde wrote: > > I had to look up the process for adding a mentor to an existing podling. From > the PPMC guide [1]: > >> Adding new mentors >> >> At times, it may be desirable

Re: Drop 0. from the version

s on it. Almost > nothing depends on Druid. > > On Fri, 21 Dec 2018 at 19:46, Julian Hyde wrote: > >> No one has mentioned Semantic Versioning (semver [1]) yet, so I will. >> I don't know whether the Druid developers think in terms of semver, >> but a lot of your audi

Re: Drop 0. from the version

No one has mentioned Semantic Versioning (semver [1]) yet, so I will. I don't know whether the Druid developers think in terms of semver, but a lot of your audience will. In semver, the shift from 0. to 1. is a big event, because the "only remove APIs in major releases" rule does not apply for

Re: Mentoring Apache Druid

mc.html#adding_new_mentors > On Dec 12, 2018, at 11:58 AM, Furkan KAMACI wrote: > > Hi Julian, > > Thanks! I believe that Druid is promising and it would be great to assist > it through its path graduating from Incubation. > > Kind Regards, > Furkan KAMACI > > On

Re: Mentoring Apache Druid

Furkan, Thanks for reaching out. We would be delighted to have some extra help! I am one of the mentors, and Taylor Goetz and Jun Rao are also active on this list. Julian > On Dec 7, 2018, at 11:51 PM, Furkan KAMACI wrote: > > Hi All, > > I'm Furkan KAMACI who is a person loves open

Re: PR Milestone policy

refore we need to optimize for the fraction >> of PRs that are merged in 1 month or less (the average time between >> creation of a new release branch and a final release date). Reviewers >> should schedule their time so that there are less PRs that are merged in >> less than one d

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC4]

+1 (binding) Downloaded, built and ran tests on Java 8/Ubuntu. Checked LICENSE, NOTICE, DISCLAIMER. Ran RAT. Checked that git matches contents of src tarball. The issues I noticed last time with GPL licenses, files missing headers have been fixed. Julian > On Dec 5, 2018, at 1:47 PM, Jihoon

Re: PR Milestone policy

To me, this means assigning milestones to contributions, not being overly > picky on code (if it has no real impact on functionality/performance). If > we need to push PRs back to a later release because they are complicated > and require more review, we can always do that. > > On Tue, No

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC3]

David, It is customary to close every vote with a either a “cancel” or “result” email. In this case, can you send an email with the subject line [CANCEL] [VOTE] Release Apache Druid (incubating) 0.13.0 [RC3] Julian > On Dec 2, 2018, at 1:53 AM, David Lim wrote: > > Hello, > > Voting on

Re: PR Milestone policy

Fangjin, You wrote > we should try to assign milestones to PRs we want > to get in Can you please define “we”? Do you mean committers, PMC members, release managers, everyone? Julian > On Nov 26, 2018, at 8:43 AM, Roman Leventov wrote: > > About a year ago, Gian wrote ( >

Re: Weekly dev sync minutes (2018-11-27)

Thanks for writing up the minutes. I know it’s a considerable effort to write minutes, but it allows me to keep up with what’s going on in the project. Also, an email to the dev list is an excellent opportunity to spawn follow-up discussions. And discussion on the dev list or in GitHub issues

Re: Sync up this week

Apache doesn’t have a policy on video per se, but we do have a policy that conversations should be open to all. Due to time-zones etc. some people may not be able to attend the dev syncs, and those people must not feel excluded. If consent is preventing you from recording the dev syncs, perhaps

Re: Druid PR review checklist

Thanks for starting this thread, Roman. It’s a great discussion to be having. A word of caution about google docs. Since this one can be edited by anyone who has the link, and the link is posted in a public archive, then at some point this doc will fall victim to spam or vandalism. I suggest

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

> On Oct 30, 2018, at 12:04 PM, Gian Merlino wrote: > > It says > to use http://static.druid.io/, but we probably won't put the artifacts > there. Indeed. It is mandatory that the artifacts and their checksums are hosted on apache.org . (There can be mirrors.) Julian

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

the committers who helped set up the >> exclusions can comment. I suspect that many of them are either a) files >> which cannot properly support the licensing header and remain syntactically >> valid, or b) deemed to be insignificant in its creative content and >> there

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

ery.dataTables-1.8.2.js server/src/main/resources/static/old-console/js/underscore-1.2.2.js > On Oct 22, 2018, at 10:58 AM, Julian Hyde wrote: > > Thanks for finding that list, David. There are a lot of things to check. > Therefore, before voting +1 you need to do some due diligenc

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

/github.com/apache/incubator-druid/labels/Apache >> For bugs/features the release note is what you want to check >> https://github.com/apache/incubator-druid/issues/6442/ >> >> >> On Sun, Oct 21, 2018 at 6:38 PM Fangjin Yang wrote: >> >>> +1 >>>

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

Hey Slim, Since this is an Apache release, and you've voted on Apache releases before in Calcite and Hive, can you explain what you checked before you voted "+1". There are many folks here who have not been through the release process, and we veterans should show them the ropes. Julian On Sun,

Re: [VOTE] Tranquility 0.8.3 release

Can someone please clarify what is going on here. Am I correct that Tranquility is not an Apache project? Who is allowed to vote for this release - Druid PPMC members? What is being voted upon? A particular set of artifacts to be released, the latest commit in github, or something else? (If

Re: First Apache release of Druid

it's doable on a relatively short > timeframe from now. > > On Mon, Sep 17, 2018 at 2:07 PM Julian Hyde <mailto:jh...@apache.org>> wrote: > >> An ASF release is fundamentally a legal transaction. Issuing a bunch of >> source code under a license, having made sure t

Re: First Apache release of Druid

SF requirements for a release. Doing so would imply a major > release for us since those changes wouldn't be backwards compatible. Are > you saying that we would be able to do a release without renaming artifacts? > > On Mon, Sep 17, 2018 at 12:42 PM Julian Hyde <mailto:jh...@apache.o

Re: First Apache release of Druid

to > generate and vote on RCs, that would be helpful towards getting it done > faster. > > > On Mon, Sep 17, 2018 at 10:45 AM Julian Hyde wrote: > >> Druid has been in incubation for several months and has not yet produced >> an Apache release. There were in

First Apache release of Druid

Druid has been in incubation for several months and has not yet produced an Apache release. There were initially some issues with IP transfer that prevented that release, but they are now solved. The release is becoming urgent, because the code is still not been released under the Apache

Re: Druid as a OLTP solution

Shushant, Gian is definitely correct that Druid is not designed for OLTP. However the scenario you describe does not sound like OLTP. You talk of querying data, but you don’t mention inserting/updating individual records with low latency, which is a hallmark of OLTP, and something that Druid

Re: Please add me to mailing list

It's incorrect to say that you subscribe to a mailing list by sending a message to it. To subscribe to dev@druid, send a message to dev-subscribe@druid. Similarly unsubscribe. Similarly users@ and commits@. Details here: * https://mail-archives.apache.org/mod_mbox/druid-dev/ *

Re: Changing release process for release candidates

If it’s not clear, “release manager” is an important role. The RM is responsible for the key events in the release - building a release candidate (including signatures), putting it in a place that it can be viewed, writing release notes, starting a vote, closing the vote, writing the release

Re: About creating 0.12.2-rc1

Gian is correct. Creating an RC doesn’t require a vote. It does require a release manager. Usually in Calcite we determine the timeframe of the release, and choose an RM, by a discussion that reaches consensus without an explicit vote. The RM may do a little “traffic control”, asking whether

Re: Podling Report (August 2018)

on August 8 >> (after the report is due I assume), should we mention that in this report? >> >> I noticed the incubator wiki page for August 2018 hasn't been created yet, >> does anyone know if that's expected to be up soon? (Not sure on what exact >> date our podling repo

Re: GitBox review comments

I have poked Infra again on our ticket: > https://issues.apache.org/jira/browse/INFRA-16674 > > On Tue, Jul 24, 2018 at 5:55 PM Julian Hyde wrote: > >> I know there is an open request with INFRA to route git review comments to >> a list other than dev. But until then, we a

GitBox review comments

I know there is an open request with INFRA to route git review comments to a list other than dev. But until then, we are still getting a lot of messages on the list each day. A lot of them come in groups, as a reviewer makes multiple comments on a particular PR. I believe git has a feature

Re: License headers and NOTICE file

Do your best with the NOTICE file. We will scrutinize it during the release process. I know it seems impolite not to mention contributors and copied code in the NOTICE, but there is a good reason to keep its contents absolutely minimal. Downstream projects are required to reproduce the NOTICE

Re: Gitbox notifications

As it happens, all 3 of Druid's mentors (including myself) are ASF members. Their names are bold in https://people.apache.org/phonebook.html?podling=druid. I am busy, I will try to get to it today. On Wed, Jul 11, 2018 at 10:20 AM, Roman Leventov wrote: > It writes "Access restricted to ASF

Re: Druid repo migration plan

> On Jul 6, 2018, at 1:08 PM, Julian Hyde wrote: > > I like the idea of a separate list for commits. Keeps the noise down on the > dev list. > > Other projects (e.g. calcite) would name that list “commits”, i.e. > comm...@druid.apache.org <mailto:comm...@druid.

Re: Druid repo migration plan

>> master >>>>>> if controlling master is important in your workflow. This way you can >>>>>> effectively merge PRs without clicking the button on GH. >>>>>> * make sure core committers have their Gitbox access setup, I think it >&

Re: Podling Report Reminder - June 2018

Yes, the mentors are active and I’m one of them. As a mentor I am happy to give advice, and do so frequently. But I’m not going to nag the PPMC to file reports. They need to do that for themselves. Julian > On Jun 19, 2018, at 18:00, Justin Mclean wrote: > > Hi, > > I noticed the podling

Re: Podling Report Reminder - May 2018

al setup >> [ ] Working towards first release >> [ ] Community building >> [ ] Nearing graduation >> [ ] Other: >> >> Date of last release: >> >> - Druid 0.12.0 on 2018-03-06 (non-Apache release) >> - No official Apache release yet since beg

Re: Druid 0.12.1-rc1 vote

You should make it clear that this is a non-ASF release. Such releases are allowed during incubation but not encouraged. Also be sure to mention it in your next report. Julian > On Apr 24, 2018, at 2:49 PM, Jihoon Son wrote: > > Hi all, > > We currently have no open

Re: Dev list migration

You should also update https://github.com/druid-io/druid/blob/master/README.md . > On Apr 24, 2018, at 8:08 AM, Gian Merlino wrote: > > Today (well, yesterday) is the day we had decided on for migrating the dev >

Re: Legal implications of using JMH

We use JMH in Calcite for microbenchmarking. My understanding was that our use is OK. We are not linking it into the product; during tests, we link against JMH, run the test, then delete the executable. In addition to Calcite, it is used in Hive [1] Log4j2 [2], and Camel [3]. I think we should

Re: Legal implications of using JMH

I agree with Gian. Calcite uses JMH. We don’t distribute the binaries it produces — because we only need them for running benchmarks. It’s not an identical situation to MySQL because while there are other implementations of JDBC — e.g. Postgres — there is only one implementation of JMH. But

Re: Dependencies licenses Report

The main tool to use is Apache RAT. Definitely use that. One of the hardest tasks is getting the contents of LICENSE and NOTICE right. That is a manual task I’m afraid. Julian > On Apr 18, 2018, at 08:34, Gian Merlino wrote: > > Hi Slim, > > Do you know if ORC &

Re: Web site

; every version we've ever released. > > Maybe it makes sense to have three repos: one for the sources and > docs/tutorials (which are tied to the sources), one for the "floating" > parts of the site that are untethered to any particular release, and one > for the

Web site

There has been some back-channel discussion about the web site. Druid has a good and successful web site outside of Apache, namely druid.io . We cannot start transitioning that site until the legal IP transfer has completed. In the mean time, we were left without a web site:

Re: [druid-dev] Apache migration logistics

on...@gmail.com> wrote: >>>> >>>>> We can register dev@druid.apache.org and us...@druid.apache.org as a >>>>> user in druid user groups so that going forward any mails that are >> sent to >>>>> druid google groups are also

Re: Roll call?

ho may have not moved over yet. > > > > Cheers, > > Charles Allen > > > > > > > From: Julian Hyde <jh...@apache.org> > Sent: Saturday, March 24, 2018 5:29:44 PM > To: dev@druid.apache.org > Subject: Roll cal

Roll call?

Do we believe that all PPMC members (initial committers and mentors) have now joined the dev and private lists? (As a moderator of the mailing lists, I ought to know how to check who is on the list, but I don't. Maybe we should have a roll call.) If everyone is on the lists, I think we should

Re: [druid-dev] Apache migration logistics

I don’t know. I don’t think it’s easy. > On Mar 9, 2018, at 7:31 AM, Roman Leventov <roman.leven...@metamarkets.com> > wrote: > > Could archives of druid-dev and druid-users mailing lists be transferred to > the new lists? > > On Thu, Mar 8, 2018 at 8:48 AM, Ju

Re: [druid-dev] Apache migration logistics

git history and > grant them admin rights to the github repo. > > Charles, it also sound like we won't be able to do any code migration util > legal signs off on the software grant, could you drive that? > > On Mon, Mar 5, 2018 at 12:52 PM Julian Hyde <jhyde.apa...@gmail.com &

Fwd: Podling Report Reminder - March 2018

Usually podlings get an automated reminder, like the one below, for the IPMC report. There was no reminder for Druid this month, because I didn’t get the dev list set up in time. Nishant filed a report in time anyway (well done!) but I thought you’d be interested in the blurb anyhow. Julian