report" button).
>
> I think that the majority of "Feature/Change request", "Feature",
> "Refactoring", "Performance", etc. issues would be "evergreen", so it's
> more practically to close them only by occasion when someone visit
documents? Assuming they look in order
then I will start a formal VOTE.
On Fri, Jun 21, 2019 at 11:59 AM Gian Merlino wrote:
> I've updated the status page:
> http://incubator.apache.org/projects/druid.html. I think it's pretty
> accurate now. I will start going through the other stuff on the g
11:05 AM Jihoon Son wrote:
>
> > +1
> >
> > On Thu, Jun 13, 2019 at 10:10 AM Nishant Bangarwa
> > wrote:
> >
> > > +1
> > >
> > > On Thu, Jun 13, 2019 at 10:33 PM Charles Allen
> > wrote:
> > >
> &g
In the last few days, website migration to https://druid.apache.org/ and
content update to comply with https://whimsy.apache.org/pods/project/druid have
been completed! I think this means we are ready to crack on. Would love to
hear what others think.
On Sat, Jun 8, 2019 at 12:27 AM Gian Merlino
Sorry, I mean references to https://github.com/druid-io/druid-io.github.io
should be changed to https://github.com/apache/incubator-druid-website-src.
That is the change that actually happened, and the one that makes sense.
On Wed, Jun 12, 2019 at 4:25 PM Gian Merlino wrote:
> Yep,
Please do, Sandish. Seems like a higher timeout would make the test more
robust.
On Thu, Jun 13, 2019 at 6:57 PM Sandish Kumar HN
wrote:
> Hi Jihoon,
>
> Thanks for all the help found below bugs.
>
> In SegmentManagerThreadSafetyTest file timeout rule is set to @Test(timeout
> = 5000L), but
There's been some discussion on GitHub about enabling stalebot (which we
use for PRs) for issues as well. Please check this PR out if you are
interested: https://github.com/apache/incubator-druid/pull/7936. It's a
follow up to https://github.com/apache/incubator-druid/pull/7927, which is
also
think 60 days is a bit short, hence the suggestion in my follow up PR to
raise it to 280 days (about 3 release cycles).
On Thu, Jun 20, 2019 at 12:40 PM Gian Merlino wrote:
> There's been some discussion on GitHub about enabling stalebot (which we
> use for PRs) for issues as well. Please
better?
>
> On Thu, 20 Jun 2019 at 23:54, Gian Merlino wrote:
>
> > By the way, I do think it makes sense to have a stalebot for issues.
> Right
> > now we have over 1000 open issues and I doubt anyone is actively
> reviewing
> > them. IMO it would be better to keep the
t have assignees, or that have
milestones, so those are options too if they make sense.
On Fri, Jun 21, 2019 at 9:07 AM Roman Leventov
wrote:
> On Fri, 21 Jun 2019 at 18:38, Gian Merlino wrote:
>
> > The effect should be giving us an
> > open issues list that more accurately respects t
, but, maybe nice to have anyway.
On Wed, Jun 19, 2019 at 9:34 PM Slim Bouguerra
wrote:
> Thanks Gian for taking the lead on this!
>
>
> On Tue, Jun 18, 2019 at 11:50 PM Himanshu wrote:
>
> > SGTM
> >
> > On Tue, Jun 18, 2019 at 6:16 PM Gian Merlino wrote:
> &g
Hey Druids,
Realtime nodes (the original Druid streaming ingestion mechanism, predating
both realtime tasks and the Kafka/Kinesis indexing services) have been
deprecated for years. Recently, Clint opened a PR to remove them:
https://github.com/apache/incubator-druid/pull/7915
I think this is a
, 2019 at 9:15 PM Gian Merlino wrote:
> Another update: as of
> https://github.com/apache/incubator-druid-website-src/pull/1 and
> https://github.com/apache/incubator-druid-website/pull/7, the
> https://druid.apache.org/ site is now serving almost all pages from
> druid.io, except:
:
> It sounds like we are doing release after release with out enough time to
> validate candidates, in the long run this might hurt adoption.
>
> On Fri, May 10, 2019 at 08:44 Gian Merlino wrote:
>
> > It sounds like a plan to me.
> >
> > On Thu, May 9, 2019 at 6:53 P
Is anyone going to the Apache Roadshow in Chicago tomorrow? I'll be around
if anyone wants to meet up.
It sounds like a plan to me.
On Thu, May 9, 2019 at 6:53 PM Clint Wylie wrote:
> I know 0.14.1-incubating just released, and the 0.15.0-incubating branch
> has already been cut, but
> https://github.com/apache/incubator-druid/issues/7607 which was introduced
> in 0.14.1-incubating seems like a
Hey Merlin,
You don't need permission to contribute: we use ASF's GitHub account at
https://github.com/apache/druid. Anyone can raise an issue, PR, etc. Please
check out the CONTRIBUTING.md doc before you start for a few guidelines.
And happy Druiding!!
On Thu, May 16, 2019 at 3:36 AM 李 梦林
Images from the docs (which live in the main Druid repo) should - I believe
- be Apache 2.0 licensed due to the fact that the repo is under that
license and all the docs pages have Apache 2.0 headers. The images don't,
but, you can't really put a header on an image. IMO the intent of
contributors
FYI: I just raised https://youtrack.jetbrains.com/issue/TW-60491 for what
looks like a TeamCity issue that is affecting Druid PRs right now.
the
Apache version has dropped to the #3 spot (down from #2 yesterday; and down
from where the legacy page was pre-migration, which was #1).
I think this means we do need to try to get 301s figured out.
On Sun, Apr 28, 2019 at 3:06 PM Gian Merlino wrote:
> Google has picked up the new URL as of t
will work fine. Do not use the rel=canonical tag in place of a
> proper redirect.
>
> I wasn't able to find similar guidance re: this issue for DuckDuckGo.
>
> On Mon, Apr 29, 2019 at 10:42 AM Gian Merlino wrote:
>
> > Another update: SEO is not looking great after another day p
I think it's nice for Druid's builtin metrics system to be somewhat
comprehensive (or at least be able to, if you turn the right stuff on)
since it makes measurement more generally accessible.
On Fri, Apr 19, 2019 at 5:22 PM Charles Allen
wrote:
> We use the gcp profiler to get this kind of
It sounds like a useful thing to me. Rather than the string 'concise' it
probably makes sense to put the BitmapSerdeFactory object there, since
that's what's responsible for reading the bitmaps and it should encapsulate
all available information about them. (See DictionaryEncodedColumnPartSerde)
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 (return rows in the order they become
available, rather than in query order sequence). I believe the SQL standard
+1 for cutting 0.15.0-incubating from master on Monday. Thanks for
volunteering.
On Fri, May 3, 2019 at 2:08 PM Jihoon Son wrote:
> It has been 3 months since 0.14.0 was branched out (it was at the end of
> January) and it's time for 0.15!
>
> Even though 0.14.1 release is still in progress,
Hey Rajiv,
Since we do time-based releases every 3 months, rather than feature-based
releases, the list would be anything that's been done since the last
release from master (0.14.0) was branched off. Part of the role of release
manager, that Jihoon is volunteering for, is putting together the
es which should be merged before release.
>
> Jihoon
>
> On Fri, May 3, 2019 at 3:00 PM Gian Merlino wrote:
>
> > +1 for cutting 0.15.0-incubating from master on Monday. Thanks for
> > volunteering.
> >
> > On Fri, May 3, 2019 at 2:08 PM Jihoon Son wrote:
> &
Hey Abhishek,
You don't need any special permissions to contribute, just join the
discussion here on the dev list, and contributing on GitHub:
https://github.com/apache/druid
Welcome to the community!!
On Sat, Apr 27, 2019 at 7:22 AM Abhishek Sharma
wrote:
> Hi All,
>
> I would like to
Hey Ashish,
This would be a better question for the users list, which is often used for
support and general help type questions. The dev list is meant for
development oriented discussions. That being said, try getting started
here: http://druid.io/docs/latest/tutorials/tutorial-tranquility.html.
a page title change to
"Redirecting..."
On Fri, Apr 26, 2019 at 11:00 AM Gian Merlino wrote:
> An update: this is done now since a couple of days ago, but Google and
> Bing are still showing http://druid.io/community for a search for "druid
> community" or even "ap
I haven't seen objection, so, I will do a PR to make this change soon.
On Mon, Apr 22, 2019 at 7:04 PM Gian Merlino wrote:
> I think it's fine to release new query features that don't have Druid SQL
> support, although I would certainly encourage people to add SQL support
> eve
Hey Kiran,
You can get on the dev list by writing to dev-subscr...@druid.apache.org
and check https://druid.apache.org/community/ for other community channels
like the user list. Welcome to the community!!
Gian
On Fri, Apr 26, 2019 at 9:08 AM kirankumar D G
wrote:
> Hi,
>
> Please add me to
ub.com/apache/incubator-druid-website/pull/3
> https://github.com/druid-io/druid-io.github.io/pull/591
>
> On Mon, Apr 22, 2019 at 3:04 PM Gian Merlino wrote:
>
> > That sounds good to me. I would also consider adding canonical tags to
> all
> > druid.apache.org pages so
That makes sense to me. Are you interested in doing a PR to the
docker-druid repo to make its README point to the new Dockerfiles? If so,
that should do it.
On Fri, Apr 26, 2019 at 3:33 AM Jokin Cuadrado wrote:
> Hi, I was searching for a way to run druid on docker for some
> experimentation,
Are people able to vote for features in GitHub issues? Are they able to
> > > vote to them if they are closed? I think it’s useful for people to
> > continue
> > > to chime in on features, and eventually build consensus about what
> should
> > > be built.
> &
ot be motivated to report further bugs.
>
>
>
> On Thu, Jul 4, 2019 at 9:13 PM Gian Merlino wrote:
>
> > I think that would be a perfect reason to comment on those issues and
> > mention that they are still relevant. The stalebot message even invites
> you
&g
Thank you Jihoon!!
On Thu, Jun 27, 2019 at 1:19 PM Jihoon Son wrote:
> The Apache Druid team is proud to announce the release of Apache Druid
> (incubating) 0.15.0.
>
> Apache Druid 0.15.0-incubating contains over 250 new features,
> performance/stability/documentation improvements, and bug
Hey Rajiv,
This doc was removed in favor of a new tutorial with guidelines about how
to configure a production cluster. I believe it should be uploaded when
Druid 0.15.0 is released (which should be very soon!), and at that point
the old url should redirect to the new one.
On Wed, Jun 26, 2019
ow of any examples in Druid SQL
> where a sql aggregation function returns an array of doubles? I looked at
> DoubleSketchSqlAggregator but it seems to be returning a single double
> value.
>
>
> On Wed, Jun 26, 2019 at 10:26 PM Gian Merlino wrote:
>
> > Hey Samarth,
>
rg)
* Fangjin Yang (f...@apache.org)
* Gian Merlino (g...@apache.org)
* Himanshu Gupta (himans...@apache.org)
* Jihoon Son (jihoon...@apache.org)
* Jonathan Wei (jon...@apache.org)
* Julian Hyde (jh...@apache.org)
* Kurt Young
.
On Tue, Jul 9, 2019 at 9:45 AM Gian Merlino wrote:
> An update, I'm just waiting for replies to some of the messages I sent to
> committers privately asking if they are interested in joining the initial
> PMC. As mentioned last week -- I'll add folks that express interest to a
> propose
Just write to dev-subscr...@druid.apache.org
On Wed, Jul 10, 2019 at 9:42 AM Parag Jain wrote:
>
>
Hey Daniel & Radu,
Yes, we use sha512 checksums for our artifacts. I think the confusion is
probably with the copy on the "closer.cgi" download page, which has an
example command that refers specifically to SHA256:
> Hashes can be calculated using GPG:
> % gpg --print-md SHA256 downloaded_file
>
I haven't seen something like that before. The package version 4.2.6 is
here on NPM: https://www.npmjs.com/package/@types/react-copy-to-clipboard
Is it possible your build environment is blocking NPM?
On Thu, Jul 11, 2019 at 9:43 AM Eyal Yurman
wrote:
> The mvn command was actually:
> mvn
Hey Eschar,
I see Himanshu wrote a note in
https://github.com/apache/incubator-datasketches-java/issues/263, and I
added a little bit of extra info as well. Hope it helps!
On Tue, Jul 2, 2019 at 7:06 AM Eshcar Hillel
wrote:
> I did some thinking and alternative 2 would not allow supporting a
’s proposed list:
>
> * Charles Allen
> * David Lim
> * Eric Tschetter
> * Fangjin Yang
> * Gian Merlino
> * Himanshu Gupta
> * Jihoon Son
> * Jonathan Wei
> * Kurt Young
> * Lijin Bin
> * Maxime Beauchemin
> * Nishant Bangarwa
> * Parag Jain
> * Roman
thoughts on that?
>
> Thanks,
> Jon
>
> On Tue, Mar 12, 2019 at 7:19 PM Gian Merlino wrote:
>
> > OpenOffice and Groovy both chose to sort of "meld" their classic and
> Apache
> > sites together: https://www.openoffice.org/, http://groovy-lang.org/.
&g
t; >
> > > On Thu, Apr 18, 2019 at 6:23 PM Fangjin Yang wrote:
> > >
> > > > Strong +1
> > > >
> > > > I think there's been enough production usage of Druid SQL, it matches
> > > what
> > > > native JSON-over-http
Hey Druids,
Sometimes I feel like this too:
https://twitter.com/julianhyde/status/1108502471830204416.
I believe our code review process today has too much friction in it, and
that we can work to reduce it. The two main frictions I see are code
reviews not happening in a timely manner, and code
FYI - I just raised an infra ticket to move notification emails for the
incubator-druid-website repo to commits@druid, just like the main
incubator-druid repo: https://jira.apache.org/jira/browse/INFRA-18260. This
is to keep github-related stuff going to commits@ so it can be more easily
separated
y changes
once review has begun (even if this means not implementing certain
nice-to-have refactorings).
On Tue, Apr 23, 2019 at 9:25 AM Slim Bouguerra wrote:
> On Mon, Apr 22, 2019 at 7:43 PM Gian Merlino wrote:
>
> > Hey Druids,
> >
> > Sometimes I feel lik
I'm not seeing the attached png (it shows up as a broken image). Seeing
code coverage sounds interesting as an FYI kind of thing. I wouldn't want
to use it as a gating factor, but seeing it could be interesting.
On Wed, Apr 17, 2019 at 9:58 AM Egor Ryashin
wrote:
> Hi,
>
> I wonder if we would
uot;Regularly do X"):
> - A rate of regularity may vary significantly, but there should be some
> slice of the time that *every* regular contributor devotes to *every*
> mentioned activity, even as little as 1 hour in 2 weeks (about 1% of their
> time). Just not zero.
> - A
> I'm inclined to say the expected data shape returned should be preserved.
This seems like a good general principle. Callers generally are happier
when the result shape is consistent. I have to admit, I don't understand
why an empty array would be better than null or vice versa. Both are a
I think it's a good idea.
In particular, https://github.com/apache/incubator-druid/pull/7512 and
https://github.com/apache/incubator-druid/pull/7520 affect the ability to
do rolling updates successfully for people using native Kafka or
parallel-batch indexing. In datasketches land,
Hey Hao,
GenericIndexed V2 is used when a column is large enough that it must be
spread over multiple files (each file has a 2GB limit, since that's the
most that can be mapped into a single ByteBuffer). Check out
LargeColumnSupportedComplexColumnSerializer for an entry point. It's used
today for
FYI -- I've also submitted an address change request from druid.io ->
druid.apache.org through Google's automated system.
On Wed, Jun 12, 2019 at 1:56 PM Gian Merlino wrote:
> Sorry, I mean references to https://github.com/druid-io/druid-io.github.io
> should be changed to https://g
Anyone have thoughts on the above?
If there are no objections, I'll reach out privately to any current
committer that isn't on the PPMC and ask if they are interested in joining
the top level PMC, and then add those names to the proposed resolution.
On Wed, Jun 26, 2019 at 10:23 PM Gian Merlino
+1 (binding)
- Verified signatures and checksums of both src and bin packages.
- NOTICE, LICENSE, DISCLAIMER are present in both src and bin packages.
- Source tarball git.version file is present and correct.
- Source tarball builds ok with "mvn package".
- Ran through quickstart on binary
I think it'd be ok to call those examples bugs. In professional programming
contexts I've always used 'bug' in a wide sense, meaning any sort of flaw
or issue in a system that causes user-visible bad behavior. It could be a
programming mistake, a design flaw, or even a problem with a dependency.
Thanks, Chi!
I haven't had a chance to experience yet how these tools work with PRs, but
will keep a look out for how useful they seem. A quick scan through the
LGTM report of master shows that it found some real issues and isn't too
noisy. There's a spread of false positives (it doesn't like
). This could have been called "improvement" unless it
> was caused by a programming mistake. I would not call anything which is
> caused by a programming mistake a mere "improvement", it's always a "bug"
> for me.
>
> On Thu, 15 Aug 2019 at 08:08, Gian Merlino w
Oh, great! It looks like this post does announce the change on behalf of
Amazon:
https://aws.amazon.com/about-aws/whats-new/2019/04/amazon_kinesis_data_streams_changes_license_for_its_consumer_library_to_apache_license_2_0/
It would simplify things to include the KCL in Druid’s Kinesis
Coveralls result.
On Tue, Aug 20, 2019 at 11:35 PM Gian Merlino wrote:
> Thanks, Chi!
>
> I haven't had a chance to experience yet how these tools work with PRs,
> but will keep a look out for how useful they seem. A quick scan through the
> LGTM report of master shows that it
apache/incubator-druid/pull/8352 - the patch basically
> adds a try/catch around a log statement and coverage decreased by 9.1%. I
> tried restarting Travis to see if it would rerun Coveralls but it does not.
>
> On Fri, Aug 23, 2019 at 1:31 AM Gian Merlino wrote:
>
> > FYI, something
What do you all think about replacing
https://github.com/druid-io/docker-druid, then, with a link to the
Dockerfile in the main Druid repo (and to our dockerhub page once it is
published), then? It is confusing to have the old repo still there, when
it's not being kept up to date.
On Thu, Aug 22,
PPMC folks, we need one more binding vote to refer this release to the
IPMC. Would someone mind taking a look?
On Sun, Aug 4, 2019 at 11:19 PM Benedict Jin wrote:
>
>
> On 2019/08/01 23:38:30, Clint Wylie wrote:
> > Hi all,
> >
> > I have created a build for Apache Druid (incubating) 0.15.1,
nd binary
> > - compiled source and ran unit tests
> > - started druid services using quickstart
> >
> > On Tue, Aug 6, 2019 at 7:45 PM Gian Merlino wrote:
> >
> > > PPMC folks, we need one more binding vote to refer this release to the
>
Hey Prashant,
Thanks for the report, we'll look into this.
Btw- I would generally not expect datasources that use Kafka ingestion to
be _fully_ aggregated, since it doesn't guarantee perfect rollup (it'll
roll up rows that come in to the same Kafka ingestion task, which is based
on when they
uté wrote:
>
> > Yes, probably not a discussion for a voting thread, but I'm happy to look
> > into getting official docker images shipped. I know that's been asked
> for.
> > I believe a docker fix was merged this morning to master so we should be
> > good for 0.16
> &g
nly a single Kafka partition and rows are coming in
> the order of timestamp and at the timestamp itself (no out of order rows
> are being ingested).
>
> On Fri, Aug 9, 2019 at 10:21 AM Gian Merlino wrote:
>
> > Hey Prashant,
> >
> > Thanks for the report, we'll
l/8084.
>
> On Sat, 6 Jul 2019 at 01:35, Gian Merlino wrote:
>
> > You raise a good point but I don't think leaving issues open with no
> > response forever is a good solution either. That's probably what would
> have
> > happened to your issues if we didn't have a stalebot
Hi, this vote is now closed. I will put up a summary shortly.
On Wed, Jul 10, 2019 at 11:19 PM Benedict Jin wrote:
>
>
> On 2019/07/10 16:52:21, Gian Merlino wrote:
> > Following our discussion on the dev mailing list (
> >
> https://list
Hi all,
The vote to proceed with graduation of Apache Druid passed with ten +1 PPMC
votes:
David Lim
Fangjin Yang
Gian Merlino
Himanshu Gupta
Jihoon Son
Jonathan Wei
Kurt Young
Lijin Bin
Nishant Bangarwa
Slim Bouguerra
In addition the following three non-binding +1 votes were received
Hey Pierre,
You submitted it to the right place. [3] is updated manually, and
periodically, based on changes to [2]. I just merged your patch, so it will
go out with the next website update. Thanks for your contribution!
On Fri, Sep 20, 2019 at 12:28 AM Pierre Smits
wrote:
> Hi all,
>
>
Congrats Furkan!!
On Tue, Sep 17, 2019 at 1:53 PM Jonathan Wei wrote:
> The Project Management Committee (PMC) for Apache Druid
> has invited Furkan Kamaci to become a committer and we are pleased
> to announce that he has accepted.
>
> Being a committer enables easier contribution to the
>
Congrats Fokko!!
On Tue, Sep 17, 2019 at 1:53 PM Jonathan Wei wrote:
> The Project Management Committee (PMC) for Apache Druid
> has invited Fokko Driesprong to become a committer and we are pleased
> to announce that he has accepted.
>
> Being a committer enables easier contribution to the
>
Hey Samarth,
This kind of thing doable in Druid SQL, which will only return the stuff
you SELECT. Native queries don't have a concept like that, so they always
return everything, even if you intended certain things to be 'internal'
computations and aren't interested in seeing the results
.
On Tue, Jul 2, 2019 at 7:46 PM 宾莉金（binlijin） wrote:
> +1 Congratulations!
>
> Julian Hyde 于2019年7月3日周三 上午1:51写道：
>
> > > 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, Taylo
Thanks Jihoon!
On Wed, Nov 6, 2019 at 11:35 AM Jihoon Son wrote:
> Hi all,
>
> our CI, especially TeamCity and LGTM had been broken for a while because of
> a missing library in the maven repository. If you see the following error
> in the log, your PR is suffering the same problem.
>
>
Is that configuration possible?
On Sat, Nov 16, 2019 at 1:00 AM Roman Leventov wrote:
> I think it would be better to configure the stale-bot to leave a message in
> a PR every 60 days, but not actually close PRs with Bug label. Feels a
> little like sweeping problems under the carpet.
>
I quite dislike EasyMock (I think it leads to brittle tests that
over-couple test code with production code). But that comment aside, I
think it is reasonable to use static imports for DSL-type stuff in tests,
which it sounds like what you are suggesting. So that sounds good to me. I
would still
Hey Druids,
The LGTM tool is broken right now and it is holding up PRs from being
validated. Vadim and I looked into it a bit and it seems likely that
something is wrong with an internal TLS proxy on the LGTM side (certain
fetches to npm through that proxy don't work, even though they work
I certainly think that would be appropriate.
I would like to submit to the board the same resolution we previously had
approved by both the dev list & the IPMC, with just the addition of some
new initial PMC members (new committers, based on previous discussion that
the initial PMC should include
This sounds great to me. Thanks Jon.
On Wed, Dec 4, 2019 at 1:42 PM Jonathan Wei wrote:
> Hi all,
>
> Since it's been ~3 months since our last major release (0.16.0 released on
> Sep. 24, branch created Aug. 27), I propose creating the 0.17.0 branch from
> master next Monday (Dec. 9).
>
> I can
That is fair, I suggest we change the first section (issues remaining) to
this then:
> The project is not aware of any issues blocking graduation. Druid
previously shelved a resolution to graduate due to a potential brand issue,
which the project has since been working on with VP Brand. It is now
gjin Yang (f...@apache.org)
* Fokko Driesprong (fo...@apache.org)
* Furkan Kamaci(kam...@apache.org)
* Gian Merlino (g...@apache.org)
* Himanshu Gupta (himans...@apache.org)
* Jihoon Son (jihoon...@apache.org)
* Jonathan Wei (jon...@apache.
Hi Justin,
I think it's fair to say that there aren't any unfinished issues, so it
makes sense for the section to be blank. You might remember that a few
months ago, Druid got close enough to graduating that the project had a
resolution approved by the dev community and the IPMC, and had been
Actually I'd suggest the opposite approach: use Scan if you want a stream.
It can handle almost any number of results (you might want to set
druid.broker.http.maxQueuedBytes to 1000 or so if you are doing large
resultsets; this will likely be the default in the future).
With Scan queries,
By the way, a link to the vote thread:
https://lists.apache.org/thread.html/2385d5545fa5bd13baf45bd7258fafa7694334d9d14267489d21d99b%40%3Cdev.druid.apache.org%3E
On Sat, Dec 7, 2019 at 1:48 PM Gian Merlino wrote:
> This vote passed with 8 PPMC +1s:
>
> David Lim
> Fangjin Yang
&g
+1!
> > > > > > > > >
> > > > > > > > > Kind Regards,
> > > > > > > > > Furkan KAMACI
> > > > > > > > >
> > > > > > > > > 4 Ara 2019 Çar, saat 23:58 tarihinde David Lim <
> > > > > david...@apache.org>
> > &g
This vote passed with 8 PPMC +1s:
David Lim
Fangjin Yang
Gian Merlino
Jihoon Son
Jonathan Wei
Julian Hyde
Kurt Young
Slim Bouguerra
Xavier Léauté
In addition, the following nonbinding +1s were received:
Benedict Jin
Clint Wylie
Fokko Driesprong
Furkan Kamaci
I will refer this to the Incubator
Hey Sascha,
We are now operating under Apache policy, meaning we require CLAs for
committers but not for every single contributor. I've written a patch to
update our site, thanks for pointing it out:
https://github.com/apache/incubator-druid-website-src/pull/65
On Tue, Oct 15, 2019 at 8:56 AM
Hi Gautam,
We have a list of suggested starter issues:
https://github.com/apache/incubator-druid/issues?utf8=%E2%9C%93=is%3Aopen+is%3Aissue++label%3AStarter+
Additionally, contributions to clarify or correct documentation are always
appreciated.
On Mon, Oct 14, 2019 at 6:55 PM gautam gupta
Hey Tony,
I accidentally rejected your message to the Druid dev list about writing a
custom parser, by fat-fingering the item in the moderation queue. Sorry
about that!
You had asked about being pointed in a useful direction in terms of writing
a custom parser for a proprietary data format. You
You can join by sending a message to dev-subscr...@druid.apache.org.
On Fri, Oct 25, 2019 at 10:03 AM 张天生 wrote:
> apply to join mail list
>
"format": "auto"
> },
> "dimensionsSpec": {
> "dimensions": []
> }
> }
> }
> }
> }
>
>
> my module looks like:
>
> public class MyTypeEventDruidParserModule implements DruidModu
The patch in https://github.com/apache/incubator-druid/pull/8900 was
effective.
If you have an open PR, please merge master into your branch in order to
fix LGTM.
On Mon, Nov 18, 2019 at 2:30 PM Gian Merlino wrote:
> Hey Druids,
>
> The LGTM tool is broken right now and it is holdi
For reference, a (brief) earlier conversation about this:
https://github.com/apache/incubator-druid/issues/4275, which links to
https://github.com/apache/incubator-druid/pull/4254#discussion_r116628607,
which links to
pydruid (https://github.com/druid-io/pydruid) is a project that is not part
of Druid, but is related:
1) Its committers are all also Druid committers.
2) Its community is a subset of the Druid community (assuming pydruid
users/devs are all also Druid users or devs, which seems likely).
3) It's
201 - 300 of 439 matches
Mail list logo
