Mailing-List: contact dev-help@streams.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@streams.incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of robert.baker.douglas@gmail.com
 designates 209.85.192.68 as permitted sender)
MIME-Version: 1.0
Date: Mon, 30 Jun 2014 11:50:59 -0500
Message-ID: 
 <CAHFTPLS7-GQBWVV=2fWrMV+kYEtuHD6q8WcJoFt=MmWYPOaw2w@mail.gmail.com>
Subject: Desired behavior for DataSift user_mention serialization
From: Robert Douglas <robert.baker.douglas@gmail.com>
To: dev@streams.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a11c2bac4b5ed0f04fd1076b5

--001a11c2bac4b5ed0f04fd1076b5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi all,

I=E2=80=99m currently working on cleaning up the implementation of the Data=
Sift
serializer and have come upon an issue. The data that we get back in a
DataSift Interaction object contains two fields, mentions (which has all
the handles for mentioned users) and mention_ids (which has all the Ids for
mentioned users). Problem is, there is no guarantee that these two lists
will be the same size. My current solution is to merge together the handles
and Ids into individual UserMention objects whenever the mentions and
mention_ids lists are the same size. In the event that those lists are not
the same size, I create UserMention objects for every entry in both lists.

Does anyone have an different opinion on how this should be handled?

=E2=80=94 Robert

--001a11c2bac4b5ed0f04fd1076b5--