trinodb/trino

Trino version master Please describe the bug We can reproduce this issue by starting io.trino.cli.Trino#main with -Duser.language=ar -Duser.country=EG VM options: trino> SELECT 1; trino> Invalid server URL: http://localhost:٨٠٨٠ This error can be resolved by updating the TrinoUri.getHttpUri method. However, the result still has a formatting issue. trino> SELECT 1; _col0 ------- 1 (1 row) Query 20261008_114335_00028_qcibj, FINISHED, ١ node Splits: ١ total, ١ done (١٠٠٫٠٠%) 0.02 [0 rows, 0B] [0 rows/s, 0B/s]

Feature Request / Improvement Description Currently, geometry-type fields coming from Oracle are not properly handled by Trino. By default, when describing a table, geometry columns are ignored. When applying the configuration: unsupported-type-handling=CONVERT_TO_VARCHAR the column is converted to VARCHAR, but it is still not queryable and leads to an internal error: TrinoQueryError( type=INTERNAL_ERROR, name=GENERIC_INTERNAL_ERROR, message="oracle/xdb/XMLType", query_id=20260623_074232_00028_a7gb2 ) Expected behavior It would be very helpful to support a default (and configurable) conversion mechanism for Oracle geometry types, for example: Conversion to an Oracle CLOB (via WKT/WKB/KML functions) Or direct mapping to a Trino GEOMETRY / geospatial type if possible Example In Oracle, geometry fields can be converted using the following functions: SELECT MY_GEOMETRY, SDO_UTIL.TO_WKTGEOMETRY(MY_GEOMETRY) AS geometry_wkt, SDO_UTIL.TO_WKBGEOMETRY(MY_GEOMETRY) AS geom

We can return metrics such as rewritten data files, removed deletion vectors, added data files in Delta Lake OPTIMIZE procedure. trino/plugin/trino-delta-lake/src/main/java/io/trino/plugin/deltalake/DeltaLakeMetadata.java Lines 2940 to 2950 in 11bf3c0 @Override public Map<String, Long> finishTableExecute(ConnectorSession session, ConnectorTableExecuteHandle tableExecuteHandle, Collection<Slice> fragments, List<Object> splitSourceInfo) { DeltaLakeTableExecuteHandle executeHandle = (DeltaLakeTableExecuteHandle) tableExecuteHandle; switch (executeHandle.procedureId()) { case OPTIMIZE: finishOptimize(session, executeHandle,

EnvMultinodeCassandra and default CassandraServer use Cassandra v3. We should update them to v4 since v3 already reached EOL. This task requires updating cu-cassandra.yaml in test/resources directory, also "Requirements" section in cassandra.md.

Description When Trino attempts to write a Delta Lake checkpoint for a table containing DECIMAL columns, it may fail with a java.lang.ClassCastException: class java.lang.Double cannot be cast to class java.lang.String. This occurs when the preceding transaction logs (.json files) were authored by Spark, which sometimes serializes DECIMAL statistics as JSON Numbers (e.g., 36.17) rather than JSON Strings (e.g., "36.17"). Trino's CheckpointWriter strictly expects these values to be Strings during the parsing phase. Steps to Reproduce Create a Delta table using Spark SQL with a DECIMAL column. CREATE TABLE delta_part_for_insert ( order_id BIGINT, customer_id BIGINT, order_amount DECIMAL(10, 2), order_ts TIMESTAMP ) USING delta PARTITIONED BY (order_ts); Insert data into the table using Spark. Spark may write the stats field in the JSON commit file as follows: "stats": "{\"numRecords\":1,\"minValues\":{\"amount\":36.17},\"maxValues\":{\"amount\":36.17},...}" Note: 36.17 is a