You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "Shirshanka Das (Jira)" <ji...@apache.org> on 2020/09/26 23:52:00 UTC
[jira] [Created] (GOBBLIN-1273) Pull or Conf file loading failures
are not easy to understand
Shirshanka Das created GOBBLIN-1273:
---------------------------------------
Summary: Pull or Conf file loading failures are not easy to understand
Key: GOBBLIN-1273
URL: https://issues.apache.org/jira/browse/GOBBLIN-1273
Project: Apache Gobblin
Issue Type: Improvement
Reporter: Shirshanka Das
When config files fail to load (specifically hocon files), Gobblin doesn't log which file and which line number caused the failure.
e.g. if a .conf file with unquoted : characters is found in a standalone server's config directory, the startup aborts with the following message:
_Exception in thread "main" java.lang.IllegalStateException: Expected to be healthy after starting_
_at com.google.common.base.Preconditions.checkState(Preconditions.java:150)_
_at com.google.common.util.concurrent.ServiceManager.awaitHealthy(ServiceManager.java:278)_
_at org.apache.gobblin.runtime.app.ServiceBasedAppLauncher.start(ServiceBasedAppLauncher.java:168)_
_at org.apache.gobblin.scheduler.SchedulerDaemon.main(SchedulerDaemon.java:75)_
_Exception in thread "JobScheduler STARTING" com.typesafe.config.ConfigException$BadPath: Reader: 30: Token not allowed in path expression: ':' (you can double-quote this token if you really want it here)_
_at com.typesafe.config.impl.Parser.parsePathExpression(Parser.java:1095)_
_at com.typesafe.config.impl.Parser.parsePathExpression(Parser.java:1049)_
_at com.typesafe.config.impl.Parser.access$000(Parser.java:27)_
_..._
--
This message was sent by Atlassian Jira
(v8.3.4#803005)