The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

FishEye: search for quoted string in content

Johan Corveleyn
July 9, 2012

In FishEye (2.7.14), when I search content for "blah" (including the double quotes), FishEye will give me all matches for blah (with or without double quotes before/after the string). Is there a way to let FishEye give only matches for "blah" literally, so only files which contain the string surrounded by double quotes?

The EyeQL that corresponds to my search is:

select revisions from dir "/" where (is head and content matches "\"blah\"") order by date desc group by changeset return path, revision, author, date, csid

Regardless, I still get all matches of files which do not have the quotes ...

Is this a bug?

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Johan Corveleyn
July 19, 2012

Filed issue with Atlassian: FE-4202 - Cannot search for quoted string in content (quotes are ignored)

0 votes
Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 9, 2012

Try this:

select revisions from dir "/" where (is head and comment =~ ".*\"blah\".*" order by date  desc  group by changeset return path, revision, author, date, csid

Johan Corveleyn
July 10, 2012

Doesn't work (I added 'content' before the =~, otherwise I get an 'unexpected token' error):

Search error:

error parsing query: expecting "matches", found '=~'

And if I use content matches ".*\"blah\".*", that never matches.

Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 10, 2012

I am sorry, you need comment. I accidently removed it while typing. Try now, I have modified the answer.

Johan Corveleyn
July 10, 2012

Ok, that works for commit messages. But I need this for "content" search, not for searching commit messages (which is why I specifically mentioned "search ... in content" in the question).

Still, thanks for taking the time to try and answer my question.

Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 10, 2012

btw, it looks only at commit messages.

TAGS
AUG Leaders

Atlassian Community Events