[
https://issues.apache.org/jira/browse/HIVE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732112#action_12732112
]
Edward Capriolo commented on HIVE-425:
--------------------------------------
Alex,
Here are the current problems I see.
* JSP
** Hard To check Syntax at Compile Time
** References to other parts of hive (not many but) may become outdated with
API changes
* Hard to unit test Are unit test tests the SessionManager, not the actual jsp
flow of passing form items.
So the ideal framework would be:
* small <5MB. we dont want to make Hive bigger just better
* mostly .Java and servlet based (little/no JSP)
* Possibly a way to unit test a transaction. Login->RunQuery->Verify Results
* Apache compat license
* XML/CSS (if it helps eliminate JSP)
* Low complexity (I am not interested in learning what a
org.springframework.transaction.interceptor.AbstractFallbackTransactionAttributeSource
) is for example :)
I know little about JSP Frameworks. Do you you have one that fits the needs?
> HWI JSP pages should be compiled at build-time instead of run-time
> ------------------------------------------------------------------
>
> Key: HIVE-425
> URL: https://issues.apache.org/jira/browse/HIVE-425
> Project: Hadoop Hive
> Issue Type: Improvement
> Components: Web UI
> Reporter: Alex Loddengaard
>
> HWI JSP pages are compiled via the ant jar at run-time. Doing so at run-time
> requires ant as a dependency and also makes developing slightly more tricky,
> as compiler errors are not discovered until HWI is deployed and running. HWI
> should be instrumented in such a way where the JSP pages are compiled by ant
> at build-time instead, just as the Hadoop status pages are.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
