Splunk stopped indexing when it came across a bigint number

[arya_alex]

I am using Splunk to import data from a mysql database using DB Connect App. I created data inputs for the same. Splunk is not properly importing and indexing certain tables. Both the tables imported& indexed 5 months of data.But both of them stopped importing when it came across this row
2013-03-06 | abc | 2783063764 | 2013-03-07 02:48:19

The value 2783063764 is the highest integer value on that table.Is this any issue with the default limit for a numerical field?

[sowings]

Splunk doesn't require your data to have any shape when indexing it. It should be treating that as a string. There may be some other issue. Are you seeing any log entries indicating an error?

[bigtyma]

If you are using a sql select statement you might consider casting the number to varchar.