robert zych
12/03/2025, 11:23 PMExpression cycle problem when using an ingest transform function where the source field name matches the pinot column name? In my case I have geojson that has a geometry field containing coordinates ({"geometry": {"coordinates": [-82.41959120338983, 35.61020539194915]}} ). I'm looking for a way to convert those coordinates using toSphericalGeography(stPoint(lon, lat)) into a column also named geometry.robert zych
12/05/2025, 11:02 PMExpression cycle issue? If so, would this require significant effort to fix?Xiang Fu
"transformFunctions": {
"rawGeometry": "jsonPathString(geometry, '$.coordinates')",
"geometry": "toSphericalGeography(stPoint("
+ "jsonExtractScalar(rawGeometry, '$[0]', 'DOUBLE'), "
+ "jsonExtractScalar(rawGeometry, '$[1]', 'DOUBLE') ))"
}Xiang Fu
geometry in the pinot schemarobert zych
12/06/2025, 2:52 AMXiang Fu
geometry data type is different than the destination column: geometry typeXiang Fu
Xiang Fu
robert zych
12/06/2025, 2:58 AMrobert zych
12/06/2025, 2:59 AMXiang Fu
TransformPipeline to process those rowsrobert zych
12/12/2025, 8:22 PMExpressionTransformer.topologicalSort treats all function arguments as pinot columns that require circular dependency checking. What are your thoughts on allowing self-referencing (argument name matches pinot column name) when the functionEvaluator contains JSON and other similar functions? For example, geometry = toSphericalGeography(stPoint(JSONPATHDOUBLE(geometry, '$.coordinates[0]'), JSONPATHDOUBLE(geometry, '$.coordinates[1]')))Xiang Fu
robert zych
12/13/2025, 6:15 PM