Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CHE-137. Improve full text searching #1215

Merged
merged 1 commit into from
May 13, 2016
Merged

CHE-137. Improve full text searching #1215

merged 1 commit into from
May 13, 2016

Conversation

RomanNikitenko
Copy link
Member

@RomanNikitenko RomanNikitenko commented May 10, 2016

  1. Escape those characters that QueryParser expects to be escaped to correct search
  2. Change behavior of full text searching:
    • old mode: on server side some text for searching splited on separate words and you get all files which contain at least one of the word
    • new mode - we will find only text for searching as particular sequence of words
  3. Change UI for 'Find text' window:
    before my changes
    search_text_before
    after my changes

search_text_after

@skabashnyuk @vparfonov @slemeur

@skabashnyuk
Copy link
Contributor

need some test for server side

@skabashnyuk
Copy link
Contributor

skabashnyuk commented May 10, 2016

-1
I think we can stay on one query parser.
Issue need some more investigation

@codenvy-ci
Copy link

Build finished.

1 similar comment
@codenvy-ci
Copy link

Build finished.

float: left;
line-height: 22px;
margin: 0 0 0 4px;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

margin-left: 4px;

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you, Vlad. I'll fix.

@RomanNikitenko
Copy link
Member Author

@skabashnyuk @vparfonov I've updated pull request, please review.

@RomanNikitenko RomanNikitenko changed the title CHE-137. Add phrase search mode CHE-137. Improve full text searching May 13, 2016
@@ -242,15 +242,15 @@ private Query createLuceneQuery(QueryExpression query) throws ServerException {
final String path = query.getPath();
final String text = query.getText();
if (path != null) {
luceneQuery.add(new PrefixQuery(new Term("path", path)), BooleanClause.Occur.MUST);
luceneQuery.add(new PrefixQuery(new Term("path", path)), MUST);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should keep BooleanClause.Occur.MUST way. It has much more descriptive.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@skabashnyuk done!

@skabashnyuk
Copy link
Contributor

other ok

@slemeur
Copy link
Contributor

slemeur commented May 13, 2016

OK for me

@vparfonov
Copy link
Contributor

ok

Signed-off-by: Roman Nikitenko <rnikitenko@codenvy.com>
@RomanNikitenko RomanNikitenko merged commit 2fa6716 into master May 13, 2016
@RomanNikitenko RomanNikitenko deleted the CHE-137 branch May 13, 2016 13:03
@codenvy-ci
Copy link

Build # 573 - FAILED

Please check console output at http://ci.codenvy-dev.com/jenkins/job/che-pullrequests-build/573/ to view the results.

Katka92 pushed a commit to Katka92/che that referenced this pull request Jun 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants