https://community.splunk.com/t5/Getting-Data-In/Getting-error-when-using-DATETIME-CONFIG-CURRENT-for-a-batch/m-p/508173#M86482 <P>Hi,</P> <P>I am using a batch input to ingest some huge files with a single line events that do not have a timestamp.</P> <P>I have used the DATETIME_CONFIG = CURRENT config but found the following error.:<BR /><BR /></P> <LI-CODE lang="markup">WARN AggregatorMiningProcessor - Too many events (100K) with the same timestamp: incrementing timestamps 1 second(s) into the future to insure retrievability . </LI-CODE> <P><BR /><BR />Which is more effective NONE or CURRENT and what can be used in my case?&nbsp;</P> <P>Thanks</P> <P>&nbsp;</P> Wed, 08 Jul 2020 22:48:47 GMT nawazns5038 2020-07-08T22:48:47Z https://community.splunk.com/t5/Getting-Data-In/Getting-error-when-using-DATETIME-CONFIG-CURRENT-for-a-batch/m-p/508173#M86482 <P>Hi,</P> <P>I am using a batch input to ingest some huge files with a single line events that do not have a timestamp.</P> <P>I have used the DATETIME_CONFIG = CURRENT config but found the following error.:<BR /><BR /></P> <LI-CODE lang="markup">WARN AggregatorMiningProcessor - Too many events (100K) with the same timestamp: incrementing timestamps 1 second(s) into the future to insure retrievability . </LI-CODE> <P><BR /><BR />Which is more effective NONE or CURRENT and what can be used in my case?&nbsp;</P> <P>Thanks</P> <P>&nbsp;</P> Wed, 08 Jul 2020 22:48:47 GMT https://community.splunk.com/t5/Getting-Data-In/Getting-error-when-using-DATETIME-CONFIG-CURRENT-for-a-batch/m-p/508173#M86482 nawazns5038 2020-07-08T22:48:47Z