daniellavrushin / linqtosolr Goto Github PK

How do you see to implement "soft commit" in AddOrUpdate and Delete methods?

@DanielLavrushin How can I get facets with count?
I'm able to get only facets using GroupByFacets on LinqToSolrQueriable

Hi

So glad you created this library. The other two are way too heavy, and this is exactly the way it should be done.

Are there any plans to support query time joins? Something that also supports joining across cores, like in this example: https://stackoverflow.com/questions/12665797/is-solr-4-0-capable-of-using-join-for-multiple-core

Just curious, because I see that your webclient has async code: Are there any plans to implement something like Entity Framework's ToListAsync?

Hello, I need some advice on LinqToSolr since I've some question specific to a solr url...it's possible to contact you somehow?
Thanks

One can store complex json objects in string fields. Using the [json]-transformer when querying fl=myField:[json] will return what's in that field as actual json. It's not searchable by Solr though, so such a field will always have indexed="false" stored="true". Wouldn't it be cool if your linq provider was able to detect that one is requesting a complex json object stored as a string in Solr and return that? An even cooler feature would be in-memory filtering of those objects, so a query like

...Where(x => x.SimpleString == "val" && x.ComplexObject.NestedString == "otherval")

is turned into something that first queries Solr, myindex/query?q=SimpleString:val and then does a .Where(x => x.ComplexObject.NestedString == "otherval") on the result in memory

Here's a client that handles serializing/deserializing complex objects

I'm testing LinqToSolr and it looks promising for our purposes. However, there is one small issue (so far) that I had to change the code for. In LinqToSolrService.PrepareQueryRequest, you have /solr/ hard-coded in the path. This causes a 404 for us because our paths look like this http://this.that.com/poolname/collectionname/select. Can you make that hard-coded value some sort of optional value?
Thanks!

Any reason why you disable the HttpBasicAuthenticator in the LinqToSolrService.cs as below:
if (!string.IsNullOrEmpty(Configuration.SolrLogin) && !string.IsNullOrEmpty(Configuration.SolrPassword)) { // Client.Authenticator = new HttpBasicAuthenticator(Configuration.SolrLogin, Configuration.SolrPassword); }