You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Sean Hsuan-Yi Chu (JIRA)" <ji...@apache.org> on 2014/11/23 00:03:12 UTC

[jira] [Commented] (DRILL-1683) malformed config file parse exception silently swallowed - drill fails to start

    [ https://issues.apache.org/jira/browse/DRILL-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222241#comment-14222241 ] 

Sean Hsuan-Yi Chu commented on DRILL-1683:
------------------------------------------

The file "/tmp/drill/sys.storage_plugins/hbase.sys.drill" is the storage plugin which one can modify in the Web-UI. (In the case of embedded mode, http://localhost:8047/storage/hbase).

Maybe the error in this issue is specific to Eclipse? Can you check again if it would still go wrong?

> malformed config file parse exception silently swallowed - drill fails to start
> -------------------------------------------------------------------------------
>
>                 Key: DRILL-1683
>                 URL: https://issues.apache.org/jira/browse/DRILL-1683
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - CLI
>         Environment: Running drill in embedded mode via sqlline on OSX under eclipse.
>            Reporter: Chris Westin
>            Assignee: Sean Hsuan-Yi Chu
>             Fix For: 0.7.0
>
>
> For unknown reasons, the file /tmp/drill/sys.storage_plugins/hbase.sys.drill contains
> {
>   "type" : "hbase",
>   "config" : {
>     "hbase.zookeeper.quorum" : "localhost",
>     "hbase.zookeeper.property.clientPort" : "2181"
>   },
>   "size.calculator.enabled" : false,
>   "enabled" : false
> }
> This causes a JsonMappingException with
> Could not resolve type id 'hbase' into a subtype of [simple type, class org.apache.drill.common.logical.StoragePluginConfig]
> at
> AsPropertyTypeDeserializer(TypeDeserializerBase)._findDeserializer(DeserializationContext, String) line: 155	
> AsPropertyTypeDeserializer._deserializeTypedForId(JsonParser, DeserializationContext, TokenBuffer) line: 98	
> AsPropertyTypeDeserializer.deserializeTypedFromObject(JsonParser, DeserializationContext) line: 82	
> AbstractDeserializer.deserializeWithType(JsonParser, DeserializationContext, TypeDeserializer) line: 107	
> TypeWrappedDeserializer.deserialize(JsonParser, DeserializationContext) line: 36	
> ObjectReader._bindAndClose(JsonParser, Object) line: 1206	
> ObjectReader.readValue(byte[]) line: 836	
> JacksonSerializer<X>.deserialize(byte[]) line: 44	
> LocalPStore<V>.get(String, boolean) line: 99	
> LocalPStore<V>.get(String) line: 89	
> LocalPStore$Iter$DeferredEntry.getValue() line: 197	
> StoragePluginRegistry.createPlugins() line: 166	
> StoragePluginRegistry.init() line: 130	
> Drillbit.run() line: 148	
> DrillJdbc41Factory$DrillJdbc41Connection(DrillConnectionImpl).<init>(Driver, AvaticaFactory, String, Properties) line: 79	
> DrillJdbc41Factory$DrillJdbc41Connection.<init>(Driver, DrillFactory, String, Properties) line: 88	
> DrillJdbc41Factory.newDrillConnection(Driver, DrillFactory, String, Properties) line: 57	
> DrillJdbc41Factory.newDrillConnection(Driver, DrillFactory, String, Properties) line: 43	
> DrillJdbc41Factory(DrillFactory).newConnection(UnregisteredDriver, AvaticaFactory, String, Properties) line: 51	
> Driver(UnregisteredDriver).connect(String, Properties) line: 126	
> SqlLine$DatabaseConnection.connect() line: 4732	
> If I remove that file, I am then able to start the embedded drillbit. I note that after I do so, the file has been recreated with different contents. If the problem is because the configuration for this storage plugin has changed, then this seems like it will cause many mysterious startup failures after upgrading.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)