Fix for #90 - introducing support for the SOLR-ExtractionHandler #109
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…is kind of file through the github web interface ever again ;)
…gestion in issue lbdremy#85 Merge branch 'v0.3.x' into v0.3.x-patch85 - resolving minor conflict in package.json introduces test/config and overwrite possibility on CLI via figc Readme explains how to use it.
…urable test settings
… exists in the schema and adding the extra returned data to compare
Conflicts: package.json
First stab at it, including the test suggested in https://wiki.apache.org/solr/RealTimeGet
Conflicts: package.json
…0.3.x-alternative83
Making it not-conflicting with the lbdremy#88 implementation by renaming get --> handleGet() Adding the handlePost to complete the use-case behind this Not returning self but rather the request since that seems the standard pattern in v0.3.x
Conflicts: test/core-query-test.js test/group-query-test.js test/mlt-query-test.js
Conflicts: lib/solr.js
…ts and test-files to use
Conflicts: lib/solr.js package.json
…ame (some version between 3.3 and 4.9) So making that optional to include!
…index. Completes the work on lbdremy#90
Introducing json-bigint to properly handle the too-big-number issue in classic json parsing. Adding the test-cases that show the need for this in regular solr fields of type long (_l suffix) and the fact that the solr 4.x optimistic locking feature (ie the _version_ field) needs this badly. Caveat: json-bigint is currently more restrictive on json parsing then the classic JSON.parse Namely: it renders an error on duplicate key fields in the json. Since the response-header of the ping in solr introduces such a duplicate key this commit chooses to force omitHeader=true for the ping request. This can be reconsidered if json-bigint would allow for a more lenient parse() in line with the classic one.
… in json-bigint we can re-introduce the headers in the ping response and return to the classic assertion scheme in the ping-tests. This should nicely roundup issue lbdremy#71.
Usage:
var client = solr.createClient({ secure : true});
…it, realTimeGet, spell}.
Manually handled Conflicts: lib/solr.js package.json test/bigint-test.js
…h the signature of createAddStream() - changing the test to use the new signature as sample. Switch to using the https support recently introduced in v0.3.x
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Including tests and updated test-material.
Thx for considering this.