I am working on a project that is on Google Standard App Engine.This requires the use of Search API functionality. However i could not find Search Api with partial text match. It is only gives full text search.
Is there a way for partial text match?
If not any custom tokenizer i can implement?
Related
I'm indexing PDFs into an Azure Cognitive Search index and created a search page.
I'm using the highlights feature, but the returned content is pretty ugly. Sometimes it even returns the content from the footer of the files. It removes spaces and it looks like a mess.
To index the files I'm using the default configuration. The 'content' field uses a Standard Analyzer. I have configured an Indexer connected to a Data Source that points to an Azure Storage folder.
What is the best approach to display a more user-friendly excerpt of the file?
I am making a react application where there will be few buttons like sorting, removing duplicates etc. And there will be input field to get the text(for example, the text that has to be sorted) and there will also be output field to display the result. I also have login and sign up page in this application, so that only registered users can use the application. Now I want to have a history view for all the operations performed by each user. To store the history, I will be using Elastic Search. I'm absolutely new to ElasticSearch. So I would like to get some rough idea or a blueprint like what are the steps I will have to follow. Much appreciated.
I've used Java in the server side
Below is highlevel idea you can implement for user tracking:
Log each action of user into log files.
Use Logstash File Input Plugin or Filebeat Log Input for reading your file and indexing to the elasticsearch using output plugin.
Use Kibana for visulization.
1-What is the best and correct way to pass a Google Map Polygon to Azure Search.
2-If 2 Polygons are intersecting, how does this need to be handled.
Thank you.
The only part of the Azure Search API where you can specify a polygon is in a filter expression. In the .NET SDK you can use the SearchParameters.Filter property to set the filter. The OData syntax reference for Azure Search has details and examples of how to format a polygon literal in the geo.intersects() function.
Azure Search only supports passing a single polygon literal to geo.intersects, so the second part of the question does not apply.
I am trying to add a filter in my Microsoft Graph API request on O365 data (like mails, messages, events, etc.) to only get items where certain regex triggers.
I found the search feature: Full Text Search Capabilities in Azure AD Graph API (preview), but it seems this feature have been removed (and it did not have regex capabilities).
Advanced warning notice: The Azure AD Graph team will be shutting off this preview capability. As of September 19th 2016, this feature will no longer be available. We’d like to hear from you if you have been using this capability, and what you think about it. We are currently investigating some options around introducing this type of capability again at a future (unspecified) date.
I also found the contains filter, that is used like this: $filter=contains(body, 'Bob'), but I can't seem to use a regex rule in it and it doesn't seem to be able to search in the body.
Is it possible to build a query that will only return items where a regex rule is triggered? Worse case scenario, I will download all items and then use regex rules on them, but I would prefer to not download all those useless items if possible.
The Azure AD Graph API and Microsoft Graph API are two different APIs. At present, the Microsoft API supports the OData Query Parameters to help customize the response.
Is it possible to build a query that will only return items where a regex rule is triggered?
No, it doesn't this feature. You may submit the feedback here if you require this feature.
I want to create some custom search logic.
I found the logic quite custom so I dont see how this can implemented by extending SOLR.
More specifically, I want client to use the id to perform a search to find similar items of the same category. But the returned results need to be filtered with some very custom logic.
For that reason, I think I want to implement some custom service that will expose a REST API to the client and then it will forward the request to SOLR search.
Do you think that I can avoid this option by extending SOLR search implementation?
Which is best practice?
The best practice is to have a layer between Solr and the client anyway. Solr does not have security out of the box and anybody who can access it can issue delete commands as well as the search one.
So, doing a REST interface to the client and talking to Solr via a secure link (firewall/IP protected) is the good practice.