TheBuilderJR opened a new issue, #13649:
URL: https://github.com/apache/datafusion/issues/13649

   ### Describe the bug
   
   If I run the following query
   
   ```
   SELECT userId FROM telemetry_user_events LIMIT 10;
   ```
   
   against a table with the following schema
   ```
   
   New Query
   {
       "fields": [
           {
               "name": "event",
               "data_type": "Utf8",
               "nullable": true,
               "dict_id": 0,
               "dict_is_ordered": false,
               "metadata": {}
           },
           {
               "name": "prompt",
               "data_type": "Utf8",
               "nullable": true,
               "dict_id": 0,
               "dict_is_ordered": false,
               "metadata": {}
           },
           {
               "name": "timestamp",
               "data_type": "Utf8",
               "nullable": true,
               "dict_id": 0,
               "dict_is_ordered": false,
               "metadata": {}
           },
           {
               "name": "timestamp_utc",
               "data_type": {
                   "Timestamp": [
                       "Millisecond",
                       "UTC"
                   ]
               },
               "nullable": true,
               "dict_id": 0,
               "dict_is_ordered": false,
               "metadata": {}
           },
           {
               "name": "teamId",
               "data_type": "Utf8",
               "nullable": true,
               "dict_id": 0,
               "dict_is_ordered": false,
               "metadata": {}
           },
           {
               "name": "userId",
               "data_type": "Utf8",
               "nullable": true,
               "dict_id": 0,
               "dict_is_ordered": false,
               "metadata": {}
           },
           {
               "name": "query",
               "data_type": "Utf8",
               "nullable": true,
               "dict_id": 0,
               "dict_is_ordered": false,
               "metadata": {}
           }
       ],
       "metadata": {}
   }
   ```
   
   I get the following error
   ```
   Schema error: No field named userid. Valid fields are 
telemetry_user_events.event, telemetry_user_events.prompt, 
telemetry_user_events.timestamp, telemetry_user_events.timestamp_utc, 
telemetry_user_events.\"teamId\", telemetry_user_events.\"userId\", 
telemetry_user_events.query.\n 1: No field named userid. Valid fields are 
telemetry_user_events.event, telemetry_user_events.prompt, 
telemetry_user_events.timestamp, telemetry_user_events.timestamp_utc, 
telemetry_user_events.\"teamId\", telemetry_user_events.\"userId\", 
telemetry_user_events.query.
   ```
   
   However if I wrap userId in quotes like so
   ```
   SELECT "userId" FROM telemetry_user_events LIMIT 10;
   ```
   
   there are no errors. but this seems unideal! all other sql query engines I 
know handle camelcase gracefully
   
   
   ### To Reproduce
   
   Included in the above
   
   ### Expected behavior
   
   no errors if i select a camelcase column without wrapping in quotes
   
   ### Additional context
   
   _No response_


-- 
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]

Reply via email to