<?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: Rexgex Non-capturing group - still capturing in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Rexgex-Non-capturing-group-still-capturing/m-p/343734#M101819</link>
    <description>&lt;P&gt;Figured this out - by changing where the new field name paranthesie was...&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;rex field=title "(?&amp;lt;titleNEW&amp;gt;(.*?))(?:-)"
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Mon, 31 Jul 2017 20:47:27 GMT</pubDate>
    <dc:creator>tb5821</dc:creator>
    <dc:date>2017-07-31T20:47:27Z</dc:date>
    <item>
      <title>Rexgex Non-capturing group - still capturing?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Rexgex-Non-capturing-group-still-capturing/m-p/343733#M101818</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;rex field=title "(?titleNEW(.*?)(?:-))"
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;I have this rex command above but it still outputs the dash at the end which is in a non-capturing group- any help?&lt;/P&gt;</description>
      <pubDate>Mon, 13 Feb 2023 16:48:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Rexgex-Non-capturing-group-still-capturing/m-p/343733#M101818</guid>
      <dc:creator>tb5821</dc:creator>
      <dc:date>2023-02-13T16:48:00Z</dc:date>
    </item>
    <item>
      <title>Re: Rexgex Non-capturing group - still capturing</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Rexgex-Non-capturing-group-still-capturing/m-p/343734#M101819</link>
      <description>&lt;P&gt;Figured this out - by changing where the new field name paranthesie was...&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;rex field=title "(?&amp;lt;titleNEW&amp;gt;(.*?))(?:-)"
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 31 Jul 2017 20:47:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Rexgex-Non-capturing-group-still-capturing/m-p/343734#M101819</guid>
      <dc:creator>tb5821</dc:creator>
      <dc:date>2017-07-31T20:47:27Z</dc:date>
    </item>
    <item>
      <title>Re: Rexgex Non-capturing group - still capturing</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Rexgex-Non-capturing-group-still-capturing/m-p/630541#M219064</link>
      <description>&lt;P&gt;Not sure if you have an optimal regex.&amp;nbsp; Why do you make a non capturing group of "&lt;STRONG&gt;-&lt;/STRONG&gt;" and why a capture group in the named group?&amp;nbsp; This is some better:&lt;/P&gt;&lt;PRE&gt;rex field=title "(?&amp;lt;titleNEW&amp;gt;.*?):-"&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;Even better, do not use * in regex when its not needed.&amp;nbsp; Do a search until you find some that its not included, like this:&lt;/P&gt;&lt;PRE&gt;rex field=title "(?&amp;lt;titleNEW&amp;gt;[^-]+)"&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 11 Feb 2023 10:29:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Rexgex-Non-capturing-group-still-capturing/m-p/630541#M219064</guid>
      <dc:creator>jotne</dc:creator>
      <dc:date>2023-02-11T10:29:12Z</dc:date>
    </item>
  </channel>
</rss>

