# Redis -\> LS -\> ES WRONGTYPE Operation against a key holding the wrong kind of value

**URL:** <https://discuss.elastic.co/t/redis-ls-es-wrongtype-operation-against-a-key-holding-the-wrong-kind-of-value/109255>\
**Category:** Logstash\
**Created:** [November 27, 2017, 5:15pm UTC](https://discuss.elastic.co/t/redis-ls-es-wrongtype-operation-against-a-key-holding-the-wrong-kind-of-value/109255 "2017-11-27T17:15:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dseixas](https://avatars.discourse-cdn.com/v4/letter/d/ba8739/32.png) [@dseixas](https://discuss.elastic.co/u/dseixas)\
**Post date:** [November 27, 2017, 5:15pm UTC](https://discuss.elastic.co/t/redis-ls-es-wrongtype-operation-against-a-key-holding-the-wrong-kind-of-value/109255/1 "2017-11-27T17:15:43Z")

</div>

Hi,

We're trying to use the combo Redis+LS+ES to try to persist xAPI statements (these statements are JSON strings).

So far, we write correctly in redis, but when LS try to do its thing we get this message:  
WRONGTYPE Operation against a key holding the wrong kind of value

A simple example of what we're writing in Redis is:

set xapi '{"id":"jghfj"}' EX 10

My logstash config file is:

> ```
> input {
> redis {
> host => "127.0.0.1"
> data_type => "list"
> key => "xapi"
> # codec => "json"
> # batch_count => 1
> # threads => 1
> }
> }
> 
> output {
> elasticsearch {
> hosts => ["localhost:9200"]
> index => "xapi"
> }
> stdout {
> codec => rubydebug
> }
> }
> 
> ```

We're out of ideas how to get this thing working. Any help is welcome.

BR  
Daniel

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 25, 2017, 5:15pm UTC](https://discuss.elastic.co/t/redis-ls-es-wrongtype-operation-against-a-key-holding-the-wrong-kind-of-value/109255/2 "2017-12-25T17:15:44Z")

</div>

Closed on December 25, 2017, 5:15pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.