Re: TeamCity having problems

It would be good to document that — for my first few PRs I just assumed that I couldn't get a login as a random contributor. On Fri, Feb 22, 2019 at 12:56 PM Justin Borromeo wrote: > You can click the “Log in as Guest” button to access the results without > registering a TeamCity account. > >

Re: TeamCity having problems

You can click the “Log in as Guest” button to access the results without registering a TeamCity account. Justin > On Feb 22, 2019, at 12:55 PM, Julian Hyde wrote: > > The page [1] requires a login. So, a Druid contributor has to get a TeamCity > account? > > That would be OK, if TeamCity

Re: TeamCity having problems

The page [1] requires a login. So, a Druid contributor has to get a TeamCity account? That would be OK, if TeamCity provides a lot of value. But it raises the bar for occasional and first-time contributors. Julian [1]

Re: TeamCity having problems

I've been seeing these issues on my PR. They tend to be declarations of 2800+ errors, which mostly seem to be "Redundant throws clause" and "Unused declaration", and mostly seem to be incorrect when I take a look. On Fri, Feb 22, 2019 at 11:00 AM Gian Merlino wrote: > It's one of the two

Re: Knowledge sharing between Druid developers via technical talks

Heads up, one blocker I ran into with recording is that there are a slew of forms that need signed to be in compliance with Model Release and other such things. Without a legal team making sure all the paperwork is in line there might be some risk. Does anyone know if the ASF have any such

Re: Knowledge sharing between Druid developers via technical talks

Hi, It would be really great to organize/attend such tech talks/meetups and record them. On the other hand, we can create a roadmap to touch common points to cover i.e. * How to install Druid for production * Tips & Tricks of schema design * Advanced queries by example * How to tune your Druid

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: Knowledge sharing between Druid developers via technical talks

Could be nice for the last talk in a meetup to be one of these, that way anyone that isn't interested could leave early. On Fri, Feb 22, 2019 at 9:51 AM Eyal Yurman wrote: > Thanks for the response, that sounds great! > > Since the meetups are user-focused, perhaps a separate "track" which is >

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: Knowledge sharing between Druid developers via technical talks

Thanks for the response, that sounds great! Since the meetups are user-focused, perhaps a separate "track" which is open to all but is dev-focused? This could be before/after the main event. I promise that once I get enough experience with the code base, I'd volunteer to present, but hopefully,

Re: TeamCity having problems

Hi Gian, There maybe a problem with permissions after upgrading Apache parent POM version to 21. This maybe a related issue: https://jira.apache.org/jira/browse/INFRA-10286 Kind Regards, Furkan KAMACI On Fri, Feb 22, 2019 at 7:13 PM Gian Merlino wrote: > It looks like TeamCity is having

TeamCity having problems

It looks like TeamCity is having problems since a few days ago - builds of master and PRs are flaky. Here's the link to recent builds of master:

Re: The compatibility rules for alert data

My feeling is that the alerts are more like log messages or exceptions (where, in general, there isn't a particular contract around what exceptions get thrown when, except in specific cases like query errors: http://druid.io/docs/latest/querying/querying#query-errors). So reasonable changes could

The compatibility rules for alert data

What are the compatibility rules for alert data, as in log.makeAlert(...).addData("myData", myData).emit(). Shall the key strings and the data format be changed only in major Druid releases?