lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shad Storhaug (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENENET-565) Port Lucene.Net.Replicator
Date Wed, 28 Jun 2017 09:45:00 GMT

    [ https://issues.apache.org/jira/browse/LUCENENET-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066226#comment-16066226
] 

Shad Storhaug commented on LUCENENET-565:
-----------------------------------------

Thanks Jens.

{quote}this is only for a single public method... Namely the ReplicationService.Perform(request,
response) method...{quote}

While that is how it was implemented in Java, it would probably make more sense to make the
"action constants" into action methods. If you look at the documentation (https://lucene.apache.org/core/4_8_0/replicator/org/apache/lucene/replicator/http/ReplicationService.html),
the URLs are like {{/<context>/<shard>/<action>}}. Therefore, in AspNetCore,
I would translate that into {{"/\{context\}/\{shard\}/\{action\}"}} with the 3rd URL segment
mapping to one of 3 different action methods (obtain, release, update) to have better separation
of concerns.

{quote}I did however run into another road-block as I was so Insane to update Visual Studio
2017 to the newest version the other day, which now means I can't build anything as it all
complains about the project.json files...{quote}

Unfortunately, Microsoft has left us a choice between VS 2015 and VS 2017 with no way to support
both. Also, there are versioning issues with the new .csproj format that I haven't found a
workaround for - namely, for pre-release versions (4.8.0-beta00004) it uses full release versions
for the project dependencies (4.8.0). It works fine in .NET Core by "downgrading" to the latest
pre-release, but for older versions of NuGet (for .NET Framework), it doesn't work.

Suffice to say that for the time being all .NET Core/.NET Standard work on Lucene.Net must
be done using VS 2015. But fortunately VS 2015 and VS 2017 will run side-by-side on the same
machine.

> Port Lucene.Net.Replicator
> --------------------------
>
>                 Key: LUCENENET-565
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-565
>             Project: Lucene.Net
>          Issue Type: Task
>          Components: Lucene.Net.Replicator
>    Affects Versions: Lucene.Net 4.8.0
>            Reporter: Shad Storhaug
>            Priority: Minor
>              Labels: features
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message