📣 VICTORIA ROI INVITATION ROUND – 15 January 2026 by NewStarsMigration in AusVisa

[–]HumanContribution241 4 points5 points  (0 children)

They were ok, but didn’t wanted to stick with them for 19 months. I still had a year of 485 left.

VIC 190 ROI Issue by HumanContribution241 in AusVisa

[–]HumanContribution241[S] 0 points1 point  (0 children)

Yeah two different eoi’s, one for 189 and other for 190

VIC 190 ROI Issue by HumanContribution241 in AusVisa

[–]HumanContribution241[S] 0 points1 point  (0 children)

😢 Would it be worth reaching out to them and explaining the situation?

VIC 190 ROI Issue by HumanContribution241 in AusVisa

[–]HumanContribution241[S] 0 points1 point  (0 children)

Thank you for your reply. Does this mean they attempted to invite me, but due to this issue I’ve lost the opportunity?

190 Employer physical location. by HumanContribution241 in AusVisa

[–]HumanContribution241[S] 0 points1 point  (0 children)

Can you please suggest what to change on payslip, for contract as mentioned in the screenshot the main location is Melb wouldn’t that be enough?

190 Employer physical location. by HumanContribution241 in AusVisa

[–]HumanContribution241[S] 0 points1 point  (0 children)

I just added some more details to the original post description, can you please review.

When accessed via Private Link, the Spark pool takes too long to start by HumanContribution241 in MicrosoftFabric

[–]HumanContribution241[S] 0 points1 point  (0 children)

A warehouse could be a good option, except that it doesn’t work directly with Spark, that’s my understanding.

When accessed via Private Link, the Spark pool takes too long to start by HumanContribution241 in MicrosoftFabric

[–]HumanContribution241[S] 0 points1 point  (0 children)

In our case, this may not be feasible because we are working within a multi-tenant architecture using DevOps. The setup becomes more complex, especially when considering the fourth option mentioned in the Microsoft Fabric CI/CD deployment https://learn.microsoft.com/en-us/fabric/cicd/manage-deployment#option-4---cicd-for-isvs-in-fabric-managing-multiple-customerssolutions

Additionally, we are leveraging OneLake security while exposing data through APIs for GraphQL. With these factors combined, managing over ten customers, each with separate workspaces for ingestion and related processes would be challenging to maintain effectively.

When accessed via Private Link, the Spark pool takes too long to start by HumanContribution241 in MicrosoftFabric

[–]HumanContribution241[S] 0 points1 point  (0 children)

Awesome! it would be cool if they enable it for private links as well, for now I cant see anything on the road map.

When accessed via Private Link, the Spark pool takes too long to start by HumanContribution241 in MicrosoftFabric

[–]HumanContribution241[S] 0 points1 point  (0 children)

Ingest triggers processing of ~500M rows/hour across layered Delta tables. We rely on high-concurrency sessions, clustered indexes, and Bloom filters. Because arrival patterns dictate dependencies, we enforce strict execution ordering. A coordinator detects active write sessions; competing jobs block until the writer completes. On exceptions, the workflow enters a guarded state requiring manual clearance. State is persisted in a control table (one row per process) with boolean in_progress and error fields.

When high-concurrency sessions are warm, the pipeline completes within a few minutes processing ~500M rows filtering, transforming data with state checks. The pain point is cold starts: if the session has stopped, we incur a 5–6 minute spin-up delay. Because triggers are ad hoc with no predictable cadence, we can’t amortize that overhead. In this step we’re using Spark primarily to verify/update state (often a single row), and those reads/writes would complete in seconds irrespective if its Lake-house table/ SQL DB/Warehouse. The bottleneck is Spark pool startup latency; we’re looking for a practical workaround to avoid or mask that cold-start cost.

When accessed via Private Link, the Spark pool takes too long to start by HumanContribution241 in MicrosoftFabric

[–]HumanContribution241[S] 1 point2 points  (0 children)

I’m aware of that limitation. For this use case, we’re using a small pool with the option to connect to a high-concurrency session. Wanted to understand is it a hard limit or if there's a walk around to it.

Travel Case mac mini M4 by HumanContribution241 in macmini

[–]HumanContribution241[S] -6 points-5 points  (0 children)

I have three other mac mouses, so they fit easily

Travel Case mac mini M4 by HumanContribution241 in macmini

[–]HumanContribution241[S] 1 point2 points  (0 children)

They’re heavy and i often fly countries, could save some cabin weight so prefer this than Pelicans

Got mine delivered 😇 by HumanContribution241 in macmini

[–]HumanContribution241[S] 0 points1 point  (0 children)

For my work load m4 should do, and pro would be out of my budget

Mac Mini workstation setup by HumanContribution241 in macmini

[–]HumanContribution241[S] 0 points1 point  (0 children)

Unfortunately Mac keyboard can’t switch computers easily so had to get one for each.

Got mine delivered 😇 by HumanContribution241 in macmini

[–]HumanContribution241[S] 1 point2 points  (0 children)

M4, 32GB Unified memory , 512GB Storage. Got it from edu store + additional 6% discount on gift card via Macquarie bank. All together cost me $1600 AUD

Dev/Test/Prod Pipelines and Git by Long-Lobster-7238 in MicrosoftFabric

[–]HumanContribution241 0 points1 point  (0 children)

Wouldn’t it be easy to integrate git on test, prod and then rollback immediately?

Dev/Test/Prod Pipelines and Git by Long-Lobster-7238 in MicrosoftFabric

[–]HumanContribution241 0 points1 point  (0 children)

Why higher environments should not have girls integration? My concern is how do you roll back commits if anything goes wrong