<?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 Cropped results for inputlookup via REST ? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Cropped-results-for-inputlookup-via-REST/m-p/322914#M60117</link>
    <description>&lt;P&gt;I'm trying to run search via the REST api, to get the contents of a lookup:&lt;/P&gt;

&lt;P&gt;| inputlookup my_lookup&lt;/P&gt;

&lt;P&gt;I got only 100 rows in the results, which is weird, because my lookup is much bigger. I've checked in limits.conf, I'm using the default setting - 50000 rows.&lt;BR /&gt;
Is there something with lookups? Any other search queries I did with REST worked as expected. I wasn't able to find indicator for this limitation in the HTTP requests/responses used for the search.&lt;/P&gt;</description>
    <pubDate>Wed, 31 May 2017 07:34:44 GMT</pubDate>
    <dc:creator>szabados</dc:creator>
    <dc:date>2017-05-31T07:34:44Z</dc:date>
    <item>
      <title>Cropped results for inputlookup via REST ?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cropped-results-for-inputlookup-via-REST/m-p/322914#M60117</link>
      <description>&lt;P&gt;I'm trying to run search via the REST api, to get the contents of a lookup:&lt;/P&gt;

&lt;P&gt;| inputlookup my_lookup&lt;/P&gt;

&lt;P&gt;I got only 100 rows in the results, which is weird, because my lookup is much bigger. I've checked in limits.conf, I'm using the default setting - 50000 rows.&lt;BR /&gt;
Is there something with lookups? Any other search queries I did with REST worked as expected. I wasn't able to find indicator for this limitation in the HTTP requests/responses used for the search.&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2017 07:34:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cropped-results-for-inputlookup-via-REST/m-p/322914#M60117</guid>
      <dc:creator>szabados</dc:creator>
      <dc:date>2017-05-31T07:34:44Z</dc:date>
    </item>
    <item>
      <title>Re: Cropped results for inputlookup via REST ?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cropped-results-for-inputlookup-via-REST/m-p/322915#M60118</link>
      <description>&lt;P&gt;Already solved here:&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/208682/rest-api-why-am-i-hitting-a-limit-of-100-exported.html"&gt;https://answers.splunk.com/answers/208682/rest-api-why-am-i-hitting-a-limit-of-100-exported.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2017 08:22:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cropped-results-for-inputlookup-via-REST/m-p/322915#M60118</guid>
      <dc:creator>szabados</dc:creator>
      <dc:date>2017-05-31T08:22:13Z</dc:date>
    </item>
    <item>
      <title>Re: Cropped results for inputlookup via REST ?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cropped-results-for-inputlookup-via-REST/m-p/322916#M60119</link>
      <description>&lt;P&gt;Click &lt;CODE&gt;Accept&lt;/CODE&gt; to close the question.&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2017 15:26:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cropped-results-for-inputlookup-via-REST/m-p/322916#M60119</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-05-31T15:26:01Z</dc:date>
    </item>
  </channel>
</rss>

