Debugging a very odd error in our trending database which only seems to occur on the specific 573214th tweet in our test data.