-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lucene query throws ArgumentException while having taxonomy field #16691
Comments
Please steps to reproduce |
@effapp I am guessing you are using the latest preview. Correct? Please share the Widget-ContentFeedByTaxonomy.cshtml code. and your parts. I am guessing in your |
Hi @MikeAlhayek , I am using release 1.8.4 of OC. It can execute correctly while replacing from lucene index and query to ElasticSearch index and query. A pieces of code as follows: var queryParams = new Dictionary<string, object>() { { "size", fetchCount }, { "from", from } }; |
There this isn't the line that is causing the exception. Are Another thing to try, is to try upgrading to OC 2.0 preview and see if you encounter the same issue. In 2.0 Newtonsoft.Json was removed from OC and YesSql. |
But there is not the issue in index and query of ElasticSearch, still using Newtonsoft.Json. |
The lucene query can execute correctly in admin UI but throw exception by calling code : "var items = await Orchard.ContentQueryAsync(query, queryParams);" the code "var items = await Orchard.ContentQueryAsync(query, queryParams);" is correctly in elasticsearch query. |
The cause of issue has been identified: deleting "filter:[]" from query scripts is normal. |
Describe the bug
Lucene query throwed the ArgumentException while having toxonomy field
OrchardCore throwed the ArgumentException: "Can not add property ArticleItemForPublic.Category.Inherited to Newtonsoft.Json.Linq.JObject. Property with the same name already exists on object" when it executed lucene query that include taxonomy field index.
Orchard Core version
1.8.4 and 1.8.3
The text was updated successfully, but these errors were encountered: