lessless
I have this challenge of importing (downloading and saving) paginate data.
Currently I’m doing it recursively in a workflow step and I think it’s safe because if it will crash (f. ex. due to remote api error).
I designed this code to resume from the last known transaction on the first fetch, so it should also resume from the last saved transaction in a case of a crash
def insert(account_id) do
Workflow.new()
|> Workflow.put_context(%{account_id: account_id})
|> Workflow.add_cascade(:trigger_sync, &trigger_sync/1, queue: :transactions_sync)
|> Workflow.add_cascade(:import, &import_txs/1,
deps: [:trigger_sync],
queue: :transactions_sync
)
|> Oban.insert_all()
end
def import_txs(%{account_id: account_id}) do
account = BankAccount.by_id(account_id)
import_txs(account.finexer_id, account)
end
def import_txs(%{paging: %{next: nil}}, _account) do
:ok
end
def import_txs(source, account) do
{:ok, txs_resp} = download_transactions(source, account)
{_, _} = save_transactions(txs_resp, account)
import_txs(txs_resp, account)
end
def download_transactions(finexer_id, account) when is_binary(finexer_id) do
APIClient.account_transactions(finexer_id, [{:"timestamp.gte", Transaction.account_checkpoint(account_id)}])
end
def download_transactions(txs_resp, _account) when is_map(txs_resp) do
APIClient.account_transactions(txs_resp, :next_page)
end
defp save_transactions(txs_resp, account) do
txs_resp
|> Map.get(:data)
|> Transaction.bulk_import(account)
end
As a matter of curiosity I wonder if workflows design can support replacing downloading paginated data by dynamically adding jobs.
For example import_txs can import first page, check if there is more (txs_resp.page.next != nil) and then schedule next job with %{source: txs_resp.page.next} as an argument.
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
Hey guys,
I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly
Do you guys have any suggestions what is the best prac...
New
Kia ora,
We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I have what I’ve heard referred to as a “lookup table” in my database. This is a way of assigning codes to common values. One common lo...
New
Hello,
I’m developing a online persistent chat system (what’s app) like using elixir/dynamodb/aws for a mobile app(flutter).
The diffic...
New
What approach to take when sending live updates to “random” users Hi! I have a question, I have a little chat app, and when I create a DM...
New
Other Trending Topics
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
There are three potential reasons for members of this forum to have a look at https://vutuv.de
You are tired or annoyed of LinkedIn.
Yo...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #iex
- #elixirconf-us
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming











Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
sorentwo
That design should work. There’s no “finished” state for a workflow, so you can always append another job. Did you give that a try?
lessless
I haven’t yet. I just don’t have enough understanding of Oban to put together a working solution.
I guess the shortest path to that would be to call
add_cascadeinstead ofimport_txsinsideimport_txs/2.So the last function would import the current page and schedule the next job. But how do I pass
txs_respto the next job?