Github user mgaido91 commented on the issue:

    https://github.com/apache/spark/pull/20594
  
    @WeichenXu123 @viirya as I said in the other PR, I think no default value 
should be persisted. #20410 and #18982 are not regression: they are problem 
which have been present in all the release so far, but they are showing up more 
and more "thanks" to all the models having the dualism inputCol/inputCols.
    
    Every usage of `isSet`on Scala side is a problem with the Python API until 
either one of them will be merged. And this issue is the same. After 
persisting, every usage of `isSet` is not working as intended. Therefore I'd be 
for either not to store any default value or store them writing explicitly that 
they are default values. 


---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to