Build 1.0.4 of nhaystack fixes the "->" operator in filter queries so that there is no longer a stack overflow. There are a couple of minor refactorings in this build as well.
You can get the build from the bitbucket downloads page.
I guess rollups in niagara would be mapped to BQL but the rest call for this is evalAll in SkySpark. Niagara version this would need more enhanced nhaystack driver right?
Mike JarmyThu 29 Aug 2013
NHaystack does allow for querying via the standard haystack Filter mechanism, but for what you are describing, yes, nhaystack would need to be enhanced.
Mike Jarmy Thu 4 Jul 2013
Build 1.0.4 of nhaystack fixes the "->" operator in filter queries so that there is no longer a stack overflow. There are a couple of minor refactorings in this build as well.
You can get the build from the bitbucket downloads page.
For developers: the fix is actually down in haystack-java. Brian has already merged my pull request, so you can get the fix at https://bitbucket.org/brianfrank/haystack-java
Alper Üzmezler Wed 28 Aug 2013
Is there going to be evalAll functionality in NHaystack driver?
Do we have to extend the driver ourselves to have that functionality?
Mike Jarmy Wed 28 Aug 2013
Can you describe what you mean by evalAll?
Alper Üzmezler Wed 28 Aug 2013
We make a call for example.
ver:"2.0" expr "readByIds([195f7df3-63d67f7c,195f7df3-80c0ca2d,195f7df3-81c840b1]).toPoints.hisRead(2013-08-28).hisRollupAuto(15min)"
I guess rollups in niagara would be mapped to BQL but the rest call for this is evalAll in SkySpark. Niagara version this would need more enhanced nhaystack driver right?
Mike Jarmy Thu 29 Aug 2013
NHaystack does allow for querying via the standard haystack Filter mechanism, but for what you are describing, yes, nhaystack would need to be enhanced.