Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add context to kafka supervisor for the kafka indexing task #3464

Merged
merged 1 commit into from
Oct 5, 2016
Merged

add context to kafka supervisor for the kafka indexing task #3464

merged 1 commit into from
Oct 5, 2016

Conversation

pjain1
Copy link
Member

@pjain1 pjain1 commented Sep 16, 2016

Fixes #3463

@@ -52,6 +54,7 @@ public KafkaSupervisorSpec(
@JsonProperty("dataSchema") DataSchema dataSchema,
@JsonProperty("tuningConfig") KafkaTuningConfig tuningConfig,
@JsonProperty("ioConfig") KafkaSupervisorIOConfig ioConfig,
@JsonProperty("context") Map<String, Object> context,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

docs ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure if we should have docs for it because for existing tasks as well context is not mentioned anywhere in the docs. Can add if required.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see a reason why it is not documented ? IMHO if it has a added value it should be documented for both task and supervisor.

@pjain1
Copy link
Member Author

pjain1 commented Sep 16, 2016

added documentation

@b-slim
Copy link
Contributor

b-slim commented Sep 16, 2016

👍

1 similar comment
@himanshug
Copy link
Contributor

👍

@cheddar
Copy link
Contributor

cheddar commented Sep 19, 2016

This is just an overall comment, but the overriding of things like memory usage on a per-task basis actually breaks the encapsulation and control that the middle manager has over the resources used on its machine.

That is, it is now possible for someone external from the system to set properties that effectively stop other people from being able to schedule and run other tasks. It looks like that capability was already introduced in #1604 so this isn't anything new. I'm fine with it going in, but I wanted to call out that this is something we are exposing now.

@pjain1
Copy link
Member Author

pjain1 commented Sep 25, 2016

@cheddar should I remove the documentation for it ?

@pjain1
Copy link
Member Author

pjain1 commented Sep 25, 2016

removed documentation of this feature because of @cheddar's comment

@pjain1 pjain1 added this to the 0.9.3 milestone Sep 25, 2016
@pjain1 pjain1 added the Feature label Sep 25, 2016
@pjain1 pjain1 merged commit 5929035 into apache:master Oct 5, 2016
@pjain1
Copy link
Member Author

pjain1 commented Oct 5, 2016

merged as it had two 👍

fundead pushed a commit to fundead/druid that referenced this pull request Dec 7, 2016
dgolitsyn pushed a commit to metamx/druid that referenced this pull request Feb 14, 2017
@pjain1 pjain1 deleted the kafka_context branch September 13, 2017 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants