Re: Is there already a KIP or JIRA to change auto.create.topics.enable to default to false?

[Grant Henke]

Feel free to create a KIP based on that discussion and drive the jira. I
don't think a KIP exists yet.

On Thu, Mar 2, 2017 at 1:28 PM, Jeff Widman  wrote:

> Thanks, that's the ticket I was thinking of.
>
> On Thu, Mar 2, 2017 at 11:19 AM, Grant Henke  wrote:
>
> > I think the idea was that once clients have the ability to create topics,
> > we would move "auto topic creation" client side and deprecate and
> > eventually remove the support for server side auto create. This
> simplifies
> > error handling, authorization, and puts the client in control of details
> > like partition counts and replication factor.
> >
> > There is a jira (KAFKA-2410
> > ) tracking the move to
> > client side auto topic creation and a discussion about some of the
> details
> > here:
> > http://search-hadoop.com/m/Kafka/uyzND1yAwWoCt1yc?subj=+
> > DISCUSS+Client+Side+Auto+Topic+Creation
> >
> > Since a change in the default behavior of auto.create.topics.enable would
> > be considered "breaking" I think it would be best to consider this change
> > as a part of the deprecation and eventual removal of the configuration.
> > Perhaps 0.11 would be a good timeframe to consider doing that, but it
> > depends on if the supporting features are complete.
> >
> > Thanks,
> > Grant
> >
> >
> >
> > On Thu, Mar 2, 2017 at 12:56 PM, Jeff Widman  wrote:
> >
> > > I thought I saw mention somewhere of changing the default of
> > > auto.create.topics.enable to false.
> > >
> > > I searched, but couldn't find anything in JIRA... am I imagining
> things?
> > >
> > > Now that there's API support for creating topics, the version bump to
> > > 0.11.0 seems like a good time to re-evaluate whether this default
> should
> > be
> > > flipped to false.
> > >
> > > I'm happy to create a KIP if needed, just didn't want to duplicate
> > effort.
> > >
> >
> >
> >
> > --
> > Grant Henke
> > Software Engineer | Cloudera
> > gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
> >
>



-- 
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke

Re: Is there already a KIP or JIRA to change auto.create.topics.enable to default to false?

[Jeff Widman]

Thanks, that's the ticket I was thinking of.

On Thu, Mar 2, 2017 at 11:19 AM, Grant Henke  wrote:

> I think the idea was that once clients have the ability to create topics,
> we would move "auto topic creation" client side and deprecate and
> eventually remove the support for server side auto create. This simplifies
> error handling, authorization, and puts the client in control of details
> like partition counts and replication factor.
>
> There is a jira (KAFKA-2410
> ) tracking the move to
> client side auto topic creation and a discussion about some of the details
> here:
> http://search-hadoop.com/m/Kafka/uyzND1yAwWoCt1yc?subj=+
> DISCUSS+Client+Side+Auto+Topic+Creation
>
> Since a change in the default behavior of auto.create.topics.enable would
> be considered "breaking" I think it would be best to consider this change
> as a part of the deprecation and eventual removal of the configuration.
> Perhaps 0.11 would be a good timeframe to consider doing that, but it
> depends on if the supporting features are complete.
>
> Thanks,
> Grant
>
>
>
> On Thu, Mar 2, 2017 at 12:56 PM, Jeff Widman  wrote:
>
> > I thought I saw mention somewhere of changing the default of
> > auto.create.topics.enable to false.
> >
> > I searched, but couldn't find anything in JIRA... am I imagining things?
> >
> > Now that there's API support for creating topics, the version bump to
> > 0.11.0 seems like a good time to re-evaluate whether this default should
> be
> > flipped to false.
> >
> > I'm happy to create a KIP if needed, just didn't want to duplicate
> effort.
> >
>
>
>
> --
> Grant Henke
> Software Engineer | Cloudera
> gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
>

Re: Is there already a KIP or JIRA to change auto.create.topics.enable to default to false?

[Grant Henke]

I think the idea was that once clients have the ability to create topics,
we would move "auto topic creation" client side and deprecate and
eventually remove the support for server side auto create. This simplifies
error handling, authorization, and puts the client in control of details
like partition counts and replication factor.

There is a jira (KAFKA-2410
) tracking the move to
client side auto topic creation and a discussion about some of the details
here:
http://search-hadoop.com/m/Kafka/uyzND1yAwWoCt1yc?subj=+DISCUSS+Client+Side+Auto+Topic+Creation

Since a change in the default behavior of auto.create.topics.enable would
be considered "breaking" I think it would be best to consider this change
as a part of the deprecation and eventual removal of the configuration.
Perhaps 0.11 would be a good timeframe to consider doing that, but it
depends on if the supporting features are complete.

Thanks,
Grant



On Thu, Mar 2, 2017 at 12:56 PM, Jeff Widman  wrote:

> I thought I saw mention somewhere of changing the default of
> auto.create.topics.enable to false.
>
> I searched, but couldn't find anything in JIRA... am I imagining things?
>
> Now that there's API support for creating topics, the version bump to
> 0.11.0 seems like a good time to re-evaluate whether this default should be
> flipped to false.
>
> I'm happy to create a KIP if needed, just didn't want to duplicate effort.
>



-- 
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke

Is there already a KIP or JIRA to change auto.create.topics.enable to default to false?

[Jeff Widman]

I thought I saw mention somewhere of changing the default of
auto.create.topics.enable to false.

I searched, but couldn't find anything in JIRA... am I imagining things?

Now that there's API support for creating topics, the version bump to
0.11.0 seems like a good time to re-evaluate whether this default should be
flipped to false.

I'm happy to create a KIP if needed, just didn't want to duplicate effort.