Github user sylvinho81 commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/60#issuecomment-99417733
  
    Hi @1teed,
    
    I am trying to apply this patch and test it, because I think is really 
interesting and I need it. 
    After apply the changes and run:
    mvn clean package
    mvn install -DskipTests -Dspark.version=1.1.1 -Dhadoop.version=1.2.1
    
    I can see:
    
    [INFO] 
------------------------------------------------------------------------
    [INFO] Reactor Summary:
    [INFO] 
    [INFO] Zeppelin ........................................... SUCCESS [  
3.472 s]
    [INFO] Zeppelin: Interpreter .............................. SUCCESS [  
9.269 s]
    [INFO] Zeppelin: Zengine .................................. SUCCESS [  
3.835 s]
    [INFO] Zeppelin: Spark .................................... SUCCESS [ 
23.308 s]
    [INFO] Zeppelin: Markdown interpreter ..................... SUCCESS [  
2.025 s]
    [INFO] Zeppelin: Angular interpreter ...................... SUCCESS [  
1.958 s]
    [INFO] Zeppelin: Shell interpreter ........................ SUCCESS [  
1.993 s]
    [INFO] Zeppelin: Hive interpreter ......................... SUCCESS [  
2.094 s]
    [INFO] Zeppelin: Tajo interpreter ......................... SUCCESS [  
1.971 s]
    [INFO] Zeppelin: JDBC interpreter ......................... SUCCESS [  
1.922 s]
    [INFO] Zeppelin: web Application .......................... SUCCESS [ 
45.557 s]
    [INFO] Zeppelin: Server ................................... SUCCESS [  
4.682 s]
    [INFO] Zeppelin: Packaging distribution ................... SUCCESS [  
0.439 s]
    
    But when I execute "bin/zeppelin-daemon.sh  start" and try to add the 
interpreter in  http://localhost:8080/ I can not see the option "jdbc" in the 
dropdown "Interpreter".
    



---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to