Skip to content

Added blog fpor azure storage and ADLS Gen 2#1432

Open
Adez017 wants to merge 7 commits intorecodehive:mainfrom
Adez017:patch-1
Open

Added blog fpor azure storage and ADLS Gen 2#1432
Adez017 wants to merge 7 commits intorecodehive:mainfrom
Adez017:patch-1

Conversation

@Adez017
Copy link
Copy Markdown
Member

@Adez017 Adez017 commented May 6, 2026

Description

Fixes #1421

Type of Change

  • New feature (e.g., new page, component, or functionality)
  • Bug fix (non-breaking change that fixes an issue)
  • UI/UX improvement (design, layout, or styling updates)
  • Performance optimization (e.g., code splitting, caching)
  • Documentation update (README, contribution guidelines, etc.)
  • Other (please specify):

Changes Made

Dependencies

  • List any new dependencies or tools required for this change.
  • Mention any version updates or configurations that need to be considered.

Checklist

  • My code follows the style guidelines of this project.
  • I have tested my changes across major browsers and devices
  • My changes do not generate new console warnings or errors .
  • I ran npm run build and attached screenshot(s) in this PR.
  • This is already assigned Issue to me, not an unassigned issue.

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 6, 2026

@Adez017 is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

@Adez017
Copy link
Copy Markdown
Member Author

Adez017 commented May 6, 2026

@sanjay-kv

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 6, 2026

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

  1. Get free Consultation use code recode50 to get free: Mentorship for free.

  2. Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.

  3. Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

@github-actions github-actions Bot added in-review The current changes are in review and would need approval and testing before merging level 1 10 points recode this is label for leaderboard labels May 6, 2026
@github-actions github-actions Bot added this to the recode:launch 3.0 milestone May 6, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 6, 2026

✅ Synchronized metadata from Issue #1421:

  • Labels: enhancement, level 1, recode
  • Milestone: None

@github-actions github-actions Bot added the enhancement New feature or request label May 6, 2026
@Adez017 Adez017 requested a review from sanjay-kv May 6, 2026 10:23
@Adez017 Adez017 moved this to In Progress in @recode-web May 6, 2026
@Adez017 Adez017 moved this to Q2 2026 – March-June in Recode Public Roadmap May 6, 2026
@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 6, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
recode-website Ready Ready Preview, Comment May 6, 2026 3:19pm

Copy link
Copy Markdown
Member

@sanjay-kv sanjay-kv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is well written blog, i requested few backlink and image changes.

🔴 One Concern Worth Flagging The sentence structure explaining flat namespace vs. hierarchical namespace closely parallels Ken Muse's 2021 blog post, which explains that in traditional Azure Storage, a file path like "myfolder/myfile.txt" has no real folder underneath — the SDKs merely split on "/" to simulate folder existence. The core idea and even the illustrative example (path with slashes that aren't real separators) match closely. Not verbatim, but structurally similar enough to warrant attribution

Comment thread blog/azure-storage-options/index.md Outdated
Comment thread blog/azure-storage-options/index.md
Comment thread blog/azure-storage-options/index.md
Comment thread blog/azure-storage-options/index.md
Comment thread blog/azure-storage-options/index.md Outdated
Comment thread blog/azure-storage-options/index.md
Comment thread blog/azure-storage-options/index.md
Comment thread blog/azure-storage-options/index.md
Comment thread blog/azure-storage-options/index.md
@Adez017
Copy link
Copy Markdown
Member Author

Adez017 commented May 6, 2026

This is well written blog, i requested few backlink and image changes.

🔴 One Concern Worth Flagging The sentence structure explaining flat namespace vs. hierarchical namespace closely parallels Ken Muse's 2021 blog post, which explains that in traditional Azure Storage, a file path like "myfolder/myfile.txt" has no real folder underneath — the SDKs merely split on "/" to simulate folder existence. The core idea and even the illustrative example (path with slashes that aren't real separators) match closely. Not verbatim, but structurally similar enough to warrant attribution

Didn't got your point on this paragraph

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 6, 2026

✅ Synchronized metadata from Issue #1421:

  • Labels: enhancement, level 1, recode
  • Milestone: None

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 6, 2026

✅ Synchronized metadata from Issue #1421:

  • Labels: enhancement, level 1, recode
  • Milestone: None

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 6, 2026

✅ Synchronized metadata from Issue #1421:

  • Labels: enhancement, level 1, recode
  • Milestone: None

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 6, 2026

✅ Synchronized metadata from Issue #1421:

  • Labels: enhancement, level 1, recode
  • Milestone: None

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 6, 2026

✅ Synchronized metadata from Issue #1421:

  • Labels: enhancement, level 1, recode
  • Milestone: None

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 6, 2026

✅ Synchronized metadata from Issue #1421:

  • Labels: enhancement, level 1, recode
  • Milestone: None

@Adez017
Copy link
Copy Markdown
Member Author

Adez017 commented May 6, 2026

This is well written blog, i requested few backlink and image changes.

🔴 One Concern Worth Flagging The sentence structure explaining flat namespace vs. hierarchical namespace closely parallels Ken Muse's 2021 blog post, which explains that in traditional Azure Storage, a file path like "myfolder/myfile.txt" has no real folder underneath — the SDKs merely split on "/" to simulate folder existence. The core idea and even the illustrative example (path with slashes that aren't real separators) match closely. Not verbatim, but structurally similar enough to warrant attribution

I had wrote the entire section @sanjay-kv , we don't had any risk now .

@Adez017
Copy link
Copy Markdown
Member Author

Adez017 commented May 6, 2026

@sanjay-kv thanks for all the suggestions you had given , i had looked thoroughly into all and resolved all of them . kindly take a look now . for me personally its far above better.

@Adez017 Adez017 requested a review from sanjay-kv May 6, 2026 14:39
@sanjay-kv
Copy link
Copy Markdown
Member

It's good.

@sanjay-kv
Copy link
Copy Markdown
Member

thanks this is perfect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request in-review The current changes are in review and would need approval and testing before merging level 1 10 points recode this is label for leaderboard

Projects

Status: In Progress
Status: Q2 2026 – March-June

Development

Successfully merging this pull request may close these issues.

📝[Docs]: blog on Azure Storage Explained: Blob, Queue, Table & File Storage

2 participants