Is it possible to extract the functionality into a nuget package?

[richorama]

I was wondering how much of the indexing functionality is in the 'core' orleans code, and how much could be extracted to a packge. It would make this functionality easier to consume if it was an 'optional extra' on top of the core orleans codebase.

[creyke]

Agreed. Maybe the dependent abstractions could be PR-ed into the main Orleans code?

[richorama]

/cc @mdashti

[Arshia001]

Was gonna ask for this just now.

[galvesribeiro]

I was going to look at it once I finish the new telemetry APIs.

The big challenge now is to understand the code and make it injectable thru facets and not depend on a base class.

[philbe]

@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?

@galvesribeiro, yes, it should be made injectable thru facets. We developed the indexing prototype over a year ago, before the decision was made (last January) to refactor the transaction mechanism using injectable facets.

[galvesribeiro]

@philbe Yep, I'll look at it

[mdashti]

@richorama, thank you for bringing up this issue. As @ph1ll mentioned, we had this in our mind from the very beginning. These are three clean commits that should be included in the core:

• 72fd56b
• d4df950
• e4c3479

The rest is completely separated into the OrleansIndexing sub-project.

[philbe]

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

[galvesribeiro]

Ops, my bad @philbe :)

[philbe]

@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 to obtain consistency between grains and indexes using transactions (in place of or in addition to the current workflow protocol).

[jamiemitchellconsultants]

@philbe
If you are still progressing with Indexing, I can offer some time to help even if it is only writing tests, documentation, sample implementations

[philbe]

@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 to run on 2.0. I'll report on the project's status next week.

[KSemenenko]

I'm very interested in this project, let me know if you need any help. @philbe

[philbe]

CC: @TedHartMS (who has taken over responsibility the port to Orleans 2.0)

@KSemenenko, thanks very much for the offer. @TedHartMS is nearly done porting indexing to Orleans 2.0. After we publish that milestone, we can discuss how best you can help. Also @jamiemitchellconsultants, if you're still interested and available.

Next up, we'll replace the base class (IndexableGrain) by facets and then use transactions to obtain consistency between grains and indexes.