Extra Inputs to Pipeline - apache-beam

We are trying to build an application using BEAM as our transformation API. Currently we are running in an issue, and would appreciate if someone can point us to in the right direction.
Here is our use case.
1. We are processing a file, which needs to call the database and then replace the value with the key. This code works fine.
2. We have some business logic where if asked for cached, then we should load the complete key/values in a map and provide it to the PCollection. This is where we are struggling.
We would really appreciate, if you someone could guide us in the right direction.
If this is not the correct forum could you please let us know where we can post such questions.
Thank you

Related

Is there anyway to find which user contribute to an Anylogic model?

I have an Anylogic model to test. There are some problems about the execution of the model. I want to find the person who made some parts of the model to get a right solution from him/her. Is there any way to find, which user made which part? I couldnt find any relative part in the program.
Best Regards,
what do you mean? You have a model that was done by a team and you want to know who did what code in the model so you go and speak to them directly ? Or you have a resource in your model that works a part (agent) and you want to have an assessment on what did each resource work on?
for the first option:
you can't unless everybody puts their names in the code and descriptions indicating what they changed or if you use a version control tool such as GIT
For the second option:
your question is a bit too broad... but what you can do to verify your model is to use the execution log, which will tell you what resource worked on what parts and for how long.
you turn your execution logs clickin in the database in your projects tab, in the database properties in the log section."Log model execution"
After that you want to check the resource_unit_states_log, which has all the information on what each one of your resources did in details, which answers your question.
There are other ways, but this will be the answer :)

In my MERN stack application, after sending a post request, why is "res.status(200).json(data)" working but only doing "res.json(data)" did not?

In my MERN stack application, after sending a POST request to my route, I handle it and save an object to mongo. When I was using .then(data => {res.json(data)}) I was getting an empty {} object as a response and nothing was saving to mongo. This seems to be in the express documentation as valid though? This was also in two tutorials I watched where a bunch of people seemed to get their project working and no one mentioned this as a sticking point in the comments. But I had to hunt down .then(data => {res.status(200).json(data)}) and then the POST request would return my object and it would then show up in mongo. Im using mongoose btw. Im not sure if that is important to say. Both times I received a 200 response however the second code was the only one that made my object appear in mongo atlas. Please please help me know why the bottom code with .status(200) worked while leaving this out did not. It's muddling my mind. This is my first time asking a question on here so any answers that are in the form of a question, please don't answer. If this is not enough information for you to go from, please respectfully ignore this post and move on. Yes I have tried to find other information on this. If you have found some that I havent, please respectfully post sources and dont close this question incase it helps others doing beginner tutorials. We have to start somewhere and of course wont be as good at finding resources as those who have been coding for years. Thank you again though to all for constructive answers :)

How to use DevOps Library variable groups in App Service

As I heard, one can really use the Library values in one's app. But all documentation around this topic is incomplete or really wrong, I cannot make up how!
We already tried mapping the values into a JSON object in our .yaml pipeline and defining them in "Configuration" of the App Service. But nothing will make these variables/groups available in our app. They should be loaded by (Microsoft.Extensions.Configuration.IConfigurationBuilder) .AddEnvironmentVariables(); as I read. But so far none of them arrive in the app, but a hundert of others that I never defined anywhere do...
Can anyone tell me if this is really possible or some step missing or so? Thank you very much in advance!

Is it possible to assign a phone number to a server without a third party tool?

I have been planning a long-term development project and a major requirement for the project is to be able to have a server receive text messages.
I know about services such as Twilio and Plivo, but I'm wondering if there's another way to create this functionality without going through a paid service.
I guess a good starter question would be: How do Twilio and Plivo do it and is there some sort of way I can recreate this myself?
I am willing to do all the research and studying necessary to figure it out, but I'm not sure where to start.
If anyone can lead me in the right direction or give me some sort of insight on this, I would appreciate it. Thank you.

API AI Recognise Infinitely varying reference

My Issue
Im currently working with API.AI for an chat bot system. Im coming up against an issue where I need to be able to recognise a booking reference in a string of text.The problem that I am having is that this booking reference has no real pattern to it, they are generated at random. But are always 5 chars long, for example ABC12.
Current Attempt
I've given API.AI examples (as an entity) of how these can look, and have switched on Automated Expansion. In my intent I have then given examples of how a user may structure these for example 'My booking reference is ABC12' and denoted where the booking reference can be found.
How ever many examples I give it just doesn't seem to recognise this. Have I done something wrong / am I missing something?
Any help would be much appreciated.