<?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: kvstore import - fastest way in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/kvstore-import-fastest-way/m-p/652035#M110723</link>
    <description>&lt;P&gt;Tnx. it's working much faster.&amp;nbsp;&lt;BR /&gt;i transfer file to server and then | inputlookup file.csv | outputlookup kvstore&lt;/P&gt;</description>
    <pubDate>Wed, 26 Jul 2023 10:29:49 GMT</pubDate>
    <dc:creator>jbanAtSplunk</dc:creator>
    <dc:date>2023-07-26T10:29:49Z</dc:date>
    <item>
      <title>kvstore import - fastest way</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/kvstore-import-fastest-way/m-p/652026#M110721</link>
      <description>&lt;P&gt;what's the fastest way to import into KVStore?&lt;BR /&gt;I have about 650 000 rows and import is slow over "Lookup File Editig" app.&lt;BR /&gt;Import last Approx. few hours.&lt;BR /&gt;&lt;BR /&gt;Is there any faster way to import into KVStore.&lt;/P&gt;&lt;P&gt;Or do I create new dummy index and then I import into index (will that be faster)&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jul 2023 09:16:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/kvstore-import-fastest-way/m-p/652026#M110721</guid>
      <dc:creator>jbanAtSplunk</dc:creator>
      <dc:date>2023-07-26T09:16:28Z</dc:date>
    </item>
    <item>
      <title>Re: kvstore import - fastest way</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/kvstore-import-fastest-way/m-p/652031#M110722</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;maybe you could create temporary csv-file where you read those by input so and then forward those to kvstore with outputlookup command?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;r. Ismo&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jul 2023 09:54:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/kvstore-import-fastest-way/m-p/652031#M110722</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2023-07-26T09:54:49Z</dc:date>
    </item>
    <item>
      <title>Re: kvstore import - fastest way</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/kvstore-import-fastest-way/m-p/652035#M110723</link>
      <description>&lt;P&gt;Tnx. it's working much faster.&amp;nbsp;&lt;BR /&gt;i transfer file to server and then | inputlookup file.csv | outputlookup kvstore&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jul 2023 10:29:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/kvstore-import-fastest-way/m-p/652035#M110723</guid>
      <dc:creator>jbanAtSplunk</dc:creator>
      <dc:date>2023-07-26T10:29:49Z</dc:date>
    </item>
    <item>
      <title>Re: kvstore import - fastest way</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/kvstore-import-fastest-way/m-p/652043#M110725</link>
      <description>&lt;P&gt;Does not look promising. hitting 10Mb limit, not all data migrated into kvstore.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jul 2023 11:30:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/kvstore-import-fastest-way/m-p/652043#M110725</guid>
      <dc:creator>jbanAtSplunk</dc:creator>
      <dc:date>2023-07-26T11:30:01Z</dc:date>
    </item>
  </channel>
</rss>

