Good question. I am not sure if the search backend would be able to help
you with that. For a large number of tickets, collecting all the
keywords might turn out to be quite time consuming and so I see why you
would like to store the results in the database. That the keywords are a
list in a single field may not be all that helpful either.
Despite all that I would start by considering storing the frequencies as
a premature optimisation to start with and you should make sure that you
know how to extract the list of keywords. Once you have that ability you
could choose to store or perhaps cache the results. Either way you will
need to consider when you should update the information (yes, obviously
every time a keyword is added/removed) and also how to do that
relatively efficiently.
I suspect it would be a lot nicer if the search system could do a lot of
this for you!
Cheers,
Gary
On 21/03/14 14:32, Sifa Sensay wrote:
Hi,
Thank you very much for the reply! I have one more question though.
For the autocompletion of keywords part, is it possible to store all
possible keywords in a separate table in the database with their frequency,
then use these frequencies for popularity order of keywords? if not, what
is the possible way to do it with database?
Kind Regards,
Sifa Sensay
On Thu, Mar 20, 2014 at 4:27 PM, Gary Martin <[email protected]>wrote:
On 20/03/14 14:04, Sifa Sensay wrote:
Hi,
Ryan told to Thimal that we can use Query API as an alternative to Search
APIs for Duplicate ticket search component. I was searching for it last
night and I have found the TicketQuery wiki macro which listing tickets
that match certain criteria. Could you please give me more detail about
it.
Is it appropriate to use TicketQuery wiki macro to in order to implement
this component?
Kind Regards
Hi Sifa,
Tapping into the new search capabilities may well get better results than
looking at custom queries. Using a wiki macro may well be an interesting
shortcut to generating the required display but you would need the server
to do the work of rendering the macro for you. If there is a macro that
gives (or can be made to give) the results in the form you require, that
could be an interesting shortcut but just requesting the data you require
should also work.
I would think that a large part of the answer may come from how you
propose to present the duplicate tickets to the user.
Cheers,
Gary
