Phil Bernstein

I agree with @BenjaminGibbs and @gabikliot that a simple mechanism is a good place to start. OTOH, it might be relatively easy to take a bigger step with a storage...

As @sergeybykov says, I've been having some research discussions about this, but I don't expect to have code to share for quite a while. RE: DocumentDB, I presume you mean...

Some query capability can and should be storage-provider agnostic. However, there will be cases where a storage system can execute optimized queries faster than what can be done in the...

We just announced an indexing mechanism for grains here: #3413.

@RehanSaeed, I don't think there's a plan on when to release this in Orleans master. @sergeybykov, care to comment? @TedHartMS has been working with me on a branch that incorporates...

@shlomiw As @sergeybykov says, the (indexing project) does what you need. It runs on Orleans V2 and @TedHartMS is done replacing the inheritance-based API with dependency injection (not sure if...

@richorama There's only a small amount of change to the Orleans runtime. Almost all of it runs at app level. @mdashti, can you please summarize these changes to the runtime?...

FYI, my GitHub username is @philbe, not @ph1ll. It looks like this got started via an autocomplete error by @galvesribeiro.

@Arshia001 @richorama @creyke @galvesribeiro I have started working with a developer to port the indexing system to Orleans 2.0, to replace the base class by facets (i.e., dependency injection), and...

@jamiemitchellconsultants CC: @kirkolynyk, who is doing the port to Orleans 2.0 Thanks for the offer, but we're not far enough along for that -- still working on getting the code...