Skip to content
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

Need for multi value properties #4

Open
shroffk opened this issue Jun 29, 2015 · 3 comments
Open

Need for multi value properties #4

shroffk opened this issue Jun 29, 2015 · 3 comments

Comments

@shroffk
Copy link
Contributor

shroffk commented Jun 29, 2015

{
  "_index": "cameltest",
  "_type": "pvs",
  "_id": "ZSS5210_LATCH",
  "_score": 1,
  "_source": {
    "updated": "2015-06-09 14:04:54",
    "properties": {
      "type": "bi",
      "fields": {
        "ADEL": null,
        "DESC": "EtherIP channel  BBM-",
        "RTYP": "bi",
        "PREC": null,
        "DTYP": "EtherIP",
        "SCAN": ".2 second"
      }
    }
  }
}
@shroffk
Copy link
Contributor Author

shroffk commented Jan 29, 2016

currently the best way to address this might be to use a naming convention
fields.RTYP = bi
fields.DTYP = "EtherIP"

@ralphlange
Copy link
Contributor

Can you supply a use case for this requested feature?

This is to some point changing the underlying data model, so I would like to have some reasoning.

@shroffk
Copy link
Contributor Author

shroffk commented Feb 25, 2016

Sorry for the lack of clarity.
The above example is the json document put into elastic search by the population scripts developed at FRIB. The multi-value property would ease the mapping.

Additionally there are certain channels which might have properties with multiple values. A example could be a pv that has a property "system" and since it belongs to many systems should have values "linac", "linac-to-booster",...

My comment argued against adding such a feature right now and rather using property/tag naming conventions resolve this issue.
With the migration to the new backend some of the performance concerns associated with a large number of properties and tags should be resolved too.

Cheers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants