Details
-
Type:
Task
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 0.3
-
Fix Version/s: None
-
Component/s: Docs
-
Labels:None
Description
per der discussion in LIVY-158
re: documentation, I'm fine with writing better documentation. Some basic configs + a link to Spark's documentation is fine. I just don't want to get into the business of replicating half of Spark's documentation in Livy, just like I don't want to replicate Spark's functionality in this area.
CLI args provided by spark-submit are very frequently used during job submission, and could be used as a reference to determine whenever a config is essential.