liamca

5 ms·

1.
by liamca 9y ago
[Full disclosure, I work on the Azure Search team] Cosmos DB has tight integration with Azure Search, to the point that you can choose to extend your Cosmos DB to Azure Search with a few clicks right from the portal to allow for full text s
2.
by liamca 11y ago
@Avalaxy, I completely agree with you and I have also taken this set of comments and passed it on to the MSDN team.
3.
by liamca 11y ago
[Full disclosure, I work at Microsoft] @an4rchy, I think if you open the page in private mode it will most likely ask you again. If that does not work, feel free to contact me and I can pass on your comments (my email is my HN alias + mic
4.
by liamca 11y ago
[Full disclosure, I work on a service called Azure Search] Very nice site! Since your site is so much based around search, I thought I would pass on a few suggestions based on what I saw. If you happen to be using a search based engine for
5.
Using Azure Search with D3.js to Build Interactive Data Visualizations(azure.microsoft.com)
2 points by liamca 11y ago|0 comments
6.
by liamca 12y ago
tkmcc is correct, the other big area that people typically want is the ability to easily tune their search results. For example, you might want to give more weighting (or boost it higher in the search results) to an item if the search text
7.
by liamca 12y ago
arafalov, The purpose of starting with this "Simple query syntax" was to try to keep things as simple and straightforward as possible for both the developer and the users of search. We have only exposed the query syntax that we h
8.
by liamca 12y ago
tmarman, It is agreed that the jump from $0 to $125 (preview pricing) is a large jump and I can say we are definitely considering something in the middle ground. I am curious, what types of features would you be willing to give up for a lo
9.
by liamca 12y ago
tracker1, I hear you on this and to add another justification for the need for openness, let me give you another example. With ElasticSearch there are some amazing tools that are available. A few that come to mind are Kibana and LogStash.
10.
by liamca 12y ago
ChuckMcM, you are absolutely right. Nailing down QPS rates are an incredibly tough thing. Not just for Azure Search but also for most Search engines that I am aware of. Things like #'s of facets, complexity of queries all play a par
11.
by liamca 12y ago
Yes, the core of Azure Search leverages ElasticSearch. It does however have an API layer on top of ElasticSearch.
12.
by liamca 12y ago
Hi ChuckMcM, I'm a Program Manager on the Azure Search team. I am going to correct your numbers a bit. Even though you can have a maximum number of 36 search units, the number of partitions you can create (currently) is 12. Partitio
13.
by liamca 12y ago
Hi blutoot, I am a Program Manager for Azure Search, so you will have to take this response as perhaps being a little ones-sided. I think you will find that getting elastic search up and running in Azure to be very easy. As to your point
14.
by liamca 12y ago
Hi MichaelGG, I am a Program Manager for Azure Search and as curiousDog mentioned, yes along with DocumentDB, we also announced Azure Search which is a PaaS based full text search service. We actually leverage ElasticSearch at the core of
15.
by liamca 12y ago
Hi ryanburk, I am a Program Manager for the Azure Search team. I am glad to hear you think our service looks promising. You are right about searching across indexes. This is something we heard often from a number of customers we worked w