We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, when a schema is generated from the Dataset, the field names are implicitly lowercased: https://github.com/tarantool/cartridge-spark/blob/master/src/main/scala/org/apache/spark/sql/tarantool/TarantoolSchema.scala#L32. That was done so because usually the queries have the field names uppercased and therefore not compatible with the schema in Tarantool. But if the schema in Tarantool has uppercase letters in the field names, there is the same problem.
Acceptance criteria:
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Currently, when a schema is generated from the Dataset, the field names are implicitly lowercased: https://github.com/tarantool/cartridge-spark/blob/master/src/main/scala/org/apache/spark/sql/tarantool/TarantoolSchema.scala#L32. That was done so because usually the queries have the field names uppercased and therefore not compatible with the schema in Tarantool. But if the schema in Tarantool has uppercase letters in the field names, there is the same problem.
Acceptance criteria:
The text was updated successfully, but these errors were encountered: