Github user benoyantony commented on the issue:

    https://github.com/apache/zeppelin/pull/1623
  
    thanks @1ambda , Sorry for the delay.
    
    1. If this feature is merged, then the properties can be referred in the 
interpreter properties. Each user can override the property value.
    
    2. Once the feature is merged, I will have another pull request on the Livy 
Interpreter which make use of the feature for its properties. 
    
    I have tested this feature at our company.  Attached is screenshot where 
the administrator setup the Livy property - livy.spark.yarn.queue to 
${queue,defaultQueue}
    
    
![livy-interpreter-properties](https://cloud.githubusercontent.com/assets/1928906/20405416/c9c1b968-acbd-11e6-8306-6b398445ad94.png)
    
    
    In the second screenshot, the  user override the queue as benoyqueue. If 
the user does not override, then the property will remain as defaultQueue.
     
    
![user-defined-properties](https://cloud.githubusercontent.com/assets/1928906/20405423/d28122d2-acbd-11e6-8b91-d58de2497148.png)



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to