I have much appreciated the help received thus far from this
community.
It seems that Aggregate (0.96) is replicating records repeatedly to
Google Fusion Tables, even though only a single record appears in
Aggregate. For example, just now I submitted a single record
successfully on the first attempt to Aggregate, and it appears there
once. But in Fusion Tables, it appears three times (!). My prior try
appeared once in Aggregate, and twice in Fusion Tables. What is going
on?
Strange - this no longer seems to be happening with newer records.
So, it is a random behavior, and I do not know what triggers it.
Best,
David
···
On Apr 11, 4:39 pm, David wrote:
> Dear all,
>
> I have much appreciated the help received thus far from this
> community.
>
> It seems that Aggregate (0.96) is replicating records repeatedly to
> Google Fusion Tables, even though only a single record appears in
> Aggregate. For example, just now I submitted a single record
> successfully on the first attempt to Aggregate, and it appears there
> once. But in Fusion Tables, it appears three times (!). My prior try
> appeared once in Aggregate, and twice in Fusion Tables. What is going
> on?
>
> Thanks again for your help!
>
> Best,
> David
This is a by-product of the basic HTTP protocol used in publishing
submissions to
any external service like Google Spreadsheets or Fusion Tables, or, in fact,
any other web service.
After Aggregate publishes the submission to the web service, it waits for a
limited time for the web service to acknowledge the publication with a
"Successfully published" reply. If it receives no reply, or if the
connection
that Aggregate holds open waiting for the reply gets terminated (due to a
network glitch), Aggregate will conclude that the publication didn't occur.
In that eventuality, Aggregate is designed to ensure that at least one copy
of the submission eventually gets to the external service, and so, at the
next
opportunity, it will attempt to publish that exact same submission.
The difficulty is, the web service (e.g., Fusion Tables) may have received
the first request, and processed it successfully, but been unable to send
the
"Successfully published" reply either because a network glitch severed its
connection to Aggregate, or because the web service took longer than the
waiting time Aggregate allows for an acknowledgment.
That can lead to duplicate records appearing in any of the external
services.
Mitch
···
On Mon, Apr 11, 2011 at 7:39 AM, David wrote:
Strange - this no longer seems to be happening with newer records.
So, it is a random behavior, and I do not know what triggers it.
I have much appreciated the help received thus far from this
community.
It seems that Aggregate (0.96) is replicating records repeatedly to
Google Fusion Tables, even though only a single record appears in
Aggregate. For example, just now I submitted a single record
successfully on the first attempt to Aggregate, and it appears there
once. But in Fusion Tables, it appears three times (!). My prior try
appeared once in Aggregate, and twice in Fusion Tables. What is going
on?
Actually, in 0.9.6 Aggregate only sends the transmission once to
FusionTables. This is something we tried to address in 1.x. Mitch is
describing Aggregate 1.x behavior not 0.9.x. My guess is that was a
transient fusion table problem they fixed.
Waylon
···
On Mon, Apr 11, 2011 at 9:39 AM, Mitch Sundt wrote:
> Hi David,
>
> This is a by-product of the basic HTTP protocol used in publishing
> submissions to
> any external service like Google Spreadsheets or Fusion Tables, or, in fact,
> any other web service.
>
> After Aggregate publishes the submission to the web service, it waits for a
> limited time for the web service to acknowledge the publication with a
> "Successfully published" reply. If it receives no reply, or if the
> connection
> that Aggregate holds open waiting for the reply gets terminated (due to a
> network glitch), Aggregate will conclude that the publication didn't occur.
>
> In that eventuality, Aggregate is designed to ensure that at least one copy
> of the submission eventually gets to the external service, and so, at the
> next
> opportunity, it will attempt to publish that exact same submission.
>
> The difficulty is, the web service (e.g., Fusion Tables) may have received
> the first request, and processed it successfully, but been unable to send
> the
> "Successfully published" reply either because a network glitch severed its
> connection to Aggregate, or because the web service took longer than the
> waiting time Aggregate allows for an acknowledgment.
>
> That can lead to duplicate records appearing in any of the external
> services.
>
> Mitch
>
> On Mon, Apr 11, 2011 at 7:39 AM, David wrote:
>>
>> Strange - this no longer seems to be happening with newer records.
>> So, it is a random behavior, and I do not know what triggers it.
>>
>> Best,
>> David
>>
>> On Apr 11, 4:39 pm, David wrote:
>> > Dear all,
>> >
>> > I have much appreciated the help received thus far from this
>> > community.
>> >
>> > It seems that Aggregate (0.96) is replicating records repeatedly to
>> > Google Fusion Tables, even though only a single record appears in
>> > Aggregate. For example, just now I submitted a single record
>> > successfully on the first attempt to Aggregate, and it appears there
>> > once. But in Fusion Tables, it appears three times (!). My prior try
>> > appeared once in Aggregate, and twice in Fusion Tables. What is going
>> > on?
>> >
>> > Thanks again for your help!
>> >
>> > Best,
>> > David
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>
>
>
> --
> Mitch Sundt
> Software Engineer
> http://www.OpenDataKit.org
> University of Washington
> mitchellsundt@gmail.com
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>