Multiple remote query executions merged together due to timestamp clash about lsq HOT 2 OPEN

I guess the better solution is the middle ground: prefer the timestamp - but if there are clashes then start using sequential ids within that timestamp. The idea is that even when processing only a subset of a log one would get the same RDF data for the remote executions because a request usually can be globally identified by its destination URL and timestamp. With sequence ID this information would get completely lost.

from lsq.

I proposed a simple solution. Obviously other solutions may be found, but I think this an important bug and should be addressed. The advantage of this solution is that is does not add any bottleneck.
If the problem is preserving the ID when processing a subset of a log, this could be addressed separately if LSQ is aware of the line of the log on which it starts (could be a parameter), by starting seqId from an appropriate initial value.

from lsq.