[jira] [Assigned] (STORM-1448) How to return objects in declare output fields

["Jayasree (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/STORM-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jayasree reassigned STORM-1448:
-------------------------------

    Assignee: Parth Brahmbhatt

> How to return objects in declare output fields
> ----------------------------------------------
>
>                 Key: STORM-1448
>                 URL: https://issues.apache.org/jira/browse/STORM-1448
>             Project: Apache Storm
>          Issue Type: Bug
>         Environment: Linux OS, Storm , Kafka
>            Reporter: Jayasree
>            Assignee: Parth Brahmbhatt
>
> I was working on twitter data using kafka-storm. I was using deserialize method to parse the twitter data using storm spout , here in parser I was facing a problem of returning all the objects. What I have done is I added them in a list and returned the list. Up to that it's working fine but, while coming to getOutputFields() it showing runtime error i.e., 
> ERROR : java.lang.IllegalArgumentException: Tuple created with wrong number of fields. Expected 6 fields but got 140 fields at backtype.storm.tuple.TupleImpl.<init>(TupleImpl.java:58) at backtype.storm.daemon.executor$fn_5624$fn5639$send_spout_msg5658.invoke(executor.clj:529) at backtype.storm.daemon.executor$fn5624$fn$reify5668.emit(executor.clj:568) at backtype.storm.spout.SpoutOutputCollector.emit(SpoutOutputCollector.java:49) at backtype.storm.spout.SpoutOutputCollector.emit(SpoutOutputCollector.java:63) at storm.kafka.PartitionManager.next(PartitionManager.java:141) at storm.kafka.KafkaSpout.nextTuple(KafkaSpout.java:141) at backtype.storm.daemon.executor$fn5624$fn5639$fn5670.invoke(executor.clj:607) at backtype.storm.util$async_loop$fn_545.invoke(util.clj:479) at clojure.lang.AFn.run(AFn.java:22) at java.lang.Thread.run(Thread.java:745) 
> I was returning 6 objects but it showing that its getting 60 fields . How to solve that ? Can anyone suggest me the solution ?



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