Error with large Twitter filter seeds

[justinlittman]

Steps to reproduce:

1. Create a Twitter filter collection.
2. Add a seed with a tracks > ~3000 characters.

Expected result:

• Twitter filter seeds should be able to be as large as filter API accepts.
• If a seed is too large, an error should be reported.

Actual result:
500

Request Method: | POST
-- | --
http://ec2-52-15-218-157.us-east-2.compute.amazonaws.com/ui/seeds/create/19
2.0.7
OperationalError
index row size 2760 exceeds maximum 2712 for index "ui_seed_collection_id_uid_token_744a7e90_uniq" HINT:  Values larger than 1/3 of a buffer page cannot be indexed. Consider a function index of an MD5 hash of the value, or use full text indexing.
/usr/local/lib/python3.6/site-packages/django/db/backends/utils.py in _execute, line 85
/usr/local/bin/python3
3.6.6
['/opt/sfm-ui/sfm',  '/usr/local/lib/python36.zip',  '/usr/local/lib/python3.6',  '/usr/local/lib/python3.6/lib-dynload',  '/usr/local/lib/python3.6/site-packages']
Fri, 14 Sep 2018 21:55:23 -0400

[lwrubel]

@justinlittman I'm having a hard time reproducing this. Which log is that error from? I was able to save a filter seed with a Track parameter that was over 6000 characters. I don't see any errors in the docker logs for either sfm_ui_1 or sfm_twitterstreamharvester_1; nor do I get Django errors in the UI.

[justinlittman]

It would be from the webapps log. Are you using a clean install or existing install? (Wondering if this may cause differences in indexes.)

[lwrubel]

I'm sorry, what do you mean by the webapps log? I removed containers and brought it up again, with an existing database external to the containers.