Hi Ganesh,
I'm trying to understand what steps you exactly did.
From your description I see you have an EMR cluster and on one node you've probably setup a web server with rdf4j-server and rdf4j-workbench web applications.
However you also mention "create hbase", which is a console command.
Rdf4j as well as Halyard consist of several layers.
Rdf4j rest API is a part of rdf4j-server web application, it is managed through rdf4j-workbench and it must be deployed in an application web server (Tomcat deployment is described in the documentation).
If you need SPARQL endpoint rest api to access particular dataset, you can rely on particular repository within the rd4j-server (created using rdf4j-workbench). Or alternatively (as a very new and experimental Halyard feature) you can run Halyard Endpoint to query-only one specific dataset through SPARQL query rest api.
If you need just access the data using SPARQL queries and SPARQL updates, you can do it using rdf4j-workbench, or through rest calls to rdf4j-server, or rest calls to Halyard Endpoint (query only), or from rd4j console, or by using Halyard command-line tools.
However rdf4-console does not setup any rest server, it has just embedded Halyard layer and embedded rdf4j framework and direct access to the data in HBase. Also please notice the difference between datasets and repositories paragraph in Halyard documentation. Rdf4j repositories are meta-descriptors individually locally configured in each server or console instance, however datasets are backed by Hbase tables and they exist across the whole cluster globally.
I hope this helped to better understand the architecture.
Thanks,
Adam
-------- Původní zpráva --------
Datum: 26.03.19 6:14 (GMT+01:00)
Předmět: Using halyard with rest api