Packages

  • package root
    Definition Classes
    root
  • package org
    Definition Classes
    root
  • package apache
    Definition Classes
    org
  • package spark

    Core Spark functionality.

    Core Spark functionality. org.apache.spark.SparkContext serves as the main entry point to Spark, while org.apache.spark.rdd.RDD is the data type representing a distributed collection, and provides most parallel operations.

    In addition, org.apache.spark.rdd.PairRDDFunctions contains operations available only on RDDs of key-value pairs, such as groupByKey and join; org.apache.spark.rdd.DoubleRDDFunctions contains operations available only on RDDs of Doubles; and org.apache.spark.rdd.SequenceFileRDDFunctions contains operations available on RDDs that can be saved as SequenceFiles. These operations are automatically available on any RDD of the right type (e.g. RDD[(Int, Int)] through implicit conversions.

    Java programmers should reference the org.apache.spark.api.java package for Spark programming APIs in Java.

    Classes and methods marked with Experimental are user-facing features which have not been officially adopted by the Spark project. These are subject to change or removal in minor releases.

    Classes and methods marked with Developer API are intended for advanced users want to extend Spark through lower level interfaces. These are subject to changes or removal in minor releases.

    Definition Classes
    apache
  • package sql

    Allows the execution of relational queries, including those expressed in SQL using Spark.

    Allows the execution of relational queries, including those expressed in SQL using Spark.

    Definition Classes
    spark
  • package types

    Contains a type system for attributes produced by relations, including complex types like structs, arrays and maps.

    Contains a type system for attributes produced by relations, including complex types like structs, arrays and maps.

    Definition Classes
    sql
  • package ops
    Definition Classes
    types
  • TimeTypeApiOps
  • TypeApiOps

package ops

Ordering
  1. Alphabetic
Visibility
  1. Public
  2. Protected

Type Members

  1. class TimeTypeApiOps extends TypeApiOps

    Client-side (spark-api) operations for TimeType.

    Client-side (spark-api) operations for TimeType.

    This class implements all TypeApiOps methods for the TIME data type:

    • String formatting: uses FractionTimeFormatter for consistent output
    • Row encoding: uses LocalTimeEncoder for java.time.LocalTime
    • Arrow conversion (ArrowUtils)
    • Python interop (EvaluatePython)
    • Hive formatting (HiveResult)
    • Thrift type mapping (SparkExecuteStatementOperation)

    RELATIONSHIP TO TimeTypeOps: TimeTypeOps (in catalyst package) extends this class to inherit client-side operations while adding server-side operations (physical type, literals, etc.).

    Since

    4.2.0

  2. trait TypeApiOps extends Serializable

    Client-side (spark-api) type operations for the Types Framework.

    Client-side (spark-api) type operations for the Types Framework.

    This trait consolidates all client-side operations that a data type must implement to be usable in the Spark SQL API layer. Mandatory methods (format, toSQLValue, getEncoder) must be implemented by every type. Optional methods (Arrow, Python, Hive, Thrift) return Option and default to None - types implement them as they expand their integration coverage.

    RELATIONSHIP TO TypeOps:

    • TypeOps (catalyst): Server-side operations - physical types, literals, conversions
    • TypeApiOps (spark-api): Client-side operations - formatting, encoding

    The split exists because sql/api cannot depend on sql/catalyst. For TimeType, TimeTypeOps (catalyst) extends TimeTypeApiOps (sql-api) to inherit both sets of operations.

    Since

    4.2.0

    See also

    TimeTypeApiOps for reference implementation

Value Members

  1. object TypeApiOps extends Serializable

    Factory object for creating TypeApiOps instances.

    Factory object for creating TypeApiOps instances.

    Returns Option to serve as both lookup and existence check - callers use getOrElse to fall through to legacy handling. The feature flag check is inside apply(), so callers don't need to check it separately.

Ungrouped