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
moving fast is awesome. crashing at lightspeed is not.
mergeSchema: true
(spark.read.table(...) .withColumnRenamed("x", "y") .write .mode("overwrite") .option("overwriteSchema", "true") .saveAsTable(...) )
not a terrible problem - just a new name - same content
(spark.read.table(...) .withColumn('x', date(col('x')) .write .mode('overwrite') .mode('overwriteSchema', 'true') .saveAsTable(...) )
this is bad. this is very bad. We not only just lost precision, but we'll have type conflicts for our streaming applications (active downstream)....
The text was updated successfully, but these errors were encountered:
newfront
No branches or pull requests
moving fast is awesome. crashing at lightspeed is not.
mergeSchema: true
only prevents type changes - while `overwriteSchemanot a terrible problem - just a new name - same content
(spark.read.table(...)
.withColumn('x', date(col('x'))
.write
.mode('overwrite')
.mode('overwriteSchema', 'true')
.saveAsTable(...)
)
this is bad. this is very bad. We not only just lost precision, but we'll have type conflicts for our streaming applications (active downstream)....
The text was updated successfully, but these errors were encountered: