Update tables env after have been register them

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Update tables env after have been register them

Andres Angel
Hello everyone,

My use case assume that we execute a job where we load from Redis few data and turn it into DS to register them as tables.

But, it's possible that after have completed this step the data might change and we may need to read again the data to keep the tables content up to date. Here is where our doubt comes up. We need to know whether or not is possible within a job reload the tables information after certain time frame frequently without restart the job and have to register again the tables from the beginning.

I appreciate your comments and the way we could approach this use case. 

Thanks so much

Reply | Threaded
Open this post in threaded view
|

Re: Update tables env after have been register them

Zhenghua Gao
What do you use the data(from redis) for? 
If it's used for driving computation, a Redis source is what you need, but not support now[1].

If it's used for lookup something by keys, you can implement a TableFunction to fetch records from redis, 
or you can take a look at LookupableTableSource of the coming release 1.9.0[2].



Best Regards,
Zhenghua Gao


On Thu, Aug 15, 2019 at 9:55 AM Andres Angel <[hidden email]> wrote:
Hello everyone,

My use case assume that we execute a job where we load from Redis few data and turn it into DS to register them as tables.

But, it's possible that after have completed this step the data might change and we may need to read again the data to keep the tables content up to date. Here is where our doubt comes up. We need to know whether or not is possible within a job reload the tables information after certain time frame frequently without restart the job and have to register again the tables from the beginning.

I appreciate your comments and the way we could approach this use case. 

Thanks so much