UI unable to detect catalog or schema or table! about yanagishima HOT 5 CLOSED

yanagishima.properties seems wrong.

The following setting seems correct.

presto.datasources=datalake
presto.coordinator.server.datalake=http://ip-172-31-16-250.ec2.internal:8889

But, the following error means presto.coordinator.server.datalake is nothing.
Is presto.coordinator.server.datalake really set? please check yanagishima.properties it out again.

java.util.NoSuchElementException: No value present
at java.util.Optional.get(Optional.java:135)
at yanagishima.config.YanagishimaConfig.getPrestoCoordinatorServer(YanagishimaConfig.java:17)

from yanagishima.

Here's what I understood about the properties file:

presto.datasources=datalake

This is to allocate a name to the datasource. This can be any name, it could also have been called foo!! Doesn't matter, as long as we continue to use this datasource name subsequently?! Am I right? I just randomly called it datalake!

Here's a line from presto config.properties file:
discovery.uri=http://ip-172-31-16-250.ec2.internal:8889

So, this is the hostname:port where presto server is running locally (on same host).

But, I don't understand what you mean by Is presto.coordinator.server.datalake really set???

Here's the output when I check what is running on port 8889:

[hadoop@ip-172-31-16-250 ~]$ sudo ss -lptn 'sport = :8889'
State       Recv-Q Send-Q             Local Address:Port                            Peer Address:Port
LISTEN      0      4096                          :::8889                                      :::*                   users:(("presto-server",pid=1798,fd=197))

from yanagishima.

You are right.

datasource name can be any name.

But, if presto.coordinator.server.datalake is not set, exception can be thrown.

https://github.com/wyukawa/yanagishima/blob/master/src/main/java/yanagishima/config/YanagishimaConfig.java#L17

So, presto.coordinator.server.datalake seems not to be set.

from yanagishima.

But, it is set in the properties file!!! Point is ... why is the code unable to read it?! I'm not saying it is your fault ... but it is not clear why?! As you can see, this property should make it through:

presto.coordinator.server.datalake=http://ip-172-31-16-250.ec2.internal:8889

but it doesn't!!!

from yanagishima.

OK. Found out the problem :)

I had to modify the security groups of my EMR Master to allow port 8889 (presto coordinator url)... see attached screenshot!

Sorry about that ... and thanks!

from yanagishima.