Channels

Public threads, grouped by where they are happening. Pick a place to read its topics.

Unity Catalog

Filed under this by 33 pieces from 1 source · the whole ledger

  1. Metastore-level ABAC policies are in Betadatabricks.comstory
  2. VARIANT cast extends to ARRAY and MAP columns in ABAC column masksdatabricks.comstory
  3. Data Classification now scans Unity Catalog views (Beta)databricks.comstory
  4. External secrets in Unity Catalog (Beta)databricks.comstory
  5. ABAC DENY policies are in Betadatabricks.comstory
  6. ABAC GRANT policies are generally available for models and servicesdatabricks.comstory
  7. Unity Catalog Skills (Beta)databricks.comstory
  8. The INSERT, UPDATE, and DELETE privileges are in Betadatabricks.comstory
  9. Secrets in Unity Catalog will soon be available by default for workspaces with the compliance security profile enableddatabricks.comstory
  10. Context attributes in ABAC column mask and row filter policies (Beta)databricks.comstory
  11. Role-based access control (RBAC) is generally availabledatabricks.comstory
  12. Role-based access control (RBAC) will soon be available by default for workspaces with the compliance security profile enableddatabricks.comstory
  13. Identity attributes in ABAC column mask policies (Beta)databricks.comstory
  14. Upcoming deprecation of the data quality monitoring downstream_impact columndatabricks.comstory
  15. Upcoming deprecation of the data quality monitoring root_cause_analysis columndatabricks.comstory
  16. Define business concepts with Pages (Beta)databricks.comstory
  17. Unity Catalog ABAC GRANT policies support more securable types in Betadatabricks.comstory
  18. READ METADATA privilege is GAdatabricks.comstory
  19. Tag automations (Beta)databricks.comstory
  20. Schema-level HTTP connections in Unity Catalog are now generally availabledatabricks.comstory
  21. Refresh materialized views and streaming tables without exempting the pipeline owner from ABAC policiesdatabricks.comstory
  22. Secrets in Unity Catalog is GAdatabricks.comstory
  23. MANAGE no longer requires USE CATALOG or USE SCHEMA on the same objectdatabricks.comstory
  24. Upcoming general availability of Unity Gatewaydatabricks.comstory
  25. Python UDTFs in Unity Catalog are now generally availabledatabricks.comstory
  26. Automated setup for S3 external locationsdatabricks.comstory
  27. Databricks-hosted sample datasets available in the samples catalogdatabricks.comstory
  28. Role-based access control (RBAC) is in Public Previewdatabricks.comstory
  29. MLflow trace storage in Unity Catalog is now generally availabledatabricks.comstory
  30. Data Classification is now available by default for additional compliance standardsdatabricks.comstory
  31. Request for Access will soon be enabled by default for all workspacesdatabricks.comstory
  32. Secrets in Unity Catalog (Public Preview)databricks.comstory
  33. Restrict access to AI Functions with Unity Catalog permissions (Public Preview)databricks.comstory

A topic here is a label each publisher printed on its own piece. Equal labels from different publishers are shown together; that does not make them one subject.

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

Where this comes from

Solid branches are exact SourceFrontier census edges used by this page. Folded branches share the publisher but did not supply these items.

Hacker News

1 feed · 1 available · hn.algolia.com

text1 channel · 1 available
  1. Used here by hn-new hacker-attention Hacker News
    used on this pagehacker-attention

Latest

It's enough - vibecoding tag crossed from useless to harmfulThe vibecoding tag has been getting more and more useless for a while now. It lost the original meaning as the culture of software engineering with LLMs matured a bit. It got silly when posts talking about LLMs in general got tagged. It got useless when posts even mentioning some project created with LLMs in passing got tagged. Now it actually got harmful to the community when tagging posts turns away very valuable members https://lobste.rs/c/vecuxj I sighed and moved on for a while now as almost everything gets tagged - you can skip a word. But now it not only carries no signal whatsoever, it turns away people creating original technical content - which is what I assume anti-vibecoding people would actually like to see more of. Please split it or kill it. But we'd be better off without what exists today. Added: To be clear, I totally support people filtering out llm-generated or llm-centric posts. But right now everyone loses. And every day we lose a little bit more. Whether it's an original, interesting arviraptor lobste.rs