Page "Proposals/BEP-0013" was changed by thimal Diff URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0013?action=diff&version=4> Revision 4 Changes: -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: Proposals/BEP-0013 ========================================================================= --- Proposals/BEP-0013 (version: 3) +++ Proposals/BEP-0013 (version: 4) @@ -80,7 +80,9 @@ This will show list of related tickets to users to avoid duplicates. -For this it need to use the BloodhoundSearch API, But due to the complexity in powerfulness of BloodhoundSearch API I hope to start with the TracSearch API and get the component to work with the TracSearch API and then move into the BloodhoundSearch API, as a incremental development. (need to check the possibility to use the Query API, I have not done many research on this so need to do bit research on this). +This has two approaches first is to use the Ticket Query API, other one is to use the BloodhoundSearch API. +But to give more support to users to find the duplicate ticket it need to search whole phrase typed in the summary field, part of the phrase typed in summary field and significant words typed in summary field. To search all these at once it is better to use BloodhoundSearch API. As the Ticket Query API search only the exact phrase or word provide to it. (but need to check the performance) +For this it need to use the BloodhoundSearch API, But due to the complexity in powerfulness of BloodhoundSearch API I hope to start with the TracSearch API and get the component to work with the TracSearch API and then move into the BloodhoundSearch API, as a incremental development. @@ -93,7 +95,7 @@ For the frond end it has two fields to update. Cc field would be same as the keyword field and owner field will give list of users according to the keys users type and only username can enter. -== Approximate Schedule #Approximate Schedule +== Approximate Schedule #Approximate Schedule Gsoc will be for 14 weeks and here is rough estimation of the work break down. But this will be change according to the work flow and the discussion with bloodhound community. -------8<------8<------8<------8<------8<------8<------8<------8<--------
-- Page URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0013> Apache Bloodhound <https://issues.apache.org/bloodhound/> The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0013' page. If it was not you, please report to .
