Ayende @ Rahien

Ayende Rahien commented on Raven’s dynamic queries

Sun, 31 Oct 2010 13:32:07 GMT

And it would be better to have this discussion in the mailing list

Ayende Rahien commented on Raven’s dynamic queries

Sun, 31 Oct 2010 13:31:46 GMT

BrightSoul, Use LuceneQuery(of Object) for now, it should respect the JObject / dynamic, but it doesn't at the moment.

BrightSoul commented on Raven’s dynamic queries

Sun, 31 Oct 2010 13:29:02 GMT

Thanks, Ayende, for such a quick response! I still don't get it thought, hehe :D Sorry to bother you... I think I need a line of code to understand. LuceneQuery is generic method, so I still have to provide a type, which I can't do. Assuming I have to retrieve all the Orders from Italy, I would do the following: session.Advanced.LuceneQuery(Of Order)().Where("Country:Italy") But "Order" is a type that doesn't exist in my application. The domain model is actually in another application I know nothing about. Then, I gave it a shot trying JObject as the type. session.Advanced.LuceneQuery(Of JObject)().Where("country:Italy") But as expected, this query didn't return any result since I couldn't instruct it that my documents are inside docs.Orders. The following is the content of the temp index that's being created: Temp/JObjects/ByCountry from doc in docs.JObjects select new { Country = doc.Country } Correct me if I'm wrong but, the AbstractIndexCreationTask is generating the frament "docs.JObjects" looking at the Type name, pluralized. What I need here is the ability to use a string (ie. "docs.Orders"), not a type, to instruct the index creator where my documents exactly are.

BrightSoul commented on Raven’s dynamic queries

Sun, 31 Oct 2010 12:17:16 GMT

uhm, angled brackets are not htmlencoded... just to clarify on my previous comment, I meant IRavenQueryable(Of JObject) as the return type of the DatabaseCommands.Query overload; and session.Query(Of Type) as the method I can't use.

Ayende Rahien commented on Raven’s dynamic queries

Sun, 31 Oct 2010 12:16:03 GMT

BirghtSoul, You can use Advanced.LuceneQuery to do so

BrightSoul commented on Raven’s dynamic queries

Sun, 31 Oct 2010 12:07:14 GMT

Hello, this is awesome stuff, but can I leverage dynamic queries If I don't have server-side entities? You see, I'm working with JObjects, storing and retrieving them with DatabaseCommands.Put and DatabaseCommands.Set. session.Query

Ayende Rahien commented on Raven’s dynamic queries

Sat, 23 Oct 2010 17:48:04 GMT

scooletz , Yes, there are already there.

scooletz commented on Raven’s dynamic queries

Sat, 23 Oct 2010 16:05:18 GMT

Finally! Will you provide some kind of strategies, which can be used to configure Raven to determine a lifespan of a created temporary index?

Steve Gentile commented on Raven’s dynamic queries

Sat, 23 Oct 2010 01:03:19 GMT

Great stuff Ayende - I really like seeing how Raven is maturing

Peter Morris commented on Raven’s dynamic queries

Wed, 20 Oct 2010 21:01:00 GMT

That's what I suggested in the first place, why are you arguing with me? :-)

Ayende Rahien commented on Raven’s dynamic queries

Wed, 20 Oct 2010 20:57:45 GMT

Jakub, Yes, you can do that using Lucene as well

Ayende Rahien commented on Raven’s dynamic queries

Wed, 20 Oct 2010 20:57:20 GMT

Peter, We didn't take away indexes, they are still there. We are simply giving the option to query without an index and have that done in an efficient manner. As for querying without an index, you can do that too, with no index created. Not really useful, to tell you the truth, but you can

Ayende Rahien commented on Raven’s dynamic queries

Wed, 20 Oct 2010 20:55:57 GMT

Stevo, Yes, there is the OEM licensing.

josh commented on Raven’s dynamic queries

Wed, 20 Oct 2010 18:54:43 GMT

This is the sort of improvement that will keep devs like me interested in the .Net world. Nice Job, Oren & Rob!

Rob Ashton commented on Raven’s dynamic queries

Wed, 20 Oct 2010 18:34:06 GMT

Jakub - yes You can even query collection properties like Tags,Name:Fish Where , denotes that Tags is a collection and Name is the property on the items in the collection you want to query The only difference is that you include the full path to properties you want to query User.Address.FirstLine

Nick Aceves commented on Raven’s dynamic queries

Wed, 20 Oct 2010 17:00:28 GMT

This is probably Raven's single most awesome feature. And that's saying something, because Raven has a boatload of awesome features.

Jakub Borys commented on Raven’s dynamic queries

Wed, 20 Oct 2010 16:39:05 GMT

Will temporary indexes be created for Lucene queries as well?

Rob Ashton commented on Raven’s dynamic queries

Wed, 20 Oct 2010 16:11:29 GMT

Peter - this functionality doesn't prevent people from defining indexes up front, the choice is entirely yours

Peter Morris commented on Raven’s dynamic queries

Wed, 20 Oct 2010 15:58:23 GMT

I think you are missing my point. If there is no index when the query runs then the user is already paying the price, when Raven then indexes the data in the background after the query has run the server pays the extra cost of generating an index that will not be used. I just think it would be wise to *also* let people define indexes.

Stevo commented on Raven’s dynamic queries

Wed, 20 Oct 2010 15:27:09 GMT

Is there any plan on having some sort of royalty-free distribution license (commercial)? Currently the lack of this keeps us from using the software.

Yitzchok commented on Raven’s dynamic queries

Wed, 20 Oct 2010 15:14:33 GMT

Wow this is very cool feature Oren. I think it will help people get into RavenDB much faster.

Ayende Rahien commented on Raven’s dynamic queries

Wed, 20 Oct 2010 14:53:44 GMT

Peter, Because with Raven, those things happen in the background. You aren't paying for indexes. In fact, one of RavenDB users has > 500 users and millions of documents, without any ill effect.

Peter Morris commented on Raven’s dynamic queries

Wed, 20 Oct 2010 14:49:04 GMT

Here are the scenarios as I see them A] Allowing a pre-defined index... Inserts/updates/deletes on that table take a little longer, but the large infrequent query is very fast. B] Not allowing a pre-defined index... Inserts/updates/deletes on that table are a bit quicker, but the large infrequent query is much slower because it is running off unindexed data. An index is also created in the background which will never be used. Why I am wrong?

Ayende Rahien commented on Raven’s dynamic queries

Wed, 20 Oct 2010 14:44:08 GMT

Not really, no. Work is done on the background, so you aren't really paying all that much for it. Especially since in Raven, readers don't block the writer. And you CAN do an effectively unidnexed query with Raven, if you want.

Richard Wilde commented on Raven’s dynamic queries

Wed, 20 Oct 2010 14:16:27 GMT

@Ayende - waiting for the "first page to be filled" answers my query. I understand the staleness versus fresh debate and have no problems with it

Peter Morris commented on Raven’s dynamic queries

Wed, 20 Oct 2010 14:13:14 GMT

I'm not sure why you would think that. If this query runs once per month and returns data from a table with millions of rows that match a specific criteria then it is going to have to read all rows to create the indexes and then select the data, this would be slower than just selecting without the index there at all; especially as the index will then be dropped before the query is run again next month.

Ayende Rahien commented on Raven’s dynamic queries

Wed, 20 Oct 2010 14:10:39 GMT

Peter, Actually, no. It is BETTER to make this a temporary index, because after a while, it gets cleared out, and doesn't takes resources. And indexing is always done on the background, anyway.

Peter Morris commented on Raven’s dynamic queries

Wed, 20 Oct 2010 14:08:09 GMT

Oren: If this is a massive query that is run once per month for example as a payroll processing task then the app is really going to suffer isn't it?

Ayende Rahien commented on Raven’s dynamic queries

Wed, 20 Oct 2010 14:06:25 GMT

Peter, 1) Not really, no. We actually recommend using the dynamic indexes by default, and letting RavenDB do that for you. Defining indexes yourself if for more complex issues. 2) You are talking about sparse indexes, and that is an implementation detail for the DB.

Ayende Rahien commented on Raven’s dynamic queries

Wed, 20 Oct 2010 14:01:31 GMT

Richard, That is the fun with RavenDB's stale-by-default. Yes, it may take a while, but you know that because the answer is stale so you can either wait for it to be non stale or use the potentially stale results.