Jorge Arbelaez
- Total activity 19
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 2
- Subscriptions 8
Activity overview
Latest activity by Jorge Arbelaez-
Jorge Arbelaez created a post,
Error JDBC store - Metadata already exist
Hello. I'm trying to insert data to a table in snowflake and I'm getting the following error: Unexpected error occurred during processAll while running the node: java.lang.IllegalArgumentExceptio...
-
Jorge Arbelaez created a post,
Connection with Dynamo db (AWS)
Hello community. Can you tell me if is possible to connect to Dynamo DB using the JDBC node. I'm trying to find a jar suitable for this but haven't had any luck finding something that can support ...
-
Jorge Arbelaez commented,
Hey @Adrian Williams, What does the reference LAE-7888 means? is there road map defined in which we can view what are the future functionalities that your team is working on? Kind regards
-
Jorge Arbelaez commented,
Hi Don. How was the process to import the library? we also have a few graphs that use the accelerator nodes. Kind regards
-
Jorge Arbelaez created a post,
Add Accelerator base library from LAE to Data3Sixty
Hello guys. can you tell me if is possible to add the accelerators library that exists in LAE to be used in Data3sixty?? KInd regards
-
Jorge Arbelaez created a post,
Error when deleting and input node from a composite
Hi Guys. I've encounter this error a few times when trying to delete an input node from a composite. Message: Handler dispatch failed; nested exception is java.lang.StackOverflowError Error...
-
Jorge Arbelaez commented,
Hi Mario I tried the scenario of replicating the same issue in the main data flow and i still get the same Warning (image attached). In regards to the clocks, I don't have clocks dependencies linke...
-
Jorge Arbelaez commented,
Hi Mario! yes! the concrete situation in which i'm right now is the following scenarios: 1. When i use as an input the same source for a JDBC query Node ( to execute 2 different queries but with th...
-
Jorge Arbelaez commented,
I found the same error when trying to execute a node which it's source is the same for different nodes. The work around that I found was to re-execute the nodes at the same time, but I don't think ...