Public

getNumRowsInSegment

isOk

getParseException

getSegmentIdentifier

getTotalNumRowsInAppenderator

isPersistRequired

isPushRequired

<init>

fail

Dictionary

Finding current android device location

A collection that associates an ordered pair of keys, called a row key and a
column key, with a sing

com.google.common.collect.Table

A specialized Writer that writes to a file in the file system. All write
requests made by calling me

java.io.FileWriter

A thread is a thread of execution in a program. The Java Virtual Machine allows
an application to ha

java.lang.Thread

HashMap is an implementation of Map. All optional operations are supported.All
elements are permitte

java.util.HashMap

HashSet is an implementation of a Set. All optional operations (adding and
removing) are supported. 

java.util.HashSet

Basic implementation of javax.sql.DataSource that is configured via JavaBeans
properties. This is no

org.apache.commons.dbcp.BasicDataSource

putExtra

getApplicationContext

notifyDataSetChanged

"WTF?! Restored topic[%s] but expected topic[%s]"

"WTF?! Restored partitions[%s] but expected partitions[%s]"

// Could eventually support leader/follower mode (for keeping replicas more in sync)

// The partition assignments may have changed while paused by a call to setEndOffsets() so reassign

// partitions upon resuming. This is safe even if the end offsets have not been modified.

// The retrying business is because the KafkaConsumer throws OffsetOutOfRangeException if the seeked-to

// offset is not present in the topic-partition. This can happen if we're asking a task to read from data

// that has not been written yet (which is totally legitimate). So let's wait for it to show up.

"OffsetOutOfRangeException with message [%s]"

"Got topic[%s] partition[%d] offset[%,d]."

"Skipped to offset[%,d] after offset[%,d] in partition[%d]."

"WTF?! Got offset[%,d] after offset[%,d] in partition[%d]."

/**
   * This method reads input data row by row and adds the read row to a proper segment using {@link BaseAppenderatorDriver}.
   * If there is no segment for the row, a new one is created.  Segments can be published in the middle of reading inputs
   * if one of below conditions are satisfied.
   *
   * <ul>
   * <li>
   * If the number of rows in a segment exceeds {@link ParallelIndexTuningConfig#targetPartitionSize}
   * </li>
   * <li>
   * If the number of rows added to {@link BaseAppenderatorDriver} so far exceeds {@link ParallelIndexTuningConfig#maxTotalRows}
   * </li>
   * </ul>
   *
   * At the end of this method, all the remaining segments are published.
   *
   * @return true if generated segments are successfully published, otherwise false
   */

// Initialize maxRowsPerSegment and maxTotalRows lazily

"Encountered row with timestamp that cannot be represented as a long: [%s]"

// Segments are created as needed, using a single sequence name. They may be allocated from the overlord

// (in append mode) or may be created on our own authority (in overwrite mode).

// There can be some segments waiting for being published even though any rows won't be added to them.

// If those segments are not published here, the available space in appenderator will be kept to be small

// which makes the size of segments smaller.

/**
   * This method reads input data row by row and adds the read row to a proper segment using {@link BaseAppenderatorDriver}.
   * If there is no segment for the row, a new one is created.  Segments can be published in the middle of reading inputs
   * if one of below conditions are satisfied.
   *
   * <ul>
   * <li>
   * If the number of rows in a segment exceeds {@link IndexTuningConfig#targetPartitionSize}
   * </li>
   * <li>
   * If the number of rows added to {@link BaseAppenderatorDriver} so far exceeds {@link IndexTuningConfig#maxTotalRows}
   * </li>
   * </ul>
   *
   * At the end of this method, all the remaining segments are published.
   *
   * @return true if generated segments are successfully published, otherwise false
   */

// Overwrite mode, guaranteed rollup: segments are all known in advance and there is one per sequenceName.

// Append mode: Allocate segments as needed using Overlord APIs.

// Overwrite mode, non-guaranteed rollup: We can make up our own segment ids but we don't know them in advance.

"Could not find interval for timestamp [%s]"

"Could not find shardSpec for interval[%s]"

// Sequence name is based solely on the shardSpec, and there will only be one segment per sequence.

// incremental segment publishment is allowed only when rollup don't have to be perfect.

How to use getNumRowsInSegmentmethodin org.apache.druid.segment.realtime.appenderator.AppenderatorDriverAddResult

Best Java code snippets using org.apache.druid.segment.realtime.appenderator.AppenderatorDriverAddResult.getNumRowsInSegment (Showing top 6 results out of 315)

How to use
getNumRowsInSegment
method
in
org.apache.druid.segment.realtime.appenderator.AppenderatorDriverAddResult