Aatirhassanpir opened a new issue, #14886:
URL: https://github.com/apache/pinot/issues/14886
## Description
Summary: This feature request proposes the addition of support for the
TIMESTAMP and BOOLEAN data types within Apache Pinot. The new data types will
allow users to store and query TIMESTAMP (in LONG format, representing
milliseconds since epoch) and BOOLEAN (in INT format, with 0 for false and 1
for true) values. This change enhances the flexibility of the system by
accommodating common data types used in modern applications.
Motivation: Currently, Apache Pinot lacks native support for TIMESTAMP and
BOOLEAN data types, which are commonly used in time-series and event-based data
systems. This feature will provide a more robust and intuitive approach for
users who need to query and store time-related data (TIMESTAMP) and boolean
flags (BOOLEAN) within Pinot.
Detailed Changes:
TIMESTAMP Handling:
Internally stored as a LONG (milliseconds since epoch).
Can be ingested either as long values or JDBC timestamp formatted strings.
In query responses, TIMESTAMP values will follow the standard JDBC format
(e.g., 2021-01-01 01:01:01.123).
BOOLEAN Handling:
Internally stored as an INT (0 for false, 1 for true).
Can be ingested from boolean values, non-zero integers (for true), zero (for
false), or string representations ("true" for true, "false" for false).
Supported Operations:
The changes will allow TIMESTAMP and BOOLEAN data types to be used in
various query operations including data ingestion, filtering, selection,
distinct, order-by, aggregation, group-by, transformation, having, and
post-aggregation.
Schema and Documentation:
TIMESTAMP and BOOLEAN data types will be recognized as dimension/time fields
in the schema.
BOOLEAN will no longer be converted to STRING in the schema.
Updates will be made to the Apache Pinot documentation to reflect these new
data types.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
