1. Would table with geospatial location column be allowed to be updated with non-geospatial data and vice verca . Or would it according to the existing behavior and any unsupported data in type/column would be treated as bad records ? => Location columns cannot be allowed with invalid datatypes. It can be treated as bad records with unsupported data in type/column.
2. Would there be any limitations with respect to using targetColumn column configured as local dictionary,inverted index,cache column or range column in table properties ? => I think, there shouldn't be any such restriction. TargetColumn is just an additional column internally generated when INDEX property is specified. 3. Would only measure data types be supported for targetDataType parameter ? Supported types can be mentioned in design doc. => We can treat the generated geohash column as dimension column as it should be part of sort columns. -- Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
