Develop a RESTful API for a Front End

[#1]

Hi all,

I'd like to develop a front end to run various algorithms I developed and visualise results. I need my Front End to be personalised that's why I didn't use Hue. To achieve this I thought about developing a RESTful API using Java Jersey and Hive JDBC to be called from AngularJS.

Is this a good choice ? or I've other alternatives (suggestions are welcome)?

Does Hive JDBC support concurrency and simultaneous queries ?

[#2 · Accepted solution]

You can use your own frontend using angular or whatever you want ( Dojo has some nice charts )

https://www.sitepen.com/blog/2008/06/06/a-beginners-guide-to-dojo-charting-part-1-of-2/

However if you need only a lower level of flexibility you could use BIRT

http://www.eclipse.org/birt/

or pentaho or other reporting tools. That would be easier and BIRT for example provides pretty flexible report creation capabilities.

( It breaks down when you want a hugely interactive frontend. )

[#3]

@Benjamin Leonhardi Thank you for your answer, Do you have an idea about the best way to access the cluster (hdfs, Hbase, ...) and retrieve data easily ?

[#4]

Depends what you plan to do.

- Aggregation queries and analytical reports then Hive ( simple jdbc connection is supported by BIRT and Pentaho and you can also make servlets with jdbc pools the whole shebang )

- Selecting one record at a time ( like a dashboard that shows the data of one customer

Hbase with REST api from javascript might work

Hbase with java api from a servlet

if you prefer SQL Apache Phoenix is a cool SQL layer on top of HBase

https://phoenix.apache.org/

- Interactive reports on thousands to millions of records ( not billions )

Apache Phoenix, it provides some good enhancements on base HBase from a performance perspective for anything that touches more than a row. You can also do Joins aggregations etc. pp.

( If you want HBase but have kerberos setup have a look at Knox its a SSL capable proxy that strips away the Kerberos requirement and replaces it with a normal web authentication setting for the hbase API )