Elasticsearch + Oracle JDBC River

时间:2015-02-07 17:37:54

标签: oracle elasticsearch elasticsearch-jdbc-river

也许这是一个简单的问题,但我是ElasticSearch的新手。安装了es 1.4,Oracle 10g启动并运行,在ES中加载的jdbc插件没有问题。漫威也在工作..试图在Marvel / Sense中用这句话创造一条河流:


PUT _river/mydata/_meta 
{
  "type": "jdbc",
  "jdbc": {
        "driver": "oracle.jdbc.OracleDriver",
        "url": “jdbc:oracle:thin:@host:1521:SID",
        "user": “oracleusr",
        "password": “ oraclepass",
        "index": “myindex",
        "type": “mytype",
        "sql": "select * from aTable"
      }
}

我一直都会收到这个错误:

{
   "error": "MapperParsingException[failed to parse]; nested: ElasticsearchParseException[Failed to derive xcontent from (offset=0, length=323): [80, 85, 84, 32, 95, 114, 105, 118, 101, 114, 47, 109, 52, 99, 47, 95, 109, 101, 116, 97, 32, 10, 123, 10, 32, 32, 34, 116, 121, 112, 101, 34, 58, 32, 34, 106, 100, 98, 99, 34, 44, 10, 32, 32, 34, 106, 100, 98, 99, 34, 58, 32, 123, 10, 32, 32, 32, 32, 32, 32, 32, 32, 34, 100, 114, 105, 118, 101, 114, 34, 58, 32, 34, 111, 114, 97, 99, 108, 101, 46, 106, 100, 98, 99, 46, 79, 114, 97, 99, 108, 101, 68, 114, 105, 118, 101, 114, 34, 44, 10, 32, 32, 32, 32, 32, 32, 32, 32, 34, 117, 114, 108, 34, 58, 32, -30, -128, -100, 106, 100, 98, 99, 58, 111, 114, 97, 99, 108, 101, 58, 116, 104, 105, 110, 58, 64, 49, 48, 46, 49, 57, 52, 46, 49, 55, 46, 49, 55, 51, 58, 49, 53, 50, 49, 58, 109, 52, 99, 34, 44, 10, 32, 32, 32, 32, 32, 32, 32, 32, 34, 117, 115, 101, 114, 34, 58, 32, -30, -128, -100, 109, 52, 99, 34, 44, 10, 32, 32, 32, 32, 32, 32, 32, 32, 34, 112, 97, 115, 115, 119, 111, 114, 100, 34, 58, 32, -30, -128, -100, 32, 109, 52, 99, 49, 50, 48, 57, 48, 53, 34, 44, 10, 32, 32, 32, 32, 32, 32, 32, 32, 34, 105, 110, 100, 101, 120, 34, 58, 32, -30, -128, -100, 109, 52, 99, 34, 44, 10, 32, 32, 32, 32, 32, 32, 32, 32, 34, 116, 121, 112, 101, 34, 58, 32, -30, -128, -100, 112, 97, 105, 115, 34, 44, 10, 32, 32, 32, 32, 32, 32, 32, 32, 34, 115, 113, 108, 34, 58, 32, 34, 115, 101, 108, 101, 99, 116, 32, 42, 32, 102, 114, 111, 109, 32, 77, 52, 67, 80, 65, 73, 83, 34, 10, 32, 32, 32, 32, 32, 32, 125, 10, 125, 10]]; ",
   "status": 400
}
我在CLI上获得

    org.elasticsearch.index.mapper.MapperParsingException: failed to parse
    at org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:562)
    at org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:490)
    at org.elasticsearch.index.shard.service.InternalIndexShard.prepareIndex(InternalIndexShard.java:413)
    at org.elasticsearch.action.index.TransportIndexAction.shardOperationOnPrimary(TransportIndexAction.java:189)
    at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.performOnPrimary(TransportShardReplicationOperationAction.java:511)
    at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$1.run(TransportShardReplicationOperationAction.java:419)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
Caused by: org.elasticsearch.ElasticsearchParseException: Failed to derive xcontent from (offset=0, length=323)

我首先是一个连接问题但是检查它似乎是ES&中映射的一个问题。甲骨文。有人做过ES + Oracle River集成吗?任何帮助都会非常感激。

1 个答案:

答案 0 :(得分:4)

我找到了一个非常好的解决方案。而不是把命令放在我所做的是有一个像这样的json配置文件:

{
    "type" : "jdbc" ,
    "jdbc" :{
        "strategy" : "oneshot",
        "driver" : "oracle.jdbc.OracleDriver",
        "url" : "jdbc:oracle:thin:@host:1521:DNS",
        "user" : "user",
        "password" : "password",
        "sql" : "select * from aTable",
        "poll" : "1h",
        "scale" : 0,
        "autocommit" : false,
        "fetchsize" : 100,
        "max_rows" : 0,
        "max_retries" : 3,
        "max_retries_wait" : "10s"
    },
    "index" : {
        "index" : "aIndex",
        "type" : "aType",
        "bulk_size" : 100
    }
}

然后用curl调用它:

'http://127.0.0.1:9200/_river/jdbcriver/_meta' -d @config.json

我不知道这是一个解析器问题,但是这种方式就像魅力一样。

由于