<?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: Question about Lookup File Editor in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Lookup-File-Editor-Is-there-any-workaround-other-than-reducing/m-p/587964#M8737</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/240826"&gt;@AHA-0114&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;there are two solutions:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;modify "ingest_max_memtable_bytes parameter in limits.conf (default 10 M) (for more infos see at &lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.5/Admin/Limitsconf" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.2.5/Admin/Limitsconf&lt;/A&gt;),&lt;/LI&gt;&lt;LI&gt;divide your lookups.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;If possible the second is better so you don't modify standard configurations, otherwise, you can use the first.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
    <pubDate>Tue, 08 Mar 2022 08:19:05 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2022-03-08T08:19:05Z</dc:date>
    <item>
      <title>Lookup File Editor: Is there any workaround other than reducing the lookup file size?</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Lookup-File-Editor-Is-there-any-workaround-other-than-reducing/m-p/587943#M8736</link>
      <description>&lt;P&gt;I try to edit lookup file through the lookup file editor, but below message is shown.&lt;BR /&gt;The file is too big to be edited (must be less than 10 MB)&lt;BR /&gt;Is there any workaround other than reducing the lookup file size?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2022 17:53:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Lookup-File-Editor-Is-there-any-workaround-other-than-reducing/m-p/587943#M8736</guid>
      <dc:creator>AHA-0114</dc:creator>
      <dc:date>2022-03-08T17:53:33Z</dc:date>
    </item>
    <item>
      <title>Re: Question about Lookup File Editor</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Lookup-File-Editor-Is-there-any-workaround-other-than-reducing/m-p/587964#M8737</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/240826"&gt;@AHA-0114&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;there are two solutions:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;modify "ingest_max_memtable_bytes parameter in limits.conf (default 10 M) (for more infos see at &lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.5/Admin/Limitsconf" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.2.5/Admin/Limitsconf&lt;/A&gt;),&lt;/LI&gt;&lt;LI&gt;divide your lookups.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;If possible the second is better so you don't modify standard configurations, otherwise, you can use the first.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2022 08:19:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Lookup-File-Editor-Is-there-any-workaround-other-than-reducing/m-p/587964#M8737</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2022-03-08T08:19:05Z</dc:date>
    </item>
  </channel>
</rss>

