<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Unique row number in  while indexing in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Unique-row-number-in-while-indexing/m-p/44909#M10612</link>
    <description>&lt;P&gt;&lt;CODE&gt;_cd&lt;/CODE&gt; is a unique number within an index (it consists of a bucket number and an offset within that bucket). It always exists. It does not increment just by 1 though, the only guarantee you have is that it's incrementing.&lt;/P&gt;

&lt;P&gt;Not sure what you mean by that it's taking a long time to search and why.&lt;/P&gt;</description>
    <pubDate>Fri, 24 May 2013 10:00:42 GMT</pubDate>
    <dc:creator>Ayn</dc:creator>
    <dc:date>2013-05-24T10:00:42Z</dc:date>
    <item>
      <title>Unique row number in  while indexing</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unique-row-number-in-while-indexing/m-p/44906#M10609</link>
      <description>&lt;P&gt;Hi All,&lt;BR /&gt;
Is there any possibility to create a unique index number while indexing because i want to search the result on behalf of last event id  i  read.then i will read the event greater then  from that last event id.&lt;BR /&gt;
The problem i faced is device is generating wrong date time and that time is future date time in that case our earliest and latest logic is failing. because i was storing the _time value as a last trigger date and that was future date.so i want to create a unique auto incremented  row number id while indexing.&lt;BR /&gt;
Please help!!&lt;/P&gt;</description>
      <pubDate>Fri, 24 May 2013 09:05:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unique-row-number-in-while-indexing/m-p/44906#M10609</guid>
      <dc:creator>himanshusinha1</dc:creator>
      <dc:date>2013-05-24T09:05:11Z</dc:date>
    </item>
    <item>
      <title>Re: Unique row number in  while indexing</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unique-row-number-in-while-indexing/m-p/44907#M10610</link>
      <description>&lt;P&gt;You could use &lt;CODE&gt;_indextime&lt;/CODE&gt; instead of &lt;CODE&gt;_time&lt;/CODE&gt;. If that's not enough you could also use (or combine) the &lt;CODE&gt;_cd&lt;/CODE&gt; field for uniqueness. Both are a kind of incrementing counters.&lt;/P&gt;</description>
      <pubDate>Fri, 24 May 2013 09:20:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unique-row-number-in-while-indexing/m-p/44907#M10610</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2013-05-24T09:20:49Z</dc:date>
    </item>
    <item>
      <title>Re: Unique row number in  while indexing</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unique-row-number-in-while-indexing/m-p/44908#M10611</link>
      <description>&lt;P&gt;Thanks.. can we get _cd in every type of device logs?&lt;BR /&gt;
Can we get the two ranges of _cd logs e.g i got 1234 in _cd now i want the logs between 1234 and 1240 o/p = 6 events?&lt;BR /&gt;
_indextime is returning epoch time and its taking long time i search.&lt;/P&gt;</description>
      <pubDate>Fri, 24 May 2013 09:34:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unique-row-number-in-while-indexing/m-p/44908#M10611</guid>
      <dc:creator>himanshusinha1</dc:creator>
      <dc:date>2013-05-24T09:34:29Z</dc:date>
    </item>
    <item>
      <title>Re: Unique row number in  while indexing</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unique-row-number-in-while-indexing/m-p/44909#M10612</link>
      <description>&lt;P&gt;&lt;CODE&gt;_cd&lt;/CODE&gt; is a unique number within an index (it consists of a bucket number and an offset within that bucket). It always exists. It does not increment just by 1 though, the only guarantee you have is that it's incrementing.&lt;/P&gt;

&lt;P&gt;Not sure what you mean by that it's taking a long time to search and why.&lt;/P&gt;</description>
      <pubDate>Fri, 24 May 2013 10:00:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unique-row-number-in-while-indexing/m-p/44909#M10612</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2013-05-24T10:00:42Z</dc:date>
    </item>
  </channel>
</rss>

