Forum Discussion
This seems like it was an oversight in the design of the LSI Bulk API. The numerical node ID was supposed to be an internal ID that was not to be exposed externally. Unfortunately it looks like it has been exposed via this API. I will certainly raise this with the Product team to see if we can expose a way to look up nodes by their numerical IDs (and/or if we want to change the LSI Bulk API to expose the string-based node ids instead of / in addition to the numerical node ids).
-Doug
DougS wrote:This seems like it was an oversight in the design of the LSI Bulk API. The numerical node ID was supposed to be an internal ID that was not to be exposed externally. Unfortunately it looks like it has been exposed via this API. I will certainly raise this with the Product team to see if we can expose a way to look up nodes by their numerical IDs (and/or if we want to change the LSI Bulk API to expose the string-based node ids instead of / in addition to the numerical node ids).
-Doug
Hi, has this been reported to Product team ? Maybe there is some progress on this?
Related Content
- 9 months ago
- 10 months ago
- 3 years ago
- 2 years ago