Azure Functions Trace 2019: functions changing trigger type?

Open
#39 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure
Domain
data

Research direction

Start with the dataset explanation and the trace records described in the issue; compare function hashes across days where trigger types differ. Done means clarifying whether hashes remain stable across trigger changes and whether identifying functions by hash plus trigger type is supported.

Written by the indexing model from the issue text.

Description

It seems functions can change trigger type between two days. After it changes, the trigger type remains stable.

I identified 1987 functions that change triggers through the traces.

Re-reading the explanation about the dataset, I believe only the names of the function and its owning application are hashed? So if a user changes the trigger type of a function, it does not change its hash? Then, would it be sensible to identify a function by its hash AND by its trigger type?

Dominant language
Jupyter Notebook
Stars
1.2k
Forks
186
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/AzurePublicDataset

All issues in Azure/AzurePublicDataset

Similar issues

More Data Engineering issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.