You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@madlib.apache.org by "Frank McQuillan (JIRA)" <ji...@apache.org> on 2016/03/29 19:21:25 UTC

[jira] [Updated] (MADLIB-984) Path - refactor regex pattern match into cpp

     [ https://issues.apache.org/jira/browse/MADLIB-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Frank McQuillan updated MADLIB-984:
-----------------------------------
    Description: 
The UDF to be implemented will obtain the matching indices in `sym_str`, which is in turn used to filter `{match_to_row_id}` for matched rows. 

This implementations pipeline operations directly in `{matched_partitions}` and remove the need of creating and joining two extra tables/views `{length_of_matches}` and `{length_of_between_matches}`.

Boost.Regex can be helpful for implementing the proposed UDF:
http://www.boost.org/doc/libs/1_60_0/libs/regex/doc/html/boost_regex/ref/regex_match.html

  was:
Story

As a data scientist, I want to be able to define multiple symbols per row for pattern matching.

Acceptance
TBD


> Path - refactor regex pattern match into cpp
> --------------------------------------------
>
>                 Key: MADLIB-984
>                 URL: https://issues.apache.org/jira/browse/MADLIB-984
>             Project: Apache MADlib
>          Issue Type: New Feature
>          Components: Module: Utilities
>            Reporter: Frank McQuillan
>            Assignee: Rahul Iyer
>             Fix For: v1.9.1
>
>
> The UDF to be implemented will obtain the matching indices in `sym_str`, which is in turn used to filter `{match_to_row_id}` for matched rows. 
> This implementations pipeline operations directly in `{matched_partitions}` and remove the need of creating and joining two extra tables/views `{length_of_matches}` and `{length_of_between_matches}`.
> Boost.Regex can be helpful for implementing the proposed UDF:
> http://www.boost.org/doc/libs/1_60_0/libs/regex/doc/html/boost_regex/ref/regex_match.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)