<?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: dboutput bug updating MySQL in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/dboutput-bug-updating-MySQL/m-p/42739#M179069</link>
    <description>&lt;P&gt;You can't currently have multiple key values for the update to occur on. This is one of the things we might add when we make dboutput GA.&lt;/P&gt;</description>
    <pubDate>Wed, 05 Jun 2013 18:52:28 GMT</pubDate>
    <dc:creator>Dan</dc:creator>
    <dc:date>2013-06-05T18:52:28Z</dc:date>
    <item>
      <title>dboutput bug updating MySQL</title>
      <link>https://community.splunk.com/t5/Splunk-Search/dboutput-bug-updating-MySQL/m-p/42735#M179065</link>
      <description>&lt;P&gt;I'm using DB Connect to send search results to MySQL.  My search command is:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;... | dboutput type=update notFound=insert database=mydb table=mytable fields=IPAddress AS ip, NetAddress AS mac, ComputerName AS device_name,
 Manufacturer AS manufacturer, Model AS model_name key=ip,mac *
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This produces the error message "No value specified for parameter 1".  Turning on debug logging I see the following query is generated:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;UPDATE mytable SET `AS`=$AS$, ip=$ip$, NetAddress=$NetAddress$, ComputerName=$ComputerName$, Manufacturer=$Manufacturer$, Model=$Model$, mac=$mac$, IPAddress=$IPAddress$ WHERE ip = $ip$
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Notice the 'AS' column was inserted.  Where did it come from and how do I get rid of it?&lt;/P&gt;

&lt;P&gt;Also, my key argument specified two fields, but only one appears in the query.  Is that another bug or something I did wrong?&lt;/P&gt;</description>
      <pubDate>Wed, 22 May 2013 15:54:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/dboutput-bug-updating-MySQL/m-p/42735#M179065</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2013-05-22T15:54:45Z</dc:date>
    </item>
    <item>
      <title>Re: dboutput bug updating MySQL</title>
      <link>https://community.splunk.com/t5/Splunk-Search/dboutput-bug-updating-MySQL/m-p/42736#M179066</link>
      <description>&lt;P&gt;I would be interested in knowing if you can actually provide two key values for the update to occur on.&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2013 21:29:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/dboutput-bug-updating-MySQL/m-p/42736#M179066</guid>
      <dc:creator>cramasta</dc:creator>
      <dc:date>2013-05-23T21:29:36Z</dc:date>
    </item>
    <item>
      <title>Re: dboutput bug updating MySQL</title>
      <link>https://community.splunk.com/t5/Splunk-Search/dboutput-bug-updating-MySQL/m-p/42737#M179067</link>
      <description>&lt;P&gt;FYI, finding out that trying to use type=update will fail when Splunk results are more than 100 rows. Seems that type=insert is able to run batches of 100 but type=update doesn't know how to run batches and the max that will work is whatever the setting is in the java.conf file for batch size &lt;/P&gt;

&lt;P&gt;Here is the error you would see ( i updated the batch size to 105 and tried exporting 108 rows, exporting 104 rows would work)&lt;/P&gt;

&lt;P&gt;command="dboutput", Unexpected error while performing dboutput: java.lang.ArrayIndexOutOfBoundsException: 105&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2013 22:48:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/dboutput-bug-updating-MySQL/m-p/42737#M179067</guid>
      <dc:creator>cramasta</dc:creator>
      <dc:date>2013-05-23T22:48:09Z</dc:date>
    </item>
    <item>
      <title>Re: dboutput bug updating MySQL</title>
      <link>https://community.splunk.com/t5/Splunk-Search/dboutput-bug-updating-MySQL/m-p/42738#M179068</link>
      <description>&lt;P&gt;trying to get my hands on the mysql connector, I dont think it has this limitation.&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2013 22:49:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/dboutput-bug-updating-MySQL/m-p/42738#M179068</guid>
      <dc:creator>cramasta</dc:creator>
      <dc:date>2013-05-23T22:49:14Z</dc:date>
    </item>
    <item>
      <title>Re: dboutput bug updating MySQL</title>
      <link>https://community.splunk.com/t5/Splunk-Search/dboutput-bug-updating-MySQL/m-p/42739#M179069</link>
      <description>&lt;P&gt;You can't currently have multiple key values for the update to occur on. This is one of the things we might add when we make dboutput GA.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2013 18:52:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/dboutput-bug-updating-MySQL/m-p/42739#M179069</guid>
      <dc:creator>Dan</dc:creator>
      <dc:date>2013-06-05T18:52:28Z</dc:date>
    </item>
  </channel>
</rss>

