: But we don't necessarily need to do it every week, if people feel it is
: noisy. We could disable the bot until we start thinking about a new
: release, and then get a ton of upgrades to merge for the new release.
That feels like it just pushes all of the work, and risk of discovering
Kevin: Even after your fix in pull #1535,
S3BackupRepositoryTest.testCopyFiles seems to be failing regularly on
Uwe's OSX & Windows jenkins nodes w/ the same HTTP read time out
failure...
(Past 24 Hours)
Class: org.apache.solr.s3.S3BackupRepositoryTest
Method: testCopyFiles
Failures: 13.11%
Hi,
Please bear with me if I'm completely lost in the forest. I don't have
much experience with what's currently called "JSON Request API" or "JSON
Facet API" as I'm mostly working on software that uses the (legacy
legacy?) GET request query string API. Which brings me to the point I'd
like
>
> If we're going to push for the JSON-style request DSL as well, do we need
> to come up with a shiny new name for that as well, or will JSON Request DSL
> work? It's basically a HTTP post with JSON instead of
> 'application/x-www-form-urlencoded'...
JSON Request DSL (or just JSON Request
Trying to sum up this discussion.
I agree that V2-facet-api is not so good a name after all.
So we basically have two main suggestions in this thread then:
A) "The Faceting API" and then the need to re-brand "The legacy Faceting API"
B) "The Aggregation API" vs whatever we called it before
Do
