Skip to content

Be more respectful of maxRowsInMemory.#3284

Merged
dclim merged 1 commit intoapache:masterfrom
gianm:maxRowsInMemory
Jul 26, 2016
Merged

Be more respectful of maxRowsInMemory.#3284
dclim merged 1 commit intoapache:masterfrom
gianm:maxRowsInMemory

Conversation

@gianm
Copy link
Copy Markdown
Contributor

@gianm gianm commented Jul 25, 2016

  • Appenderator: Respect maxRowsInMemory across all sinks.
  • KafkaIndexTask: Respect maxRowsInMemory across all partitions.

Fixes #3271.

- Appenderator: Respect maxRowsInMemory across all sinks.
- KafkaIndexTask: Respect maxRowsInMemory across all partitions.
@fjy fjy added this to the 0.9.2 milestone Jul 25, 2016
@fjy
Copy link
Copy Markdown
Contributor

fjy commented Jul 25, 2016

👍

@dclim
Copy link
Copy Markdown
Contributor

dclim commented Jul 26, 2016

👍

@dclim dclim merged commit 8030f1c into apache:master Jul 26, 2016
gianm added a commit to gianm/druid that referenced this pull request Nov 2, 2017
AppenderatorImpl already applies maxRowsInMemory across all sinks. So dividing by
the number of Kafka partitions is pointless and effectively makes the interpretation
of maxRowsInMemory lower than expected.

This undoes one of the two changes from apache#3284, which fixed the original bug twice.
In this, that's worse than fixing it once.
gianm added a commit that referenced this pull request Nov 2, 2017
AppenderatorImpl already applies maxRowsInMemory across all sinks. So dividing by
the number of Kafka partitions is pointless and effectively makes the interpretation
of maxRowsInMemory lower than expected.

This undoes one of the two changes from #3284, which fixed the original bug twice.
In this, that's worse than fixing it once.
gianm added a commit to gianm/druid that referenced this pull request Nov 2, 2017
…e#5034)

AppenderatorImpl already applies maxRowsInMemory across all sinks. So dividing by
the number of Kafka partitions is pointless and effectively makes the interpretation
of maxRowsInMemory lower than expected.

This undoes one of the two changes from apache#3284, which fixed the original bug twice.
In this, that's worse than fixing it once.
jihoonson pushed a commit that referenced this pull request Nov 3, 2017
#5036)

AppenderatorImpl already applies maxRowsInMemory across all sinks. So dividing by
the number of Kafka partitions is pointless and effectively makes the interpretation
of maxRowsInMemory lower than expected.

This undoes one of the two changes from #3284, which fixed the original bug twice.
In this, that's worse than fixing it once.
gianm added a commit to implydata/druid-public that referenced this pull request Nov 3, 2017
…e#5034)

AppenderatorImpl already applies maxRowsInMemory across all sinks. So dividing by
the number of Kafka partitions is pointless and effectively makes the interpretation
of maxRowsInMemory lower than expected.

This undoes one of the two changes from apache#3284, which fixed the original bug twice.
In this, that's worse than fixing it once.
gianm added a commit to implydata/druid-public that referenced this pull request Nov 8, 2017
…e#5034)

AppenderatorImpl already applies maxRowsInMemory across all sinks. So dividing by
the number of Kafka partitions is pointless and effectively makes the interpretation
of maxRowsInMemory lower than expected.

This undoes one of the two changes from apache#3284, which fixed the original bug twice.
In this, that's worse than fixing it once.
seoeun25 added a commit to seoeun25/incubator-druid that referenced this pull request Jan 10, 2020
seoeun25 pushed a commit to seoeun25/incubator-druid that referenced this pull request Feb 25, 2022
seoeun25 pushed a commit to seoeun25/incubator-druid that referenced this pull request Feb 25, 2022
@gianm gianm deleted the maxRowsInMemory branch September 23, 2022 19:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants