Hi,
For me the wild card functionality is fine and functions as expected.
It's partly because of it that I expected an exact match when no operator
was in play.
Regards,
-Stefan
On Sun, Oct 4, 2015 at 10:15 PM, Steven Phillips <ste...@dremio.com> wrote:
> Repated_contains originally worked as Jason describes, exact matching. At
> some point, someone thought that it should allow wildcards and do substring
> matching. There was never any real discussion on what this function should
> do, though. It would probably be a good idea for someone to come up with a
> more thorough proposal that includes a more comprehensive list of repeated
> functions and what they will do.
>
> On Wed, Sep 23, 2015 at 10:16 AM, Jason Altekruse <
> altekruseja...@gmail.com>
> wrote:
>
> > I think it is reasonable to consider that a bug. We should implement the
> > function both as it works today and as you were originally expecting it.
> > Any ideas about about a good naming scheme for the two?
> >
> > Unfortunately the regular contains() method does substring matching, but
> I
> > think the name repeated_contains() should be used for exact matching. I'm
> > inclined to suggest something like repeated_contains_regex_matching() for
> > the other, but that is a bit long.
> >
> > On Mon, Sep 21, 2015 at 2:41 AM, Stefán Baxter <
> ste...@activitystream.com>
> > wrote:
> >
> > > Hi
> > >
> > > repeated_contains seems to have a strange default behavior as it
> behaves
> > > like a startsWith, rather than a equalTo.
> > >
> > > With this data:
> > >
> > > {"alist":["cat","dog"]}
> > > {"alist":["catastrophic"]}
> > >
> > >
> > > and this query:;
> > >
> > > select alist from table where repeated_contains(`alist`,'cat');
> > >
> > >
> > > both records are returned.
> > >
> > > I do realize that repeated_contains accepts regular expressions but i
> > > wonder if this behavior is by design or a bug. (I also know that I can
> > end
> > > the query string with a $ but that just does not seem right)
> > >
> > > Regards,
> > > -Stefan
> > >
> >
>
