-
Notifications
You must be signed in to change notification settings - Fork 49
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
ElasticsearchString attribute appears to not work #154
Comments
should be, I'll have a look, which version are you using? greetings Damien |
works with the preview version and Elastic version number": "2.3.1", I checked the mapping and its not analyzed. Maybe an attribute property is no longer supported. hope this helps greetings Damien |
Thanks! Elasticsearch 2.3.1 and was latest version of your code. It's a console application as I have an NServiceBus endpoint handling all elasticsearch updates. That source file returns 404. Which source files should I look at to reimplement this functionality? I saw you've made changes since I've last looked at this. Was any of that related? |
sorry, I've updated to netstandard 1.4. The console app is a demo which uses this. The changes I made are just porting the application to netstandard 1.4, so from version 2.3.3.1 onwards, only net461 or higher is supported. I would like to support net451, but its too much effort testing for both. Greetings Damien |
I use 4.6.1 :) I'll test the console app and if the non_analyzed option doesn't work still I'll use that to try to fix it. Thanks! |
Great, thanks |
I've decorated properties in a few of my classes with [ElasticsearchString(Index = StringIndex.not_analyzed)] on several of my classes, and when they're saved to Elasticsearch, the created index still marks them as analyzed.
Attempted to debug this myself, but could not find where this is checked anywhere in ElasticsearchCRUD. Is this feature not yet implemented?
The text was updated successfully, but these errors were encountered: