> On Dec. 15, 2015, 6:53 a.m., PRAGYA MITTAL wrote:
> > docs/src/site/twiki/FalconNativeScheduler.twiki, line 76
> > <https://reviews.apache.org/r/41342/diff/2/?file=1164445#file1164445line76>
> >
> >     In distributed mode, how can multiple servers share same derby db ? Any 
> > configuration required for it.

Not applicable for Derby DB.. clarified that.


> On Dec. 15, 2015, 6:53 a.m., PRAGYA MITTAL wrote:
> > docs/src/site/twiki/FalconNativeScheduler.twiki, line 81
> > <https://reviews.apache.org/r/41342/diff/2/?file=1164445#file1164445line81>
> >
> >     How to run this command in distributed mode (we can mention via server 
> > it has to be run)

Clarified that only Falcon server needs to maintain state and the script needs 
to be run for Falcon server installation alone.


> On Dec. 15, 2015, 6:53 a.m., PRAGYA MITTAL wrote:
> > docs/src/site/twiki/FalconNativeScheduler.twiki, line 102
> > <https://reviews.apache.org/r/41342/diff/2/?file=1164445#file1164445line102>
> >
> >     Can we add any other db that we plan to support in future.

Mentioned that we may extend support to other DBs.


> On Dec. 15, 2015, 6:53 a.m., PRAGYA MITTAL wrote:
> > docs/src/site/twiki/FalconNativeScheduler.twiki, line 110
> > <https://reviews.apache.org/r/41342/diff/2/?file=1164445#file1164445line110>
> >
> >     Is falcon dependent on a specific version of mysql ?

I can mention the version it has been tested against. It should work with any 
version above that too.


> On Dec. 15, 2015, 6:53 a.m., PRAGYA MITTAL wrote:
> > docs/src/site/twiki/FalconNativeScheduler.twiki, line 112
> > <https://reviews.apache.org/r/41342/diff/2/?file=1164445#file1164445line112>
> >
> >     falcon.statestore.jdbc.driver in case of mysql ?

jdbc.url is the only property that needs to be changed. Have called it out.


> On Dec. 15, 2015, 6:53 a.m., PRAGYA MITTAL wrote:
> > docs/src/site/twiki/FalconNativeScheduler.twiki, line 113
> > <https://reviews.apache.org/r/41342/diff/2/?file=1164445#file1164445line113>
> >
> >     *.falcon.statestore.jdbc.username=sa
> >     *.falcon.statestore.jdbc.password=
> >     
> > *.falcon.statestore.connection.data.source=org.apache.commons.dbcp.BasicDataSource
> >  
> >     
> >     Does these property remain same for both mysql and derby ?

Yes. Have called it out.


> On Dec. 15, 2015, 6:53 a.m., PRAGYA MITTAL wrote:
> > docs/src/site/twiki/FalconNativeScheduler.twiki, line 114
> > <https://reviews.apache.org/r/41342/diff/2/?file=1164445#file1164445line114>
> >
> >     Can multiple servers use same mysql db?

Yes. Mentioned the same in the doc.


> On Dec. 15, 2015, 6:53 a.m., PRAGYA MITTAL wrote:
> > docs/src/site/twiki/FalconNativeScheduler.twiki, line 116
> > <https://reviews.apache.org/r/41342/diff/2/?file=1164445#file1164445line116>
> >
> >     Does user need to create 'statestore' db prior to running the script. 
> > If so , can root user do it or it has to a specific user ?

For MySQL yes.. For derby, not necessary. Updated the doc.


> On Dec. 15, 2015, 6:53 a.m., PRAGYA MITTAL wrote:
> > docs/src/site/twiki/FalconNativeScheduler.twiki, line 117
> > <https://reviews.apache.org/r/41342/diff/2/?file=1164445#file1164445line117>
> >
> >     Is mysql-connector.jar bundled in falcon or user needs to copy it. If 
> > user has to copy then where should we copy ?

Nope. Absence of documentation means the user does not need to do anything :-).


> On Dec. 15, 2015, 6:53 a.m., PRAGYA MITTAL wrote:
> > docs/src/site/twiki/FalconNativeScheduler.twiki, line 137
> > <https://reviews.apache.org/r/41342/diff/2/?file=1164445#file1164445line137>
> >
> >     Does migration require engine change in startup.properties ?

Apart from enabling native scheduler nothing else. Called it out explicitly.


> On Dec. 15, 2015, 6:53 a.m., PRAGYA MITTAL wrote:
> > docs/src/site/twiki/FalconNativeScheduler.twiki, line 48
> > <https://reviews.apache.org/r/41342/diff/2/?file=1164445#file1164445line48>
> >
> >     Does it mean we dont need OozieWorkflowEngine in the long run.
> >     If user wants to schedule some job via oozie and then some via 
> > scheduler, will this work even without changing engine in 
> > startup.properties .
> >     
> >     Can we be more clear on property dependency on engine (if any)

Have tried to word this a little more clearly.


> On Dec. 15, 2015, 6:53 a.m., PRAGYA MITTAL wrote:
> > docs/src/site/twiki/falconcli/Schedule.twiki, line 16
> > <https://reviews.apache.org/r/41342/diff/2/?file=1164446#file1164446line16>
> >
> >     
> > *.workflow.engine.impl=org.apache.falcon.workflow.engine.OozieWorkflowEngine
> >  and user gives this property, what is the expected behaviour. Is this 
> > property dependent of the engine defined in startup.properties.

Details have been added to FalconNativeScheduler page.


- Pallavi


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41342/#review110433
-----------------------------------------------------------


On Dec. 15, 2015, 5:27 a.m., Pallavi Rao wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41342/
> -----------------------------------------------------------
> 
> (Updated Dec. 15, 2015, 5:27 a.m.)
> 
> 
> Review request for Falcon and PRAGYA MITTAL.
> 
> 
> Bugs: FALCON-1652
>     https://issues.apache.org/jira/browse/FALCON-1652
> 
> 
> Repository: falcon-git
> 
> 
> Description
> -------
> 
> Documentation for enabling native scheduler in falcon
> 
> 
> Diffs
> -----
> 
>   docs/src/site/twiki/Configuration.twiki 74da49a 
>   docs/src/site/twiki/FalconDocumentation.twiki f384a42 
>   docs/src/site/twiki/FalconNativeScheduler.twiki PRE-CREATION 
>   docs/src/site/twiki/falconcli/Schedule.twiki 63aa9c1 
>   src/conf/startup.properties 1694930 
> 
> Diff: https://reviews.apache.org/r/41342/diff/
> 
> 
> Testing
> -------
> 
> Compiled and ensured the html shows up properly on the browser.
> 
> 
> Thanks,
> 
> Pallavi Rao
> 
>

Reply via email to