GitHub user joemeszaros opened a pull request:
https://github.com/apache/nifi/pull/92
NIFI-988: PutDistributedMapCache processor
There is a standard controller service, called DistributedMapCacheServer,
which provides a distributed cache, and an associated
DistributedMapCacheClient
Github user markap14 commented on the pull request:
https://github.com/apache/nifi/pull/92#issuecomment-142647457
@joemeszaros Can you explain the use case here a little bit more? The
DistributedMapCache services were originally developed in order to be used in
the DetectDuplicate pro
Github user joemeszaros commented on the pull request:
https://github.com/apache/nifi/pull/92#issuecomment-142654373
I have several tracking event files, containing user interactions, e.g.
user.x liked item.y in the following format:
|UserId | Action | ItemId |
|
Github user markap14 commented on the pull request:
https://github.com/apache/nifi/pull/92#issuecomment-142689586
OK so to make sure that I am understanding the use case. The idea is just
to use this processor to put data into this cache, so that other custom
processors can access the
Github user joemeszaros commented on the pull request:
https://github.com/apache/nifi/pull/92#issuecomment-142863157
Yes, you are correct.
The PutDisributeMapCache processor relies on the existing
DistributedMapCacheServer, which internally use
org.apache.nifi.distributed.ca
Github user joemeszaros commented on the pull request:
https://github.com/apache/nifi/pull/92#issuecomment-143226518
I started to implement nifi-tools, including a very simple map cache
client. You can find the project on my github page
[here](https://github.com/joemeszaros/nifi-tools
Github user joemeszaros commented on the pull request:
https://github.com/apache/nifi/pull/92#issuecomment-144332289
@markap14 Did you get a proper answer for your cache related questions? If
you do not have any concern with this new processor, it would be reasonable to
implement the
Github user markap14 commented on the pull request:
https://github.com/apache/nifi/pull/92#issuecomment-144378199
@joemeszaros the concern that I have with the notion of the
ExtendedDistributedMapCacheClient is that once that is released, it will have
the same caveats as the Distribut
Github user joemeszaros commented on the pull request:
https://github.com/apache/nifi/pull/92#issuecomment-144703463
I think your answer is related to an other pull request #94 (NIFI-989). Let
me share my opinion there, not in this PutDistributedMapCache PR.
---
If your project is se
Github user markap14 commented on the pull request:
https://github.com/apache/nifi/pull/92#issuecomment-144783590
Sorry, you are right - I posted to the wrong PR. Will re-post this comment
on the other one for clarity. Thanks!
---
If your project is set up for it, you can reply to th
Github user joemeszaros commented on the pull request:
https://github.com/apache/nifi/pull/92#issuecomment-149458834
@markap14 Do you have any concern with this new processor? It is still open
for a while and it would be grateful, if we could finish it by merging or
closing the PR.
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/92
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled
Github user markap14 commented on the pull request:
https://github.com/apache/nifi/pull/92#issuecomment-149919219
@joemeszaros I very much appreciate the contribution back to the NiFi
community. Very sorry it took so long. I have now merged it into master.
Thanks again!
-M
Github user joemeszaros commented on the pull request:
https://github.com/apache/nifi/pull/92#issuecomment-150028829
Thanks for merging!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this f
14 matches
Mail list logo
