Skip to content

(Team 2) Design: Query Rewriter #29

Closed

Description

@chenlica

Team 2:

Please do the following for your task.

Add @kishore-narendran to this issue.

Activity

  1. changed the title [-]Design: character-based fuzzy search[/-] [+](Team 2) Design: character-based fuzzy search[/+] on Apr 5, 2016
  2. chenlica commented on Apr 12, 2016

    @chenlica
    ContributorAuthor

    Per our discussion in the lecture today, please do the following:

  3. chenlica commented on Apr 19, 2016

    @chenlica
    ContributorAuthor

    @shiladityasen and @kishore-narendran: Please refine your design to come up with an interface for the classes. We can schedule a meeting this week when you are ready.

  4. JavierJia commented on Apr 21, 2016

    @JavierJia
    Contributor
  5. changed the title [-](Team 2) Design: character-based fuzzy search[/-] [+](Team 2) Design: Query Rewriter[/+] on Apr 21, 2016
  6. ss3n commented on Apr 21, 2016

    @ss3n
    Contributor

    Thank you Professor,

    We will go through the literature to find how to incorporate that in our
    module.
    For now we are going to define the interfaces, write some tests and build a
    very naive algorithmic version in sandbox.

    On Wed, Apr 20, 2016 at 8:45 PM, Jianfeng Jia notifications@github.com
    wrote:

    Here is the Chinese tokenizer code in SRCH2 codebase:
    https://github.com/SRCH2/srch2-ngn/blob/master/src/core/analyzer/ChineseTokenizer.cpp#L197

    —
    You are receiving this because you were mentioned.
    Reply to this email directly or view it on GitHub
    #29 (comment)

  7. kishore-narendran commented on Apr 26, 2016

    @kishore-narendran
    Contributor

    The current status of the issue is such:

    • The interface to the QueryRewriter has been setup
    • QueryRewriter internally uses FuzzyTokenizer to find the permutations of search strings needed.
    • A few test cases have also been written in QueryRewriterTest.java
    • A new type of IField was written to reflect the type of ITuple that the QueryRewriter will return i.e. a list of Strings.

    The above changes were submitted in the PR #75

    This is what is up next -

    • We will write a naive version of the FuzzyTokenizer and test it in textdb-sandbox
    • The naive version will then be ported into textdb-dataflow to the actual FuzzyTokenizer class
    • We will then optimize and improve the FuzzyTokenizer algorithm, and iterate

    @chenlica @JavierJia

    This is currently the status of the issue!

  8. ss3n commented on Apr 26, 2016

    @ss3n
    Contributor

    QueryRewriter will require certain dictionaries to be present (or provided by user) such as dictionary of English words. Which would be the ideal directory to store this dictionary in?
    @chenlica @JavierJia @rajesh9625 @sandeepreddy602

  9. sandeepreddy602 commented on Apr 26, 2016

    @sandeepreddy602
    Contributor

    @shiladityasen... You can create one more source folder src/test/resources and add your directories there.

  10. chenlica commented on Apr 26, 2016

    @chenlica
    ContributorAuthor

    @sandeepreddy602 : This English word dictionary is part of the operator, so it should NOT be part the test folder, right? Can each operator have its own local "resources" directory for such files?

  11. sandeepreddy602 commented on Apr 26, 2016

    @sandeepreddy602
    Contributor

    @chenlica.. In that case we can create the source folder src/main/resources and create directory for each operator. We can add the operator related data files in the corresponding directory.

  12. chenlica commented on Apr 26, 2016

    @chenlica
    ContributorAuthor

    @sandeepreddy602 : Agreed. We can use this PR to create this folder structure. I hope it's easy for each operator to locate that file using a relative path.

  13. ss3n commented on Apr 27, 2016

    @ss3n
    Contributor

    @chenlica @sandeepreddy602 : Just to clarify, we are deciding to create a separate package src/main/resources for every project (such as textdb-dataflow)? Then every operator implemented in the project can access the files in src/main/resources.

    Is this correct?

  14. 11 remaining items

  15. added a commit that references this issue on May 2, 2016
  16. kishore-narendran commented on May 2, 2016

    @kishore-narendran
    Contributor

    This is the current status of this issue:

    This is what is up next:

    • An optimized version of the implementation will be implemented in an upcoming PR, which will either utilize @JavierJia's dynamic programming approach, OR, we are alternatively looking at an algorithm that utilizes a Trie data structure to perform the tokenization.
  17. chenlica commented on May 9, 2016

    @chenlica
    ContributorAuthor

    Team 2: Any update on your task? Thanks for agreeing to present the dynamic programming algorithm today. It will be good to create a Google presentation for your work.

  18. ss3n commented on May 9, 2016

    @ss3n
    Contributor

    Hello Professor,

    We are deciding the basic layout of the presentation and some examples to
    illustrate the working and where it fits in our application.

  19. chenlica commented on May 23, 2016

    @chenlica
    ContributorAuthor

    @shiladityasen and @kishore-narendran when can you raise a PR to finish it?

  20. ss3n commented on May 23, 2016

    @ss3n
    Contributor

    @chenlica : Professor, we intend to raise a PR later tonight or by tomorrow morning.

  21. kishore-narendran commented on May 23, 2016

    @kishore-narendran
    Contributor

    #120

    The above PR, implements:

    • The Dynamic Programming algorithm for performing tokenization with highest likelihood.
    • Modifies test cases.
  22. added a commit that references this issue on May 24, 2016
  23. kishore-narendran commented on Jun 7, 2016

    @kishore-narendran
    Contributor

    @chenlica We completed the documentation, and this can be found at https://github.com/TextDB/textdb/wiki/CS290-2016S-Task:-Query-Rewriter. Do you think we can proceed to close this issue?

  24. chenlica commented on Jun 7, 2016

    @chenlica
    ContributorAuthor

    I will review it first. Thanks.

  25. chenlica commented on Jun 8, 2016

    @chenlica
    ContributorAuthor

    I reviewed and polished your wiki page. Now you can close the issue.

    Congratulations!

  26. ss3n commented on Jun 8, 2016

    @ss3n
    Contributor

    Thank you so much, Professor :)

    On Tue, Jun 7, 2016 at 5:58 PM, Chen Li notifications@github.com wrote:

    I reviewed and polished your wiki page. Now you can close the issue.

    Congratulations!

    —
    You are receiving this because you were mentioned.
    Reply to this email directly, view it on GitHub
    #29 (comment), or mute
    the thread
    https://github.com/notifications/unsubscribe/APbwhOH_GNnSKLkm61up4uyWidfbzcjfks5qJhOogaJpZM4H_v0D
    .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions