{"schema_version":1,"products":[{"id":"databricks-genie","name":"Databricks Genie","category":"数据 Agent"},{"id":"snowflake-cortex","name":"Snowflake Cortex Agents","category":"数据 Agent"},{"id":"fabric-data-agent","name":"Microsoft Fabric Data Agent","category":"AI 数据平台"},{"id":"dbt","name":"dbt","category":"语义层"},{"id":"cube","name":"Cube","category":"语义层"},{"id":"motherduck","name":"MotherDuck","category":"语义层"},{"id":"hex","name":"Hex","category":"AI 数据分析"},{"id":"looker","name":"Looker","category":"AI 数据分析"},{"id":"metabase","name":"Metabase / Metabot","category":"AI 看板"},{"id":"thoughtspot","name":"ThoughtSpot / Spotter","category":"AI 看板"}],"generated_at":"2026-10-14T12:59:28.810365+08:00","page_size":20,"home_event_ids":["2389fdc1bfba","b02b3cf7ac2e","df7d46e3ac4c","07d1a43e95cd","0966706f65b6","4c71993796c9","ccb0dfb24f16","d6c25a6e1f4d","b337d61cf716","cc01f4804031","b8f47b56b10b","179f269cb81e","4723f7d12121","6344b92b62db","5fc29d2143be","592746be7343","dfb9071b69e0","2f4285058421","d7e32f5af807","aa409ff1c354","1adabc48a9b5","5a1bcbbb92b1","8bfe1611f440","33b95e6ebad1","501361194897","55f175005622","18737669128e","4d4a27348e16","081f46c6c668","78f048488594","e4732f605006","fc025a8dae14","25038efe8dd5","5aad609d18d6","e2eeb6c0d24f","d1b062467e67","3fa42f3de13c","11bb140ae597","32c1d135e095","9ba28a519ea2","7b6deb18642c","445685a78953","c2e2f0147991","cdebe30eb814","8fe391a589c5","33d6e2757304","9145a29c01c3","67a1d2d0cb76","15a1daab0803","0a5e2954e746","854bf2b7766d","3d59ce90c174","a5e85b0e5b72","dcacd92fda95","c3e60124b535","248a0f91d772","cd61831e0655","67a7cef4fcc2","f2e20584f9b0","c043c6996461","03313007af0f","21a48ac63d78","fd1218fe1e81","6df9230e2f9b","3bab1efbb5de","fb2ee3737ecf","5d4bf78db846","7daf943a93a4","ddec884f46e7","e800e0369acc","d31716d36370","444b07d4567c","f00206fc1d6a","e1b8af84b84f","643b4690d563","7b960331578f","1683f2ca1c36","549d1d1ddade","4e03fd51d0a6","ca06eb030d88","7a101e693f8f","ef1ba3c7dd5a","e7a841a9d56c","480c1590c586","66638a56112b","c09b234dbbdd","6104559e9a96","661daa33a256","cdc582d9ae58","c4c3bbd6249e","60ad2a548483","de87ef36dd84","2e4e437e1168","320f80a74cba","62e265af89f4","fad0d9b82b18","d366d7dca12f","f9f138495fde","e704c420a297","a749656d502d","17b3b16903c0","c975ecb799c8","c167f613aaf5","ce25c73d71b2","b5e0a3db863f","c02e6f3fe00c","14614cd42402","eb2c204086f2","b5d78eb75dbc","e8eee7d3d631","c4451479dae7","6de6a0da5d3d","7d03159f7684","7600831240d2","ec72634f6edf","a3fccdbe66ce","98b74dfc9301","d927e58a6db6","80b6ab9f4ca1","60bf8e4b7542","82b17f45b54e","6fa801a59b33","e4034125cc97","0de08774e321","d2e6d3dce3a0","167559854496","871c27bf0387","7fd21eb8c5a2","d769b4f2c54f","b6c0f5d8a2e4","ae224a31c6ec","3bdb33764a67","f79f63c63e0d","62fa1dd33601","c2ec32b4904f","0715f0d3b7c0","a5ce3472770d","2f576701d80e","4ce08dbfa3a3","bfde167efa74","fb7a958f0064","e21d73e20f8f","6f777771ef7a","ddc6673776cd","b94c6c9a09dd","93d95b246d70","34bc72cca022","b96997bdba83","478f1b088f17","d2044403b905","951b7e33e52c","f2cae75df487","9013c2752aa4","e8e737d1c54c","e7dff550bb3c","a2e6f6d71810","dfd3a445a252","382fa24348cc","f76140abac25","91c492ef27ba","4509822decea","58f44ab1fece","1b6c9f3bf4a5","2f57edb18020","113da8bd65f9","44fb880837be","30b83b28a4ab","230eabee1072","72a01216eb46","741e2c14aac4","d5de35c54292","76d282dae0bb","0db2ede356a0","ae192c8958aa","3b18acac037a","042bbfa5ed32","8ac6899a569e","4f77f168f10e","841b5b975437","7ac392ea710c","979fa6b46cc5","eb90995c71f5","686054379e87","a6d68993f8e6","fa10b9bbe065","677217a95906","a0e0653ed731","39972c74aa29","ffc9d0d8b95f","dd5a53569de5","e2626ff1bf17","610ddc3d94ab","40c2caf96019","a1ebe51c3113","4c809899a4af","ec9943e319c5","eee1c02052f9","dd8cfe06050b","537b81bfdf56","0afd2b5824d2","9f8f09e080f9","0e858c1b5028","510e7cc5672e","7438410f9370","1040324d5b86","d7b6cc4a3303","c98d04acd1bf","a112e98a96f3","4e1f47dc01ac","e12a2952d00e","2a38d7e7886d","9033e4dee9cb","825556db5df8","1ee284ef0f32","e19bdeb4b036","2857d7b10179","9a7cfad4c8e4","2e9f871c967c","880cf15dc545","29786a87453c","7f6d22a0733c","03d840633827","d71cb00b889d","1acb63d9b8cf","22e61cb37a9c","779a5a2e9b2e","ac7b53978f0b","4b8fffa27e50","c8aeffe2b296","fe759b807f34","80c7dbc69c9c","26d202fd3489","ab586bc5d470","89da9115d842","425da12da7dc","d94c3328a3f2","25f0fe575038","c5db01d12b78","7c8800d1b37a","89845bea3750","025d7e1e4c9f","e54258012cf5","c3d67ea96518","72abdeca2f43","0ae0d3b4c0b0","2dc4de112d3d","883e8310f9a4","b61e19f27b42","e5047a94013f","ea4f1d97db33","b4ab99888c0d","159bcbb463f0","08421439e662","b77d23be249c","373235bebbaa","4a741d5c9e08","2735f617dc71","110ce74fa9e5","29e0b8236c7e","f65a1c3ef6c3","5ab337977aa6","2f84330339e9","eebe3840dcae","2eee875ea4c4","775f063ddfa3","80834225a78b","4d66f00eb39c","4761ed6dc8dd","6d4892f9d110","b84cc37d6f34","a28e77234d8e","9ee1caee2efa","52613ad8696c","b887687fe920","d59935fed7ef","3a9bd9cef38b","c5c8e925af01","04f292a5b8db","8472b7757697","4b50e35ecf47","ba19ed95fa31","2cb23ff14d5d","0d51b4362db6","7bcb449b109d","34f821da1d0f","774466de20a5","2621c2f3f508","5cac4004492d","402c6e3ce47a","57a7b282e14e","bd501c61d0f5","49b7c1960c22","71f75d69b18c","b9a25258238e","729c4b318a8b","c9ec1d90d337","cbf67eab8b01","2b3bac906a4b","d05ec7db74fa","121742439778","01bf8edae61d","d08baffbd722","70a81e2b6a37","591af11b5a5c","9bfa01144959","fd2e877cea44","c4e8f5a99035","39da2eb43096","341e5c5d3b89","4dad370e7247","bb6fe0f2d967","0d7185877bfa","afa110f519ff","6597afea514d","1590ce86fc2a","562907be2c5e","0980eee65ba0","4fa13c7cd30d","ef728d771871","bb69209c8d0f","b1206f2af34f","723c65c45ba9","d199550f2126","58f6eefe19db","f72942ffb967","ae59d5e45ca4","797acf2223dd","c90518881d01","6dc4e96e1ba7","a0a2d1d1e7b2","8feab1f0fa88","324abe85aa2a","5d62b7c6659d","3ab0ee43451d","f62fc670d258","185ee6eef27b","4c08e8e2cd44","f6162b805044","b8c871673575","0ef0564c116b","9ee13d67ebf3","ac7f62f35ef1","cc5c540a68f6","66e29f373297","45280e8ace9a","b219fb4a4304","a18fcf7ace27","86beae9f2748","d17829a807e2","d1f8a4b05ddf","70dc45860539","d89b42ab29e1","e3de08c4636a","4309cc7b0aec","ec9f60f77f17","d256128c2be7","fb749e18d61f","79c21caab6c3","e0a99392bc14","2ce94d63e438","fa2922eb6e68","340d835ba088","bd0a61be6b17","4f8c0a7d39f2","d4736cba9e07","fe27a272d0ce","1f2d67f8a512","657606c702fa","886b990fc1eb","1491e2cab966","d5e1ac751487","1cffe8c0886e","0916566e9991","fb81aeaf8e1a","98029c1b119e","fb6358d08535","e2adb769c3f5","10b6595d9b0a","6202212eeef3","db5674e1e03f","d2b5cfdbe7ec","177c2ac1fe39","01c578964b47","a0dfec66106c","4b74ba76aba5","28640dc36b12","21aaca4de4c7","66b04ff2d911","13ea46c500cf","d5cc6c757eb2","73dcdf0229c0","ecaefd096734","f4faeb6a40d3","ebe3d9541f1b","424b235d79d4","f76b86977b69","5c3a552147a1","d7c6d34e3d28","751bcb32efab","83357b7d65a2","5f9770dfca34","75210254bb59","0628bd50a80c","463acfe6a87d","41e1e7af7342","33b09d80e649","f22b1abe499d","9809cc8aea4d","c81741c8eae1","0aa16e2af514","18d4c041883c","2edb0885e1af","8c48e9aeec01","6c6fc36a363b","9f95b0f204de","b3444cea9cb6","01c3a1427929","bd7415fa4b93","29de685d5ab9","dd21ab640be2","1c087c0268b7","6d3a13fed4af","e768a44d300c","5a0ad358d586","e1458227e025","14238297ec97","f6add537db07","d5bfdeffce5c","6c6fa2765f00","bf71c501757a","7ebe29c893ee","ea26c96e3ff7","de350ca98624","ece5a6f921ad","99e77da46ab2","9574a86569ae","bcfd90e63775","cb619e8bf5e1","7db363bb1279","ea9a3a96fb86","aac18bc37c0e","1109cee945b2","96ab4b9624a6","c076af28e6b5","7be0c18da6ba","d3c5241619d2","c83867043e41","1f0497343807","188ddde3038b","d44ed50d0181","052a4392ec5b","6160b9f3ecaf","73a1ea512cd9","1e5e06d6ee03","5e7420583c0b","04fb8493780b","ddccf55e7eee","3fd2fe2ea75f","c5616347cb4f","07e502da82c2","de4f194acee8","59839f525322","e7f241b84ae2","cb734e7a1469","5b0f19a6ef69","5422d3495b2d","42d6165ced5d","0c00044a00c6","10a590ba05c3","89e0bffe4749","cf462f603c77","009c04918a87","f01dc118d37a","5b66bceba7c5","4395c235c498","de330de1394c","16934756bbd8","474a4fade92e","5f7ac34525b8","16d70a9b5e86","0b602400e43b","87c9acba5c38","b4ff3df743a4","2a6cb6153284","c96797b511e6","f70f3be61bc1","477745cf963d","65c35101abc1","2db4b086244c","0b039fb415c1","4c404bb47e34","1a5723bd7772","852499f0cb49","ac7c75fedd0b","5c4d28e53f75","5f8de8bd22e1","036431034b26","7dc53089a3b8","11bd570decd5","0faa3f1f97f8","e6e46cfe5599","1659453556d9","36e5214115ac","63b7989f4b33","f4962a2fa921","ed8330108532","190e28d13cb4","9f1a279db0dc","460d5283bb04","9653f52649c8","341ca51f8349","05b5c328b16d","9e059ac6ed28","d42105556279","a64173b0e40c","08162567f084","017baad77d72","d461dff20c65","26c7d5691708","74499ad15c94","ae39e628c113","4c9db581d5c6","ddcb4a5b6b52","04a9eab02673","5ce50d8a33b1","ded49e4ed330","5a003e60d050","663664951a62","a09c3221be78","5f584be1ab5d","e7420873acde","6a368cebfaaa","9f8ca8dc2ec6","7e23299ee03d","d44afcf41d63","cd516e1927b0","44517f2e6a68","c07808b097ea","b07c642afcbe","11caa8f9632f","fc1ed813ad68","0d666c08c243","60f9a9e4ae1a","97215171d286","679beacaaad9","566f6790c35c","63587adfe4de","7e46d654139f","c93bfa7909b8","c759c2325b45","598be2f438cd","6beb8036da98","849a2dcfc7c0","b37fd3d1c6d4","06473dc33f26","3c77505eef20","4c65d42c540c","ab71223dcc04","fe9ed70935a3","f5f77fd32d06","06ffc5e72f47","7175222a4aa1","ccc4b7fc179e","014ecba7e596","d17e13a7ceb3","bd750fad1df5","818d9d4e44f6","3576da62258e","07887457a24c","f7606c6bf1ab","d2194130512d","909af102152a","c218bd27e661","99fb5308d61b","fde18bebfbc0","bb45de9b3b4f","e7ef7e2d8090","4842d16865d3","64843a2454f2","8f1d134628cf","3c7ef4914e12","8fe614eddcbb","8f1a098ff064","875c99b3755b","dbe61a6475ee","82d023cf6dcc","01bd33c269e9","4d75839a2208","6a15bb49ecb1","f38e097a8967","8e5b13e46c10","8381a579fe49","ba8377c644db","c0107b7e1677","735b02a1d1e4","cbaf1f7bd561","1f6b975a6a4f","15799bed7e83","3bb9e34e59c3","dcb97c54e8f3","f9d8ce10886b","1526c962704f","e68fa92fad0f","097d6cd340b4","e4930118a675","8be1e5305105","98c97903bcf1","d4f17e123698","214ed5550146","d5b1f80826c9","f0a996fceedf"],"events":[{"event_id":"c09b234dbbdd","zh_title":"Apache Iceberg 1.12.0 发布","zh_summary":"Apache Iceberg 社区发布 1.12.0，自 1.11.0 以来包含 142 位贡献者的 777 次提交。该版本提升 Variant 读取性能，并将 shredded Variant 写入扩展到 Spark 之外，支持 Flink、Kafka Connect sink 和通用记录写入器。它还为 geometry 和 geography 地理空间类型增加读写支持，并以 WKB 存储在 Avro 和 Parquet 中。版本包含多项 Variant 正确性与健壮性修复，如 UTF-8 边界、指标崩溃和大十进制分片等。","reason":"Iceberg 是湖仓开放表格式的核心项目，本次更新涉及半结构化数据性能、多引擎写入和地理空间类型，直接影响数据平台选型与接入效率。","category":"platform","category_label":"AI 数据平台","vendors":["Apache Iceberg"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":37,"quality_score":80,"trend_score":3,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"news","pinned":false,"published":"2026-10-05T08:00:00+08:00","first_seen":"2026-10-14T12:59:28.810365+08:00","original_url":"https://iceberg.apache.org/blog/apache-iceberg-1.12.0-release/","items":[{"source":"Apache Iceberg Blog"}],"source_badge":"RSS"},{"event_id":"179f269cb81e","zh_title":"ggsql 0.5.0 发布 beta：用 SQL 绘图","zh_summary":"Posit 宣布 ggsql 0.5.0 进入首个 beta 版本。该版本新增 ADBC 读取器与 hybrid-reader 模式，可在只读数据库上先将查询结果转入 DuckDB/SQLite 等内存库处理，并输出 PDF/SVG 图表。ggsql 支持通过 SQL 生成出版级图表，无需切换到 R 或 Python，并内置 Markdown 文本格式。原文提到 hybrid 模式可绕过后端写权限限制，但数据量很大时会带来额外开销。","reason":"数据从业者可关注 SQL 原生可视化工具如何降低在数据库内出图的门槛，以及只读连接与缓存权衡对分析流程的影响。","category":"bi","category_label":"BI 与可视化","vendors":["Posit","DuckDB","SQLite"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["自助分析"],"decision_concerns":["成本与性能"]},"heat":69,"quality_score":83,"trend_score":58,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":83,"shelf":"news","pinned":false,"published":"2026-10-13T21:18:51.875000+08:00","first_seen":"2026-10-14T12:59:28.810365+08:00","original_url":"https://opensource.posit.co/blog/2026-09-24_ggsql_0_5_0/","items":[{"source":"Bluesky 数据社区"}],"source_badge":"Bluesky"},{"event_id":"3fa42f3de13c","zh_title":"持久化AI Agent记忆：跨会话如何记住上下文","zh_summary":"文章将持久化 AI Agent 记忆定义为模型上下文和权重之外的外部存储层，用于跨会话、工具与机器保存和检索有用上下文，而不是依赖更大的上下文窗口。它区分情节、语义和程序性记忆，并强调通过“捕获到更新”的循环保持记忆最新；Claude Code、Codex 和 Dify 可共享同一持久状态层。作者指出，仅靠向量检索不够，生产级记忆还需要范围、元数据与一致性。文中还以会话保持50轮连贯为例，说明会话连续性不等于持久召回。","reason":"AI Agent 正在进入生产，跨会话记忆直接影响分析型 Agent 的准确性与可用性；文中关于外部存储、记忆类型和一致性要求的拆解，对构建可运营的 Data Agent 有参考价值。","category":"agent","category_label":"Data Agent","vendors":["PingCAP","TiDB"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":25,"quality_score":45,"trend_score":9,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":45,"shelf":"evergreen","pinned":false,"published":"2026-10-09T00:06:08+08:00","first_seen":"2026-10-14T12:59:28.810365+08:00","original_url":"https://www.pingcap.com/blog/persistent-ai-memory/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"df7d46e3ac4c","zh_title":"2026实时分析实践指南：用湖仓统一实时分析","zh_summary":"文章讨论实时分析在2026年为何成为关键能力，覆盖实时BI看板、运营监控、日志与实时报表等场景。它提出用新鲜度、延迟、并发三个维度评估实时需求，而不是把实时简单看作二元要求。传统方案往往需要引入 Apache Druid、Apache Pinot 或 ClickHouse 等专用服务引擎，带来数据副本、管道和治理开销。文章主张把实时分析作为湖仓的一项能力，在既有分析负载上提供快速、可治理的实时洞察，减少架构蔓延。","reason":"数据从业者应关注如何判断哪些工作负载真正需要实时能力，以及湖仓统一实时负载与专用服务引擎之间的延迟、并发、成本和治理取舍。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","Apache Druid","Apache Pinot","ClickHouse"],"topics":["实时分析","湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案","权限与治理"],"use_cases":["看板与报告","生产评估与运营"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":56,"quality_score":57,"trend_score":55,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":57,"shelf":"evergreen","pinned":false,"published":"2026-10-14T03:17:26+08:00","first_seen":"2026-10-14T06:48:59.631187+08:00","original_url":"https://www.databricks.com/blog/practical-guide-real-time-analytics-2026","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"2389fdc1bfba","zh_title":"Lakeflow Designer 10月更新：新增无代码数据清洗与质量算子","zh_summary":"Databricks 发布 Lakeflow Designer 近四个月更新。该无代码 AI 原生数据准备与分析工具自 6 月 GA 后已有超 3,000 家客户使用，部分客户迁移后无代码工具支出降低 90%。本次新增 Prepare、Unique、Guardrails 等无代码算子，并增强现有算子、输出选项和画布，用于数据清洗、去重和数据质量检查。它还保留 Genie Code、Python 和 SQL 算子，方便分析人员与业务专家构建更大工作流。","reason":"数据从业者应关注 Databricks 在无代码数据准备与治理上的 AI 原生工作流更新，尤其新增数据清洗、去重和质量检查算子，以及按量计费带来的降本信号。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["自助分析","生产评估与运营"],"decision_concerns":["成本与性能","用户采用与业务价值"]},"heat":58,"quality_score":62,"trend_score":55,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"news","pinned":false,"published":"2026-10-14T03:00:00+08:00","first_seen":"2026-10-14T06:48:59.631187+08:00","original_url":"https://www.databricks.com/blog/whats-new-lakeflow-designer-october-2026-roundup","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"d6c25a6e1f4d","zh_title":"Databricks入选Gartner分析与BI平台魔力象限远见者","zh_summary":"Databricks宣布首次进入2026年Gartner分析与商业智能平台魔力象限，并被评为“远见者”。公司称其在所有参评厂商中获得最高的“愿景完整性”得分之一，并称这是该报告20多年历史上最佳首次亮相。文章认为BI本质已经改变，未来属于将分析与AI原生融合的数据平台。Databricks还提到数据与AI平台融合、代理式分析、以语义层为核心三大趋势。","reason":"Gartner ABI魔力象限是观察BI/分析平台格局的重要参考，Databricks首次入选并强调语义层与代理式分析，有助于数据从业者理解BI与数据平台融合方向。","category":"bi","category_label":"BI 与可视化","vendors":["Databricks"],"topics":["BI变局","语义层"],"product_ids":[],"focus":{"id":"ai-platform","label":"AI 数据平台","priority":1,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","报表与可视化"],"use_cases":[],"decision_concerns":["准确性与语义一致性"]},"heat":43,"quality_score":30,"trend_score":54,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":30,"shelf":"news","pinned":false,"published":"2026-10-14T02:00:00+08:00","first_seen":"2026-10-14T06:48:59.631187+08:00","original_url":"https://www.databricks.com/blog/databricks-visionary-gartnerr-magic-quadranttm-analytics-and-business-intelligence-platforms","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"cc01f4804031","zh_title":"ClickHouse 发布托管 Postgres 与 WalShadow 实时复制","zh_summary":"ClickHouse 在 Open House NYC 展示 Postgres 负责事务、ClickHouse 负责分析的集成栈，并现场演示 WalShadow 将 Postgres 复制到 ClickHouse 低于一秒。同期推出 ClickHouse Managed Postgres 的 Google Cloud 私有预览和 chdb Postgres 扩展，WalShadow 进入私有预览。文章称采样十家使用 Postgres ClickPipes 的 AI-native 客户，六个月数据量增长超过 1000%。Managed Postgres 采用本地 NVMe 存储，性能提升 2 到 10 倍，PeerDB 驱动的 CDC connector 已被超过一千家客户使用。","reason":"对数据从业者，Postgres 到 ClickHouse 的 CDC、托管 Postgres 和性能数据直接影响实时分析栈选型与架构。该内容来自厂商第一方，包含具体产品和演示指标。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse","Google Cloud","PeerDB"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案"],"use_cases":["数据接入","看板与报告"],"decision_concerns":["成本与性能"]},"heat":62,"quality_score":73,"trend_score":52,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":73,"shelf":"news","pinned":false,"published":"2026-10-13T23:35:19+08:00","first_seen":"2026-10-14T06:48:59.631187+08:00","original_url":"https://clickhouse.com/blog/postgres-at-open-house-nyc","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"b02b3cf7ac2e","zh_title":"Amazon Redshift 解决 Iceberg 表并发写冲突","zh_summary":"Amazon Redshift 现在可自动解决许多 Apache Iceberg 表的并发写入冲突，把此前会失败并要求重试的提交直接完成。文章解释 Iceberg 使用乐观并发控制（OCC）与快照隔离，写写冲突来自按表版本而非按行或分区检查。Redshift 会把检查从操作级逐步升级到分区级和文件级，以判断并发写入是否真正重叠，并说明由此带来的吞吐提升。该机制面向流式任务、调度管道和一次性转换同时写同一张表的场景。","reason":"对使用 Redshift/Iceberg 的数据平台团队，这是并发写入可靠性、吞吐与快照隔离语义的关键更新；理解冲突检测粒度有助于设计流批一体写入和重试策略。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon Redshift"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["生产评估与运营"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":63,"quality_score":72,"trend_score":56,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"news","pinned":false,"published":"2026-10-14T04:16:48+08:00","first_seen":"2026-10-14T06:48:59.631187+08:00","original_url":"https://aws.amazon.com/blogs/big-data/resolving-concurrent-write-conflicts-for-apache-iceberg-tables-in-amazon-redshift/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"4c71993796c9","zh_title":"用Fivetran AI连接器集中管理AI使用数据","zh_summary":"Fivetran官方博客介绍其如何用自有AI connectors将分散在OpenAI、Anthropic等平台的使用与支出数据集中到一处。文章指出，AI提供商通常只给用户级数据，而财务团队需要按成本中心分摊AI支出，手动CSV导出和拼接流程难以为继。Fivetran通过标准化AI connectors替代手动采集，构建集中视图，用于回答AI花了多少钱、谁在使用、是否提升生产力等问题。该实践面向希望把AI消费数据纳入预算、成本核算和经营分析的团队。","reason":"数据从业者可参考如何把多源AI使用与支出数据接入数据平台，并与成本中心、预算和生产力评估关联。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran","OpenAI","Anthropic"],"topics":["财务经营"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["成本与性能","用户采用与业务价值"]},"heat":54,"quality_score":55,"trend_score":54,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":55,"shelf":"evergreen","pinned":false,"published":"2026-10-14T01:11:49+08:00","first_seen":"2026-10-14T06:48:59.631187+08:00","original_url":"https://www.fivetran.com/blog/centralizing-ai-usage-data-with-fivetrans-ai-connectors","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"5fc29d2143be","zh_title":"用红黄绿三色提示语给Agent装刹车省token","zh_summary":"作者为Claude Code、Codex等Agent手搓不到300字的进度提示语，在每轮回复结尾用绿/黄/红灯标注任务状态：绿灯只记搁置项，黄灯输出带证据的后续计划，红灯存档结束。实践场景覆盖代码开发、数据库迁移验证、旧会话整理等，通过hook自动生效，减少Agent无限推荐下一步导致的token浪费和任务拖长。","reason":"这是面向Agent使用者的原创实践方法，直接回应Agent任务边界失控与token成本问题，对使用Agent做数据开发和运维的从业者有可复用价值。","category":"agent","category_label":"Data Agent","vendors":["Claude Code","Codex","DeepSeek"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","Agent接口与工具"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["成本与性能","用户采用与业务价值"]},"heat":59,"quality_score":72,"trend_score":48,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-10-13T16:56:20+08:00","first_seen":"2026-10-14T06:48:59.631187+08:00","original_url":"https://www.woshipm.com/ai/6477460.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"07d1a43e95cd","zh_title":"Snowflake PrivateLink 连接：账户授权、端点绑定与网络策略","zh_summary":"本文聚焦 AWS PrivateLink 入站连接到 Snowflake 服务，指出私有连接实际由多个彼此独立的控制项组成：AWS 账户授权、端点级绑定（pinning）、网络策略白名单以及 Snowflake 认证。文章通过架构图区分流量路径与控制平面，并分两道关卡说明：先授权 AWS 账户，再将 VPCE ID 注册绑定到特定的 Snowflake 账户。文中还回答了几个常见疑问：授权某个 AWS 账户不会自动绑定端点，TLS 连接成功并不代表该端点被允许，AWS PrivateLink 也不提供限制单一消费者账户可创建 VPCE 数量的可配置配额。","reason":"面向数据平台运维与安全从业者，清晰拆解 Snowflake 私有连接的多层控制与常见误判，有助于正确配置与审计网络访问。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["数据接入"],"decision_concerns":["权限与安全"]},"heat":62,"quality_score":71,"trend_score":55,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":71,"shelf":"evergreen","pinned":false,"published":"2026-10-14T03:01:02+08:00","first_seen":"2026-10-14T06:48:59.631187+08:00","original_url":"https://medium.com/snowflake/snowflake-privatelink-connectivity-account-authorization-endpoint-pinning-and-network-policies-1a782a7ef5f5?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"ccb0dfb24f16","zh_title":"从 Snowflake SQL 查询调用外部 API 与 SFTP 服务","zh_summary":"作者分享团队在 Snowflake 中调用第三方加密 API 的实践：通过 External Access Integration，在 Python UDF 中调用 REST API 解密 token（如加密卡号）以支持下游分析。需求包括 OAuth 2 客户端凭据认证、经 AWS PrivateLink 路由流量，并覆盖 SFTP 服务器调用。架构区分两条网络路径：OAuth 走公网出站 HTTPS，API 走 PrivateLink。作者指出 Snowflake 侧配置约占 30% 工作量，剩余 70% 在基础设施协调、AWS 配置和证书链问题。","reason":"对数据平台/数据工程团队，本文给出从云数仓安全调用外部 API/SFTP 的可复用架构与踩坑，涉及 PrivateLink、OAuth 和证书链，具实践参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake","AWS"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["数据接入"],"decision_concerns":["权限与安全"]},"heat":63,"quality_score":75,"trend_score":54,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-10-14T01:01:03+08:00","first_seen":"2026-10-14T06:48:59.631187+08:00","original_url":"https://medium.com/snowflake/breaking-out-of-snowflake-calling-external-apis-and-sftp-servers-from-sql-queries-3fe5afb65baf?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"0966706f65b6","zh_title":"Power Pages 推出 SPA 模板：分钟级建站","zh_summary":"Power Pages 插件为 GitHub Copilot CLI 和 Claude Code 新增 SPA 模板支持，/create-site 可基于现成单页应用模板创建站点。新功能包括智能模板匹配、构建前预览和引导式预配，会导入 Dataverse 解决方案、上传站点并应用示例数据。首批提供 311 Citizen Services Portal 和 Supplier Invoice Portal 两个模板。官方称从模板创建只需几分钟和少量 AI credits，而从零生成可能超过一小时，模板默认符合 WCAG 2.2。","reason":"这是微软 Power Platform 在 AI 辅助应用生成上的产品更新，涉及 Dataverse、AI 成本与生产级交付，数据平台/数据产品团队可借此观察 AI Agent 如何降低低代码应用交付门槛。","category":"product","category_label":"数据产品","vendors":["Microsoft","Power BI","Power Pages","Dataverse"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案","Agent接口与工具"],"use_cases":["方案封装与分发","Agent构建"],"decision_concerns":["成本与性能","用户采用与业务价值"]},"heat":57,"quality_score":61,"trend_score":54,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":61,"shelf":"news","pinned":false,"published":"2026-10-14T01:25:20+08:00","first_seen":"2026-10-14T06:48:59.631187+08:00","original_url":"https://www.microsoft.com/en-us/power-platform/blog/power-pages/create-power-pages-sites-in-minutes-with-spa-templates/","items":[{"source":"Microsoft Power BI（Power Platform Blog）"}],"source_badge":"RSS"},{"event_id":"b8f47b56b10b","zh_title":"John Paul 用代理式分析扩展个性化服务","zh_summary":"在 Big Data Paris 的炉边对话中，John Paul 全球数据与 CRM 总监 Hubert Choplin 分享了公司如何利用代理式分析改造数据架构。John Paul 作为 Accor 集团成员，管理三大洲 350 名礼宾人员，服务多达 100 万活跃会员，年处理超 80 万次请求。文章强调现代分析工具实施更快，无需数月或大量顾问；目标是通过数据民主化让团队更快决策并提升客户体验。核心是从“数据驱动”走向“行动驱动”。","reason":"数据从业者可关注代理式分析在礼宾/CRM 个性化场景的落地案例，以及数据民主化如何支撑一线团队实时决策。","category":"agent","category_label":"Data Agent","vendors":["ThoughtSpot"],"topics":["Data Agent","客户运营"],"product_ids":["thoughtspot"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","场景与方案"],"use_cases":["自助分析"],"decision_concerns":["成本与性能","用户采用与业务价值"]},"heat":50,"quality_score":48,"trend_score":51,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":48,"shelf":"evergreen","pinned":false,"published":"2026-10-13T22:16:53.920815+08:00","first_seen":"2026-10-13T22:16:53.920815+08:00","original_url":"https://www.thoughtspot.com/blog/how-john-paul-delivers-personalization-at-scale-with-agentic-analytics","items":[{"source":"ThoughtSpot Blog"}],"source_badge":"RSS"},{"event_id":"592746be7343","zh_title":"ClickHouse 查询尾延迟 32ms 根因与修复","zh_summary":"客户在空闲后执行简单 SELECT 查询时，观察到约 32 ms 的额外尾延迟。ClickHouse 团队将其定位为 Native 协议元数据包未批量发送，导致重置后的 TCP 拥塞窗口被撑满。作者用 network namespace 和 tc 模拟约 32 ms 网络 RTT，并设置 initcwnd=8 复现了该问题。最终通过批量发送这些元数据包修复。","reason":"这是 ClickHouse 官方对生产环境尾部延迟的完整根因分析、复现和修复，涉及 Native 协议与 TCP 拥塞控制，对数据库性能排查和网络调优有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":69,"quality_score":96,"trend_score":48,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":96,"shelf":"evergreen","pinned":false,"published":"2026-10-13T16:49:51+08:00","first_seen":"2026-10-13T22:16:53.920815+08:00","original_url":"https://clickhouse.com/blog/chasing-32ms-tail-latency-clickhouse","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"4723f7d12121","zh_title":"Fivetran Activations 降价并增强规模化能力","zh_summary":"Fivetran 宣布下调 Activations 高用量区间的价格，并推出多项产品增强，帮助客户在规模化时以更可预测的成本激活更多数据。新功能包括按 Activation source 到目标路径分组的 source-based 管理模型、跨 Fivetran Cloud Region 全球部署、按 source 自定义区域和存储配置，以及复用 PrivateLink 和统一 Permissions。Fivetran 还推出重新设计的 API 和更新的 webhooks，以降低运营开销并自动化工作流。Activations 旨在为仓库或数据湖中的可信数据提供受治理的路径，直接进入 HubSpot、广告平台等业务工具，减少 CSV 导出和一次性管道。","reason":"数据集成与激活团队可关注其如何通过降价及权限、区域、API 等增强，降低从仓库/数据湖到业务工具规模化运营的门槛。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran"],"topics":["客户运营"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理","场景与方案"],"use_cases":["数据接入","方案封装与分发"],"decision_concerns":["成本与性能","权限与安全"]},"heat":51,"quality_score":52,"trend_score":51,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":52,"shelf":"news","pinned":false,"published":"2026-10-13T21:00:02+08:00","first_seen":"2026-10-13T22:16:53.920815+08:00","original_url":"https://www.fivetran.com/blog/more-value-as-you-scale-with-fivetran-activations","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"6344b92b62db","zh_title":"QCon AI纽约2026：生产级Agent的权限、评估与成本","zh_summary":"QCon AI 纽约 2026（12月15-16日，泽西城 Westin Jersey City Newport）公布多场生产级 AI 主题演讲，聚焦 Agent 上线后的代码评审压力、token 成本上升、评估可信度以及权限与护栏问题。讲者包括 AWS Data Protection 创始人 Nancy Wang（生产环境中 Agent 的身份与授权）、LinkedIn 负责 Kubernetes 迁移的 Ronak Nathani（覆盖 50 万+ 节点、500 万+ Pod 的运维 Agent 的技能、工具与护栏）、DoorDash Agentic Ordering 基础模型负责人 Fabio Flores（用同一评判模型贯穿仿真与生产会话，让上线前测得的改进延续到线上）。文章强调这些资深工程师已在真实系统中做出决策并给出系统设计与背后的数字，便于其他团队对照自身约束做取舍。","reason":"对正在做 Data Agent/ChatBI 落地的团队，Agent 的身份授权、护栏、评估闭环与 token 成本是绕不开的工程约束，LinkedIn、DoorDash 这类生产系统的具体做法可直接用来对照自建方案。","category":"agent","category_label":"Data Agent","vendors":["AWS"],"topics":["Data Agent","平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","权限与治理"],"use_cases":["生产评估与运营","Agent构建"],"decision_concerns":["可靠性与评估","权限与安全"]},"heat":43,"quality_score":35,"trend_score":50,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":35,"shelf":"news","pinned":false,"published":"2026-10-13T20:00:00+08:00","first_seen":"2026-10-13T22:16:53.920815+08:00","original_url":"https://www.infoq.com/news/2026/10/qcon-ai-newyork-2026-sessionsv2/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"b337d61cf716","zh_title":"Neo4j 在 Snowflake 上创建虚拟图","zh_summary":"Neo4j 官方博客介绍 Neo4j Aura 的 Virtual Graph 功能，可在 Snowflake 之上创建虚拟图，无需复制数据。文章以 Snowflake 的 TPC-H 示例数据集为例，该数据集含 8 张表，并隐含图结构。设置过程包括创建 Snowflake 服务账号、角色并授权读取示例数据，再配置 RSA 密钥和 Neo4j Aura 虚拟图实例。作者称该方式可缩短实现价值时间并降低 TCO。","reason":"数据从业者可了解图数据库与云数仓的原生集成方式，以及在不搬数据的前提下构建知识图谱/企业知识层的可行路径与权限配置要点。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake","Neo4j"],"topics":["语义层"],"product_ids":[],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["数据接入"],"decision_concerns":["成本与性能","权限与安全"]},"heat":61,"quality_score":73,"trend_score":51,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":73,"shelf":"evergreen","pinned":false,"published":"2026-10-13T22:01:05+08:00","first_seen":"2026-10-13T22:16:53.920815+08:00","original_url":"https://medium.com/snowflake/neo4j-virtual-graph-on-snowflake-bee771442fe1?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"501361194897","zh_title":"Flo Health 用 Databricks 构建更安全开放模型","zh_summary":"Flo Health 为 8100 万月活用户构建医疗健康类生成式 AI，对安全性和实用性要求很高。团队用 AI 评审员和隐私优先的合成数据定义医疗安全与有用性标准，并基于 Databricks AI Runtime 在无服务器 NVIDIA H100 GPU 上分布式微调开放模型。Flo 估算，相比调用前沿模型 API，定制微调模型可将推理成本降低一个数量级，并增强对模型行为与生命周期的控制。该实践强调先做评估再做训练，以兼顾安全、成本与个性化。","reason":"该案例展示大规模 GenAI 产品如何用评估优先、合成数据和分布式微调平衡医疗安全、个性化与推理成本，对构建生产级 AI 数据平台有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":50,"quality_score":67,"trend_score":37,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":67,"shelf":"evergreen","pinned":false,"published":"2026-10-12T23:13:04+08:00","first_seen":"2026-10-13T08:42:26.816714+08:00","original_url":"https://www.databricks.com/blog/how-flo-health-built-safer-more-useful-open-models-databricks-ai-runtime","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"18737669128e","zh_title":"Metabase 如何自动化发布：从手工清单到每日补丁","zh_summary":"Metabase 官方博客回顾了其发布流程的自动化演进。2022 年发布经理仍需按手工清单在本机构建二进制、人工点击测试、再用脚本容器化并上传到 Docker Hub 和官网，通常每两周才交付一个小版本。后来团队把 Bash 与 Clojure 脚本改为经过测试的 TypeScript 函数，并用 GitHub Actions 串联 Build/Test/Publish。最终他们将 Build 与 Test 合并，复用测试流程中已构建的二进制并打上版本标签，使发布耗时减少近半小时，如今每天可自动发出新补丁。","reason":"Metabase 是主流 BI 工具，本文第一方披露其发布自动化如何减少人工错误、提升交付频率，对数据产品与 BI 团队的工程效率和发布可靠性有参考价值。","category":"bi","category_label":"BI 与可视化","vendors":["Metabase"],"topics":[],"product_ids":["metabase"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":[],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":53,"quality_score":76,"trend_score":34,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":76,"shelf":"evergreen","pinned":false,"published":"2026-10-12T17:09:09+08:00","first_seen":"2026-10-13T08:42:26.816714+08:00","original_url":"https://www.metabase.com/blog/how-we-automate-metabase-releases","items":[{"source":"Metabase Blog"}],"source_badge":"RSS"},{"event_id":"2f4285058421","zh_title":"Amazon EMR 原生集成 AWS Glue 数据质量","zh_summary":"Amazon EMR Data Quality built on AWS Glue 现已在 Amazon EMR 原生可用，并随 emr-spark-8.1.0 及更高版本提供。用户可使用与 AWS Glue 相同的 DQDL 编写数据质量规则，直接在 Amazon EMR on EC2、Serverless 和 EKS 的 Spark 作业中运行。文章介绍两种模式：临时校验，以及 Iceberg Write-Audit-Publish 模式，即 ETL 写入分支、从 Glue Data Catalog 获取托管规则集、校验通过后再合并到主表。","reason":"说明 EMR 数据质量从自建 Deequ 或绕行 Glue 转向原生、集中规则管理，并结合 Iceberg WAP 降低脏数据进入生产湖仓的风险，对数据平台和湖仓治理团队有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon EMR","AWS Glue"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["生产评估与运营"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":55,"quality_score":71,"trend_score":42,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":71,"shelf":"news","pinned":false,"published":"2026-10-13T07:40:26+08:00","first_seen":"2026-10-13T08:42:26.816714+08:00","original_url":"https://aws.amazon.com/blogs/big-data/bring-data-quality-to-your-amazon-emr-workloads-with-amazon-emr-data-quality-built-on-aws-glue-data-quality/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"33b95e6ebad1","zh_title":"使用KPL与KCL构建跨账户流式管道","zh_summary":"AWS官方博客介绍如何用Amazon Kinesis Producer Library（KPL）和Kinesis Client Library（KCL）在多个AWS账户间构建高吞吐、低延迟的流式管道。文章覆盖生产者、流、消费者分属不同账户的最隔离架构，并说明需协调IAM策略、加密密钥与跨账户监控。KPL负责高吞吐写入、聚合记录、重试与CloudWatch指标，KCL 3.5通过DynamoDB协调分片租约进行消费。文中给出跨账户访问的最佳实践与详细演练。","reason":"面向数据平台从业者的跨账户实时数据接入与安全隔离实践，涉及IAM、加密、监控和Kinesis库配置，对建设企业级流式管道有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon Kinesis","AWS Lambda","Amazon Data Firehose","Apache Flink"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["数据接入"],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":59,"quality_score":85,"trend_score":37,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-10-12T23:48:07+08:00","first_seen":"2026-10-13T08:42:26.816714+08:00","original_url":"https://aws.amazon.com/blogs/big-data/build-cross-account-streaming-pipelines-with-the-amazon-kinesis-producer-library-and-kinesis-client-library/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"aa409ff1c354","zh_title":"Fivetran托管数据湖写入凭证正式可用","zh_summary":"Fivetran 宣布 Managed Data Lake Write Credentials 正式普遍可用，用户现可对托管数据湖执行 DDL 和 DML 操作。该能力通过为托管 Apache Polaris 目录提供第二套写权限凭证实现，可用于删除记录（如响应 GDPR 请求）和删除不再需要的表。写凭证仅 Destination Admin 或 Account Admin 可见，并非面向普通用户。Fivetran 表示其 750+ 连接器可将数据以 Apache Iceberg 格式写入 S3、Azure Data Lake 和 Google Cloud Storage，并可由 Snowflake、BigQuery、Databricks 等引擎查询。","reason":"该更新直接关系到托管数据湖的写入权限、治理与表生命周期管理，对使用 Fivetran 建设开放数据基础设施的数据团队有运维参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran","Snowflake","Google BigQuery","Databricks"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["数据接入"],"decision_concerns":["权限与安全"]},"heat":51,"quality_score":65,"trend_score":39,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"news","pinned":false,"published":"2026-10-13T03:07:17+08:00","first_seen":"2026-10-13T08:42:26.816714+08:00","original_url":"https://www.fivetran.com/blog/introducing-fivetran-managed-data-lake-write-credentials","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"5a1bcbbb92b1","zh_title":"Fivetran推出托管数据湖服务，自动化湖表维护","zh_summary":"Fivetran 发布托管数据湖服务 Fivetran Managed Data Lake，支持 Amazon S3、Azure Data Lake Storage、Microsoft OneLake 和 Google Cloud Storage。该服务可从 700+ 预置或自定义数据源自动集成数据，并在落入数据湖前完成规范化、压缩和去重，以 Delta Lake 或 Apache Iceberg 开放表格式存储。它可与 AWS Glue、Databricks Unity Catalog、Apache Polaris 等数据目录原生集成，并支持通过 Databricks、Snowflake、Starburst、Redshift 等计算引擎用 Python/SQL 查询。用户还可用 dbt 转换、Power BI 可视化，或用 SageMaker、Azure Machine Learning、Databricks Mosaic AI、Vertex AI 构建 AI/ML 模型。","reason":"数据湖表维护、开放表格式与数据治理是湖仓落地的关键运维痛点；该发布把 Fivetran 的集成能力延伸到托管数据湖运维，数据平台团队可关注其对湖仓架构和数据集成方案的影响。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran","Databricks","Snowflake","Starburst","dbt"],"topics":["湖仓"],"product_ids":["dbt"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["可维护性与复用","成本与性能"]},"heat":54,"quality_score":63,"trend_score":46,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":63,"shelf":"news","pinned":false,"published":"2026-10-13T03:05:09+08:00","first_seen":"2026-10-13T08:42:26.816714+08:00","original_url":"https://www.fivetran.com/blog/announcing-fivetran-managed-data-lake-service","items":[{"source":"Fivetran Blog"},{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"55f175005622","zh_title":"何时使用 Liquid Clustering？湖仓布局策略基准测试","zh_summary":"文章在 Delta Lake 上对 Liquid Clustering、ZOrdering 和分区策略在四类工作负载中进行基准测试。它发现 ZOrder 在日期列作为次级或三级键时存在隐藏故障模式，时间范围查询比简单日期分区表慢 78%。Liquid Clustering 在点查等场景延迟最低，尽管扫描的原始数据多于 ZOrder，并建议查询模式多样或演进时作为默认。仅在过滤列稳定且高度选择性的多列谓词场景下，ZOrder 更合适。","reason":"湖仓物理布局直接影响查询成本、延迟与运维负担；该基准给出可落地的策略选择框架和反直觉发现，适合数据平台与数仓从业者参考。","category":"platform","category_label":"AI 数据平台","vendors":[],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":57,"quality_score":84,"trend_score":35,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":84,"shelf":"evergreen","pinned":false,"published":"2026-10-12T19:00:00+08:00","first_seen":"2026-10-13T08:42:26.816714+08:00","original_url":"https://www.infoq.com/articles/liquid-clustering-lakehouse-layout/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"1adabc48a9b5","zh_title":"Agent37：低成本AI Agent沙箱，单沙箱月均成本0.37美元","zh_summary":"YC孵化项目Agent37推出面向AI Agent运行的低成本沙箱服务，称价格不到多数沙箱提供商的10%，客户平均每沙箱每月花费0.37美元。团队通过分析CPU/RAM突发型消耗模式、绕开超大规模云厂商租用Hetzner/OVH主机、采用gVisor实现跨沙箱内存共享与快速启动来压低成本，免费套餐月均基础设施成本约0.05至0.10美元。","reason":"涉及Agent运行基础设施的成本优化路径，对数据/分析Agent的部署与运营有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["Agent37"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":60,"quality_score":72,"trend_score":50,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"news","pinned":false,"published":"2026-10-13T00:46:34+08:00","first_seen":"2026-10-13T08:42:26.816714+08:00","original_url":"https://news.ycombinator.com/item?id=50059096","items":[{"source":"Hacker News（数据关键词）"}],"source_badge":"HN"},{"event_id":"d7e32f5af807","zh_title":"用 Snowflake Cortex Search 做客户需求智能匹配","zh_summary":"Snowflake 官方博客介绍了一套可复用的匹配模式：把客户用自由文本描述的需求，与产品路线图/解决方案目录做语义匹配。实现上使用 Snowflake Cortex Search Service 理解请求意图，超越关键词命中，并借助 AI_CLASSIFY、AI_COMPLETE 等 Cortex AI 函数处理文本，数据资产本身都存在 Snowflake 中。该能力被嵌入 Salesforce 的客户功能需求表单，销售工程师填写客户目标、产品限制与业务影响时即自动弹出最相关的已有增强项及其所属产品域。作者强调同一框架可迁移到工单匹配解决模板、客户目标匹配伙伴能力、技能缺口匹配培训资源等场景。","reason":"第一方技术实践，展示了基于数据平台做语义检索匹配的完整落地路径与可复用框架，对想做 RAG/语义搜索类数据产品的团队有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake","Salesforce"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","场景与方案"],"use_cases":["数据发现与搜索"],"decision_concerns":["准确性与语义一致性","用户采用与业务价值"]},"heat":49,"quality_score":61,"trend_score":39,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":61,"shelf":"evergreen","pinned":false,"published":"2026-10-13T03:49:59+08:00","first_seen":"2026-10-13T08:42:26.816714+08:00","original_url":"https://medium.com/snowflake/ai-powered-gtm-triage-smart-suggestions-using-cortex-search-8d518bf4bf03?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"4d4a27348e16","zh_title":"BigQuery 推出 TimesFM 3.0，支持多变量时序预测","zh_summary":"BigQuery 宣布 TimesFM 3.0 预览，新增原生多变量时间序列预测，可在 BigQuery SQL 中通过 AI.FORECAST 使用。TimesFM 3.0 是 Google Research 开发的 330M 参数基础模型，支持单/多目标列以及仅历史值和历史+未来值协变量。它称在 GIFT-Eval、FEV-Bench 和 TIME 三个公开时序榜单上取得第一的零样本准确率。该模型也可作为 TimesFM 2.0/2.5 的 drop-in 升级用于 AI.FORECAST 单变量预测和 AI.DETECT_ANOMALIES 异常检测；文中用 NYC Citi Bike 数据集演示 7 天 subscriber_trips 与 casual_trips 预测。","reason":"把多变量基础模型预测直接带入 BigQuery SQL，分析团队无需自训模型即可处理更贴近现实的预测问题，并以 drop-in 方式升级现有单变量/异常检测工作流。","category":"platform","category_label":"AI 数据平台","vendors":["Google","Google Cloud","BigQuery"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案"],"use_cases":[],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":51,"quality_score":77,"trend_score":30,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":77,"shelf":"news","pinned":false,"published":"2026-10-12T08:00:00+08:00","first_seen":"2026-10-13T08:42:26.816714+08:00","original_url":"https://cloud.google.com/blog/products/data-analytics/bigquery-timesfm-3-0-with-multivariate-time-series-forecasting","items":[{"source":"Google Cloud Data Analytics Blog"}],"source_badge":"RSS"},{"event_id":"2e4e437e1168","zh_title":"2026年9月就业报告：平稳但缺乏火花","zh_summary":"根据美国劳工统计局数据，9月雇主新增2.9万个岗位，失业率从4.1%微升至4.2%。7月和8月修正合计减少6万个岗位，使三个月平均新增就业为5.1万/月，与上月报告一致。劳动力参与率微升至61.8%。报告认为劳动力市场保持平稳但缺乏增长动力，可能影响美联储10月是否再次加息的决策。","reason":"该报告是典型的数据驱动宏观分析，用就业、失业率、修正值和参与率等指标回答劳动力市场状况，并关联美联储利率决策，可供关注组织人才与经营环境的数据从业者参考。","category":"insight","category_label":"AI分析","vendors":["Indeed"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":33,"quality_score":73,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":73,"shelf":"news","pinned":false,"published":"2026-10-02T21:18:34+08:00","first_seen":"2026-10-12T23:28:02.880832+08:00","original_url":"https://hiringlab.indeed.com/2026/10/02/september-2026-jobs-report-steadiness-without-a-spark/","items":[{"source":"Indeed Hiring Lab"}],"source_badge":"RSS"},{"event_id":"6a368cebfaaa","zh_title":"如何成为Agent老板：微软智能体管理建议","zh_summary":"微软Copilot Studio高级产品营销经理Jack Rowbotham分享如何成为“Agent老板”：在Microsoft 365 Copilot中创建智能体，明确要改善的具体业务流程，并像管理团队一样委派任务。文章建议为智能体写清“职位描述”，对重复性、规则型任务可让一人管理数十个智能体。作者认为未来简历不仅包含人类经验与技能，还包括构建、管理和部署智能体的能力。","reason":"该文虽不涉及具体数据栈，但微软将智能体管理视为未来工作核心能力，对数据团队构建分析Agent、设计人机协作流程有参考价值。","category":"agent","category_label":"Data Agent","vendors":["Microsoft","Copilot Studio","Microsoft 365 Copilot"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","知识与上下文"],"use_cases":["Agent构建"],"decision_concerns":["用户采用与业务价值"]},"heat":17,"quality_score":37,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":37,"shelf":"evergreen","pinned":false,"published":"2026-08-01T03:40:39+08:00","first_seen":"2026-10-12T23:28:02.880832+08:00","original_url":"https://www.microsoft.com/en-us/worklab/how-to-be-an-agent-boss","items":[{"source":"Microsoft WorkLab"}],"source_badge":"官网"},{"event_id":"8bfe1611f440","zh_title":"Aloudata入选2026 IDC中国新兴金融科技50","zh_summary":"IDC发布“2026 IDC 中国新兴金融科技 50”榜单，Aloudata以NoETL语义编织创新金融数据基础设施并实现规模化落地而入榜。Aloudata通过Aloudata BIG主动元数据平台和算子级血缘，服务招商银行、民生银行、杭州银行、华泰证券等机构，用于加工链路治理、数据资产管理、监管报送口径盘点等场景。案例中，民生银行监管报送口径盘点效率提升20倍、成本下降90%；杭州银行根因分析提效40%、影响面分析人天成本降低50%。面向AI时代，Aloudata还推出语义平台Aloudata CAN和Aloudata Agent可信数据分析智能体，支持智能问数、归因分析和报告生成。","reason":"文章涉及金融数据治理、可信语义层和Data Agent落地，并给出银行/证券客户案例与量化收益，对关注数据平台与AI分析落地的从业者有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Aloudata"],"topics":["Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","指标与语义"],"use_cases":["指标问答","看板与报告"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":43,"quality_score":56,"trend_score":32,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":56,"shelf":"news","pinned":false,"published":"2026-10-12T14:25:08+08:00","first_seen":"2026-10-12T23:28:02.880832+08:00","original_url":"https://aloudata.com/news/aloudata-2026-idc-china-emerging-fintech-50","items":[{"source":"Aloudata 动态"}],"source_badge":"官网"},{"event_id":"25038efe8dd5","zh_title":"TinyFish 用 Databricks 训练并部署 Web 模型","zh_summary":"TinyFish 为企业提供跨实时网络的 agent 基础设施，支持 Search、Fetch、Browser 和 Agent API 等大规模已认证 Web 工作流。它用 Databricks AI Runtime 在托管 GPU 上训练和微调其 web-native 模型，用 MLflow 做评估，并通过 Databricks Model Serving 生产推理。其内部 go/no-go 基准在 2,178 个 web-agent 任务上测得 77.6% 任务成功率。团队已从监督微调起步，正转向 DPO，以打通从生产 agent 行为到后训练、评估和部署的闭环。","reason":"数据从业者可关注 Databricks AI Runtime、MLflow 与 Model Serving 如何串联 agent 模型的后训练到生产，以及 web-agent 任务成功率的评估口径，对平台选型与 Agent 评估有参考。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","TinyFish"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估"]},"heat":33,"quality_score":57,"trend_score":13,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":57,"shelf":"news","pinned":false,"published":"2026-10-10T00:32:01+08:00","first_seen":"2026-10-12T23:28:02.880832+08:00","original_url":"https://www.databricks.com/blog/post-training-production-how-tinyfish-runs-its-web-native-model-databricks-ai-runtime","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"5d4bf78db846","zh_title":"Fivetran 发布 dbt 平台与 Context Layer 更新","zh_summary":"Fivetran 月度产品更新汇总了 dbt Summit 上发布的下一代 Fivetran + dbt 平台，包括 dbt v2 引擎、dbt State、Lake Compute、dbt Wizard、dbt Charts 等。Fivetran Context Layer 进入 Limited Public Preview，可从现有管道构建 Agent 上下文，把分析、运营和知识源（含非结构化内容索引）发布到用户仓库中的 Agents Schema 开放 SQL 表，供任意 AI 工具查询。面向 dbt 用户，开源 dbt context engineering 包提供宏，帮助把数据转化为 Agent-ready 上下文。Lake Compute 处于 private beta，是运行在 Apache Iceberg 表上的托管无服务器 dbt 转换计算引擎，可与现有仓库并行以优化各模型计算。","reason":"关注 Fivetran 如何把数据集成管道与 dbt 转换延伸到 Agent 上下文和 Iceberg 湖仓计算，是数据平台 AI 化与 Agent 数据底座的重要产品动向。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran","dbt Labs"],"topics":["平台AI化","湖仓"],"product_ids":["dbt"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","Agent接口与工具"],"use_cases":["数据接入","Agent构建"],"decision_concerns":["准确性与语义一致性","成本与性能"]},"heat":28,"quality_score":55,"trend_score":6,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":55,"shelf":"news","pinned":false,"published":"2026-10-07T21:22:46+08:00","first_seen":"2026-10-12T14:02:41.023410+08:00","original_url":"https://www.fivetran.com/blog/product-update","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"eb2c204086f2","zh_title":"Apache Iceberg Go 0.7.0 发布","zh_summary":"Apache Iceberg 社区发布 iceberg-go 0.7.0。该版本距 2026 年 5 月的 0.6.0 约四个月，合并近 750 个 PR，来自 53 位贡献者，其中 33 位为首次贡献者。iceberg-go 是 Apache Iceberg 表格式的原生 Go 实现，为 Go 应用提供读取、写入和管理 Iceberg 表的库。","reason":"Iceberg 是湖仓架构的核心表格式之一，Go 原生实现更新对使用 Go 构建数据平台与数据接入链路的团队有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Apache Iceberg"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":[],"decision_concerns":[]},"heat":26,"quality_score":56,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":56,"shelf":"news","pinned":false,"published":"2026-10-01T08:00:00+08:00","first_seen":"2026-10-11T20:53:42.021878+08:00","original_url":"https://iceberg.apache.org/blog/apache-iceberg-go-0.7.0-release/","items":[{"source":"Apache Iceberg Blog"}],"source_badge":"RSS"},{"event_id":"081f46c6c668","zh_title":"Snowflake 10.36预览：模式级数据指标函数更新","zh_summary":"Snowflake 发布 10.36 版本预览说明，计划于 2026 年 10 月 6 日完成。此次数据治理更新允许在模式级数据指标函数（DMF）关联中设置 EXCLUDE_TABLE_TYPES = ('TRANSIENT')，避免 DMF 关联到 transient tables。'TRANSIENT' 匹配 CREATE TRANSIENT TABLE 以及在 transient schema/database 中创建的表，但不包括会话临时表。另有行为变更：模式级 DMF 将跳过会话临时表，用户无需再列出 'TEMPORARY'。","reason":"该更新直接影响 Snowflake 数据质量监控与治理配置，数据从业者需关注 DMF 作用范围及临时表排除逻辑，以免监控结果与预期不一致。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["生产评估与运营"],"decision_concerns":["准确性与语义一致性"]},"heat":38,"quality_score":62,"trend_score":18,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"news","pinned":false,"published":null,"first_seen":"2026-10-10T20:37:20.530078+08:00","original_url":"https://docs.snowflake.com/en/release-notes/2026/10_36","items":[{"source":"Snowflake Release Notes"}],"source_badge":"官网"},{"event_id":"6160b9f3ecaf","zh_title":"2021年人才吸引力评分卡","zh_summary":"该2021人才吸引力评分卡回顾了2018-2020年的趋势：疫情加速了远程办公、人口增长放缓和大型城市人口外迁，中型市场在百强中占比超过一半。2019年，Wayfair与Amazon迁入佛罗里达州Duval County、Tesla在内华达州Storey County建设Gigafactory，带动部分县大幅增长。2018年，Texas和Florida凭借高就业增长与净迁入吸引居民，佛罗里达州占前50县的34%。","reason":"该报告用人口迁移、就业增长等数据评估区域人才吸引力，可作为数据驱动行业报告的参考，并为组织选址与人才配置提供区域洞察。","category":"product","category_label":"数据产品","vendors":[],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["看板与报告"],"decision_concerns":[]},"heat":26,"quality_score":58,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":58,"shelf":"news","pinned":false,"published":"2026-08-15T21:06:59.523000+08:00","first_seen":"2026-10-10T14:05:08.792168+08:00","original_url":"https://lightcast.io/resources/research/2021-talent-attraction-scorecard","items":[{"source":"Lightcast Research"}],"source_badge":"官网"},{"event_id":"ddccf55e7eee","zh_title":"斯坦福AI Index 2026：AI技能与就业趋势","zh_summary":"斯坦福 HAI 发布《AI Index 2026》，并联合 Lightcast 基于每日收集的数十亿条职位招聘数据，追踪 AI 对劳动力市场的影响。报告显示，美国职位招聘中提及 AI 技能的比例已达 2.5%，同比上升 55%，相比 2022 年上升 72%，相比十年前上升 297%。‘Agentic AI’技能簇的招聘提及量一年内增长超 280%，从 2024 年的 0.06% 升至 2025 年的 0.23%，对应美国约 9 万个职位。新加坡的 AI 职位招聘占比最高（近 5%），美国则以华盛顿特区集中度最高。","reason":"该报告用招聘数据刻画 AI 技能需求与 Agentic AI 的扩散，对数据从业者判断组织人才结构、AI 采用阶段和市场方向有参考价值。","category":"product","category_label":"数据产品","vendors":["Lightcast"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["用户采用与业务价值"]},"heat":36,"quality_score":81,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":81,"shelf":"evergreen","pinned":false,"published":"2026-08-15T21:01:25.968000+08:00","first_seen":"2026-10-10T14:05:08.792168+08:00","original_url":"https://lightcast.io/resources/research/stanford-ai-index-2026","items":[{"source":"Lightcast Research"}],"source_badge":"官网"},{"event_id":"33d6e2757304","zh_title":"Alteryx Live Query 与 BigQuery 处理非结构化数据","zh_summary":"Google Cloud 与 Alteryx 介绍 Alteryx One Live Query 与 BigQuery 的集成，用于企业在大规模非结构化数据场景下减少数据移动并实现仓库内执行。Live Query 提供浏览器端无代码环境，业务用户可构建数据管道；配合 BigQuery 可进行安全 SQL 下推。该方案可编排 Gemini 等 AI/ML 模型，从 PDF 和图像中提取信息，同时保持 BigQuery 的治理与安全。文章以发票 PDF 为例，覆盖提取、分类、校验、路由和入账流程，并借助细粒度访问策略在仓库内处理异常报告。","reason":"数据从业者可关注仓库内非结构化数据处理与 AI 抽取的集成路径，以及 SQL 下推、数据治理和减少数据移动的实践。","category":"platform","category_label":"AI 数据平台","vendors":["Google","Google Cloud","Alteryx","BigQuery"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据接入"],"decision_concerns":["权限与安全","成本与性能"]},"heat":29,"quality_score":51,"trend_score":10,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":51,"shelf":"news","pinned":false,"published":"2026-10-09T08:00:00+08:00","first_seen":"2026-10-10T14:05:08.792168+08:00","original_url":"https://cloud.google.com/blog/products/data-analytics/modernize-unstructured-data-workloads-with-alteryx-and-bigquery","items":[{"source":"Google Cloud Data Analytics Blog"}],"source_badge":"RSS"},{"event_id":"e4732f605006","zh_title":"加州基于Databricks构建行为健康公共县概况看板","zh_summary":"加州卫生保健服务部（DHCS）在 Databricks 平台上构建了 Behavioral Health Public County Profile，这是一个整合全州 58 个县行为健康数据的公共仪表盘，面向近 4000 万加州居民。该工具允许公众比较各县在行为健康规划、资金、服务交付和州目标进展上的表现，并查看人口统计、无家可归与住房相关服务数据。用户还可审查各县依据《行为健康服务法案》（BHSA）制定的三年综合计划，并监测将县级投资与结果关联的绩效指标。加州州长加文·纽森于 2026 年 10 月 1 日宣布其上线，称其用于提升政府问责与公众理解。","reason":"该案例展示 Databricks 在公共部门整合多源健康数据、构建面向公众的绩效仪表盘中的应用，对关注数据平台、政府数据透明度与 BI 落地的从业者有参考价值。","category":"bi","category_label":"BI 与可视化","vendors":["Databricks"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["看板与报告","自助分析"],"decision_concerns":["用户采用与业务价值"]},"heat":29,"quality_score":47,"trend_score":14,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":47,"shelf":"news","pinned":false,"published":"2026-10-10T05:30:00+08:00","first_seen":"2026-10-10T06:42:25.814398+08:00","original_url":"https://www.databricks.com/blog/how-california-built-its-behavioral-health-public-county-profile-databricks","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"9ba28a519ea2","zh_title":"通过受治理数据共享解决国防供应链可见性","zh_summary":"DoW（Department of War）无法看清自身供应链，成本与定价证据依赖人工数据调用和碎片化表格，下层供应商来源大多未知。自2020年以来十余项行政令和指令要求获取实际成本数据、逐层映射关键供应链并对20多万家供应商持续可见，但重大采办项目平均延期3年，审计在缺乏成本数据的单一来源合同中发现超5亿美元受质疑成本。Databricks 提出用联邦式数据交换替代接入每家承包商ERP：各承包商就地治理数据，仅向指定接收方发布版本化、质量检查过的证据。该方案由 Databricks 执行治理、所有权、访问控制、CUI 标记、血缘和审计日志，并通过 OpenSharing 跨组织边界移动受治理数据，政府获得验证证据而承包商可保持源系统封闭。","reason":"该文展示了用 OpenSharing 和联邦式治理实现跨组织数据交换的架构，涉及权限、血缘、审计、版本化质量证据等平台治理实践，可迁移到复杂供应链与多方数据协作场景。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["供应链"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理","场景与方案"],"use_cases":["方案封装与分发","生产评估与运营"],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":37,"quality_score":66,"trend_score":13,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":66,"shelf":"evergreen","pinned":false,"published":"2026-10-09T22:00:00+08:00","first_seen":"2026-10-10T06:42:25.814398+08:00","original_url":"https://www.databricks.com/blog/solving-defense-supply-chain-visibility-through-governed-data-sharing","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"78f048488594","zh_title":"dbt 支持 Amazon Redshift 数据共享读写","zh_summary":"dbt 官方宣布原生支持 Amazon Redshift 数据共享的读与写。用户可跨 Redshift 数据仓库物化模型，并在开发与 CI 环境之间隔离，无需复制或移动数据。此次还升级 dbt-redshift，从旧版 Postgres 元数据 API 迁移到 Redshift 原生的 SVV_* 系统视图和 SHOW API。官方称该版本可带来更快运行、更可靠元数据解析和高并发下更好的表现。","reason":"面向使用 dbt 与 Redshift 的数据团队，说明跨库/跨集群建模、开发与 CI 隔离及数据共享读写的新能力，并涉及元数据 API 迁移带来的性能与可靠性变化。","category":"platform","category_label":"AI 数据平台","vendors":["dbt Labs","dbt","Amazon Redshift"],"topics":[],"product_ids":["dbt"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":46,"quality_score":84,"trend_score":14,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":84,"shelf":"news","pinned":false,"published":"2026-10-10T06:02:00+08:00","first_seen":"2026-10-10T06:42:25.814398+08:00","original_url":"https://www.getdbt.com/blog/dbt-now-supports-amazon-redshift-data-sharing","items":[{"source":"dbt Blog"}],"source_badge":"RSS"},{"event_id":"fc025a8dae14","zh_title":"iSAM Funds用ClickHouse Cloud构建期权研究平台，解决万倍数据难题","zh_summary":"iSAM Funds是一家英国另类资产管理公司，专注系统化投资，其期权团队用ClickHouse Cloud研究完整期权历史数据。该平台在AWS上运行，实现35–50倍压缩和单核摄入速度提升100倍，并简化数据管道。团队面对底层资产变动带来的期权扇出，设计规模约1万个符号，需要解决分发、存储和查询的乘数效应。ClickHouse帮助其处理更多数据、降低复杂度，并缩短研究员从想法到假设测试的路径。","reason":"数据从业者应关注这个高基数市场数据场景下的OLAP平台实践，尤其是压缩、摄入性能与管道简化如何支撑量化研究。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse","AWS"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":36,"quality_score":64,"trend_score":14,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":64,"shelf":"evergreen","pinned":false,"published":"2026-10-10T02:47:59+08:00","first_seen":"2026-10-10T06:42:25.814398+08:00","original_url":"https://clickhouse.com/blog/isam-market-data-research-platform","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"5aad609d18d6","zh_title":"Snowflake External Volume 引入工作负载身份联合","zh_summary":"Snowflake 宣布 External Volumes 的工作负载身份联合（WIF）进入 Private Preview。WIF 用短时、联合身份替代存储凭证，为每个 external volume 使用唯一身份，不再依赖共享的 Snowflake 托管 IAM principal。访问云存储时，Snowflake 签署短时身份令牌，云厂商验证后授予仅限授权存储位置的临时凭证。该方案旨在提供更清晰的信任边界、隔离性、控制力与可审计性。","reason":"Snowflake 官方发布的数据平台存储访问安全机制更新，涉及 external volume、云存储、IAM 与审计，对数据平台架构和安全治理从业者有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake","AWS"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["数据接入"],"decision_concerns":["权限与安全"]},"heat":38,"quality_score":68,"trend_score":13,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"news","pinned":false,"published":"2026-10-10T00:21:12+08:00","first_seen":"2026-10-10T06:42:25.814398+08:00","original_url":"https://medium.com/snowflake/modernizing-external-volume-access-with-workload-identity-federation-e5adadde26d0?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"11bb140ae597","zh_title":"从数据平台到AI数据入口，爱分析启动2026 AI数据基础设施厂商征集","zh_summary":"爱分析启动2026年AI数据基础设施研究项目并征集厂商。文章指出，企业数据基础设施正从服务业务人员和数字化系统，转向为大模型与Agent持续供给数据，并补充业务语义、上下文管理、数据调用和安全治理能力。爱分析测算，2025年中国AI数据基础设施市场规模约450亿元，预计2029年达1,984亿元，复合增长率约44.9%。研究覆盖AI数据库、多模态数据管理、DataOps、本体平台、高质量数据集、Agent数据调用和数据安全，后续将发布厂商全景报告和实践报告，征集截止2026年10月31日。","reason":"文章给出AI数据基础设施的市场规模预测和研究范围，并指向Agent数据调用、语义上下文、数据安全等关键能力，有助于数据从业者判断平台演进方向与选型边界。","category":"platform","category_label":"AI 数据平台","vendors":[],"topics":["平台AI化","语义层"],"product_ids":[],"focus":{"id":"ai-platform","label":"AI 数据平台","priority":1,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","Agent接口与工具"],"use_cases":[],"decision_concerns":["准确性与语义一致性","权限与安全"]},"heat":28,"quality_score":46,"trend_score":13,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":46,"shelf":"news","pinned":false,"published":null,"first_seen":"2026-10-09T21:21:53.296571+08:00","original_url":"https://www.ifenxi.com/research/content/6968","items":[{"source":"爱分析"}],"source_badge":"RSS"},{"event_id":"e2eeb6c0d24f","zh_title":"爱分析2026 Data+AI应用实践报告：Data Agent落地路径","zh_summary":"爱分析发布《2026爱分析·Data+AI应用实践报告》，聚焦通用Data Agent与工业Data Agent两类市场，围绕场景选择、数据与知识准备、任务执行和持续运营提炼落地关键。报告引用Anthropic实践：其内部约95%的业务分析查询已由Claude自动完成，整体准确率约95%，背后依赖权威数据集、分析Skills、持续评测与反馈闭环。报告还结合Anthropic自助数据分析与某新能源企业智能运维实践，提供Data Agent从试点走向生产应用的建设路径。","reason":"报告把Data Agent从演示到生产的关键环节拆解为场景选择、数据与知识准备、任务执行和持续运营，并给出Anthropic高自动分析准确率案例，适合正在规划ChatBI/分析Agent落地的数据团队参考。","category":"agent","category_label":"Data Agent","vendors":["Anthropic"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","知识与上下文"],"use_cases":["自助分析","生产评估与运营"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":41,"quality_score":75,"trend_score":13,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":null,"first_seen":"2026-10-09T21:21:53.296571+08:00","original_url":"https://www.ifenxi.com/research/content/6965","items":[{"source":"爱分析"}],"source_badge":"RSS"},{"event_id":"c3e60124b535","zh_title":"StubHub、Figma、Reddit：企业BI新范式（Hex）","zh_summary":"Hex 博客指出，企业 BI 长期由数据团队构建仪表板、业务用户点击查看，造成仪表板泛滥、自助不足和请求积压。随着 AI 能力提升，业务用户希望用自然语言提问、继续探索并自行构建分析，相关 AI 工作流已在企业中自发出现。StubHub、Reddit、Figma、Ramp 等公司正在重新思考 BI：StubHub 借助 Hex 的 Threads 推动对话式自助分析，让业务用户自主回答问题。企业面临的挑战是在释放 AI 原生工作流的同时，维持信任和统一治理。","reason":"推荐理由：企业 BI 正从预置看板转向 AI 原生自助分析，文中 StubHub、Reddit 等案例提供了对话式 BI 的落地思路，数据团队可关注自助采用与治理平衡。","category":"bi","category_label":"BI 与可视化","vendors":["Hex"],"topics":["BI变局","ChatBI"],"product_ids":["hex"],"focus":{"id":"ai-analysis","label":"AI 数据分析","priority":3,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["自助分析","指标问答"],"decision_concerns":["权限与安全","用户采用与业务价值"]},"heat":27,"quality_score":52,"trend_score":7,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":52,"shelf":"evergreen","pinned":false,"published":"2026-10-08T08:00:00+08:00","first_seen":"2026-10-09T21:21:53.296571+08:00","original_url":"https://hex.tech/blog/stubhub-figma-reddit-the-new-model-for-enterprise-bi/","items":[{"source":"Hex Blog"}],"source_badge":"官网"},{"event_id":"8fe391a589c5","zh_title":"DuckDB CLI 推出 Agent 模式，优化 AI 代理查询","zh_summary":"DuckDB v2.0 CLI 新增 Agent 模式，检测到 AI 代理时会输出紧凑 Markdown 表、明确截断、提前停止失控查询、以 JSON 报错，并在长查询前预告成本。DuckDB 让 Claude Code 用英文回答 TPC-H scale factor 100 的 22 道题，每题分别在 agent 模式和 -no-agent 下运行 3 次，132 次全部正确。agent 模式下模型读取的 token 从 123.6k 降至 50.8k，减少 59%；但总成本和运行时间未明显节省，因每轮重读系统提示，节省约占总输入 0.5%，运行轮次略多（237 vs 224）。文章公开了实验设置、完整结果和后续实验报告。","reason":"数据从业者可了解数据库 CLI 如何为 AI 代理优化输出与错误处理，并看到含 token 收益和成本边界的可复现实验，对构建 Text-to-SQL/分析 Agent 有参考价值。","category":"agent","category_label":"Data Agent","vendors":["DuckDB"],"topics":["Data Agent","平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":48,"quality_score":93,"trend_score":10,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":93,"shelf":"news","pinned":false,"published":"2026-10-09T08:00:00+08:00","first_seen":"2026-10-09T21:21:53.296571+08:00","original_url":"https://duckdb.org/2026/10/09/agent-mode.html","items":[{"source":"DuckDB Engineering Blog"}],"source_badge":"RSS"},{"event_id":"cdebe30eb814","zh_title":"Snowflake 10.35 新增 STREAMS 账户使用视图","zh_summary":"Snowflake 发布 10.35 版本说明，覆盖 2026 年 9 月 24 日至 9 月 30 日。Account Usage 更新新增 ACCOUNT_USAGE.STREAMS 视图，为账户中每个流显示一行，包含源对象、基表、模式、陈旧度及其他属性。该视图于 9 月 29 日加入 Account Usage 更新，发布说明于 9 月 30 日首次发布。更多信息可参见 STREAMS view 文档。","reason":"这是 Snowflake 官方版本发布说明，新增账户级流对象监控视图，数据平台从业者可据此了解流数据管道的可观测性与治理能力变化。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估"]},"heat":31,"quality_score":55,"trend_score":11,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":55,"shelf":"news","pinned":false,"published":null,"first_seen":"2026-10-09T14:11:51.241859+08:00","original_url":"https://docs.snowflake.com/en/release-notes/2026/10_35","items":[{"source":"Snowflake Release Notes"}],"source_badge":"官网"},{"event_id":"445685a78953","zh_title":"Snowflake 10.37 版本说明预览：行为变更包","zh_summary":"Snowflake 发布 10.37 版本说明预览，该版本自 2026 年 10 月 8 日开始，计划于 10 月 13 日完成。此次包含 2026_08、2026_07、2026_06 三个行为变更包，状态分别为默认禁用可由管理员启用测试、默认启用可退出、已普遍启用且不可开关。页面提醒相关功能和变更可能尚未在所有账户可用，需关注发布完成情况与变更日志。","reason":"帮助 Snowflake 用户提前了解版本行为变更及管理员开关状态，便于规划升级、测试与兼容性处理。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["可维护性与复用"]},"heat":37,"quality_score":68,"trend_score":11,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"news","pinned":false,"published":null,"first_seen":"2026-10-09T14:11:51.241859+08:00","original_url":"https://docs.snowflake.com/en/release-notes/2026/10_37","items":[{"source":"Snowflake Release Notes"}],"source_badge":"官网"},{"event_id":"32c1d135e095","zh_title":"医疗大模型院内落地路径与产品化难点","zh_summary":"文章基于作者多年医疗数据平台与AI应用落地经验，指出截至2025年末全国已发布352个医疗垂直大模型，但能跑通“部署—使用—付费”闭环的产品仍稀缺。作者将卡点归为数据治理、临床信任、工作流嵌入、收费模式四重结构性障碍，其中清洗标注成本占AI研发总成本40%以上，通用大模型约50%医疗回答被评为“有问题”。文章对比讯飞医疗星火、京东健康京医千询与卓医、商汤医疗“大医”三条路径，并提出数据治理先行、低风险场景积累信任、能力内生进流程、立项锁定付费主体的落地次序。","reason":"对数据从业者而言，文章把医疗AI产品化失败的第一性原因落到院内多源异构数据治理、业务口径标准化和BI/360视图的数据底座上，并给出可复用的落地次序与产品化取舍，适合做垂直行业AI数据项目复盘参考。","category":"product","category_label":"数据产品","vendors":["讯飞医疗","京东健康","商汤医疗"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"ai-platform","label":"AI 数据平台","priority":1,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理","场景与方案"],"use_cases":["看板与报告","生产评估与运营"],"decision_concerns":["准确性与语义一致性","用户采用与业务价值"]},"heat":43,"quality_score":81,"trend_score":11,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":81,"shelf":"evergreen","pinned":false,"published":"2026-10-09T12:05:35+08:00","first_seen":"2026-10-09T14:11:51.241859+08:00","original_url":"https://www.woshipm.com/evaluating/6475085.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"0a5e2954e746","zh_title":"F型视觉模型与报表信息层级设计","zh_summary":"文章介绍尼尔森2006年提出、2017年更新的F型视觉模型，说明用户浏览网页时视线常呈F形扫描，重要信息应放在左上一横一竖。作者将这一模型与报表信息层级结合，主张顶部放汇总核心数据，越往下信息越细，三层结构类似麦肯锡金字塔原理。文中提到管理中层可能关注20–40个指标（如30个），并以总营收逐层拆解为例说明信息组织与钻取路径。结尾推荐AI报表工具智能小V，称其可结合企业语义模型和指标体系自动规划销售经营分析报告。","reason":"F型视觉模型与信息层级是报表和仪表板设计的实用方法，能帮助数据从业者优化看板阅读路径、提升管理层用户采用与业务价值。","category":"bi","category_label":"BI 与可视化","vendors":["智能小V"],"topics":["数据人"],"product_ids":[],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["看板与报告"],"decision_concerns":["用户采用与业务价值"]},"heat":32,"quality_score":57,"trend_score":11,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":57,"shelf":"evergreen","pinned":false,"published":"2026-10-09T10:38:17+08:00","first_seen":"2026-10-09T14:11:51.241859+08:00","original_url":"https://www.woshipm.com/ai/6475158.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"c2e2f0147991","zh_title":"从 Demo 到生产：AI Agent 缺的到底是什么？","zh_summary":"文章提出 Agent = Model + Harness 的框架，认为生产级 Agent 真正缺的不是模型，而是围绕模型搭建的记忆、工具访问、模型路由、护栏、成本控制与可观测性等 Harness 能力。Harness 被分为开发侧（记忆、工具与 MCP、检索、Prompt、编排）和运维侧（可观测性、评估、护栏、路由、成本监控、部署、扩缩容）两部分。作者对比托管方案 HaaS 与自主管理技术栈，给出团队能力、云投入、成本、治理、可移植性、预期规模、运维复杂度容忍度等选型维度，并以财务 Agent FinBot 为例逐项对比两种实现方式。","reason":"文章把 Agent 生产化中散落的基础设施工作抽象为 Harness 这一整体来设计，并给出托管与自建的选型框架，对正在把分析类 Agent 从 Demo 推向生产的数据团队有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":[],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","知识与上下文"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":34,"quality_score":62,"trend_score":11,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-10-09T14:11:51.241859+08:00","first_seen":"2026-10-09T14:11:51.241859+08:00","original_url":"https://www.infoq.cn/article/PLEWse6sEviMN99iLE93?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"d1b062467e67","zh_title":"Databricks 在 Unity Catalog 推出 Workday 联邦连接器","zh_summary":"Databricks 宣布 Unity Catalog 的 Workday Data Connect 联邦连接器进入公开 Beta，面向需要将 Workday HR 与财务数据同其他企业数据一起分析的数据平台与分析团队。通过 Lakehouse Federation，团队可直接从 Databricks Data + AI Platform 查询 Workday Data Cloud 中的 HR 和财务数据，而无需维护重复副本。管理员可在 Workday 侧共享表并授权 Integration System User 只读访问，在 Databricks 创建 OAuth 连接与 Unity Catalog 外部目录，再通过表级访问控制治理权限。用户可用 Databricks SQL、AI/BI、notebooks 和 Genie 查询该目录。","reason":"该发布把 Workday HR/财务数据以零拷贝方式接入 Databricks，并用 Unity Catalog 做表级治理，适合关注湖仓联邦查询、数据接入与权限治理的数据从业者。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","Workday"],"topics":["湖仓"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据接入","自助分析"],"decision_concerns":["权限与安全","可维护性与复用"]},"heat":34,"quality_score":63,"trend_score":10,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":63,"shelf":"news","pinned":false,"published":"2026-10-09T07:00:00+08:00","first_seen":"2026-10-09T07:24:38.195968+08:00","original_url":"https://www.databricks.com/blog/announcing-workday-data-connect-federation-unity-catalog","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"854bf2b7766d","zh_title":"Databricks 推出 Funke：湖仓原生解析 HL7v2","zh_summary":"Databricks 推出 Funke，原生支持在湖仓中解析 HL7v2 医疗消息。文章指出 HL7v2 部署广泛但结构嵌套、各系统实现有差异，过去需先转 FHIR 或用第三方引擎扁平化，带来成本、延迟和数据细节损失。Funke 是 2021 年开源 Spark 库 Smolder 的继任者，针对现代 Databricks 平台重建，结合 Unity Catalog、Declarative Automation Bundles 和 Spark Declarative Pipelines。它旨在让医疗团队直接在平台内处理临床数据，减少额外厂商依赖和数据搬移。","reason":"该发布直接关系到湖仓中的医疗数据集成与治理，适合关注数据接入、平台原生解析和降低第三方依赖的数据从业者。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":33,"quality_score":60,"trend_score":10,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"news","pinned":false,"published":"2026-10-09T06:00:00+08:00","first_seen":"2026-10-09T07:24:38.195968+08:00","original_url":"https://www.databricks.com/blog/introducing-funke-native-hl7v2-parsing-databricks","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"9145a29c01c3","zh_title":"Lakebase：用数据库分支支持编码智能体","zh_summary":"Databricks 的 Lakebase Postgres 通过数据库分支支持编码智能体开发流程。每个并行智能体可拥有完全隔离的分支，用于执行 schema 变更、迁移和测试，避免共享开发/测试库冲突及生产数据风险。分支采用 copy-on-write，可在不到 1 秒内创建，且空闲分支可 scale-to-zero，不产生计算成本。文章给出端到端开发循环示例，并提供 GitHub Actions 工作流示例仓库。","reason":"数据从业者可关注数据库如何被改造成智能体并行开发的安全隔离环境；其中分支、写时复制、缩容到零等机制对数据平台治理与成本控制有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","Lakebase"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["Agent构建"],"decision_concerns":["权限与安全","成本与性能"]},"heat":40,"quality_score":77,"trend_score":10,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":77,"shelf":"evergreen","pinned":false,"published":"2026-10-09T06:00:00+08:00","first_seen":"2026-10-09T07:24:38.195968+08:00","original_url":"https://www.databricks.com/blog/lakebase-and-agentic-sdlc-branching-databases-coding-agents","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"3d59ce90c174","zh_title":"生物医学影像的真正瓶颈是数据，而非模型","zh_summary":"文章第一部分指出，医院和卫生系统掌握原始影像数据，但数据锁在为阅片而非研究设计的PACS和厂商中立归档中；抽取队列需从临床系统取图、去标识化（PHI可能藏在DICOM头甚至像素中）并寻找算力。FDA截至2024年中批准的约950个AI/ML设备中，约723个（约76%）为放射学工具，几乎都是窄范围、人工监督的分诊、测量、重建或工作列表排序。学术界依赖MIMIC-CXR（377,110张胸片）、TCIA、fastMRI、UK Biobank及MONAI、nnU-Net、3D Slicer；但BMJ 2020综述的81项研究中仅少数为前瞻性或真实临床测试，93%和95%的研究代码与数据不可得。Medtech厂商（GE HealthCare、Siemens Healthineers、Philips、Canon）最难的是跨扫描仪泛化，需多中心训练数据并通过510(k)/PMA证明；Pharma/biotech则把影像作为测量工具，依赖RECIST、iRECIST、RANO等标准。","reason":"医疗影像AI的瓶颈不在模型而在数据获取、去标识、治理与跨机构复用；对做数据集成、治理和AI平台的人有直接借鉴。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","GE HealthCare","Siemens Healthineers","Philips","Canon"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据接入"],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":39,"quality_score":75,"trend_score":10,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-10-09T05:00:00+08:00","first_seen":"2026-10-09T07:24:38.195968+08:00","original_url":"https://www.databricks.com/blog/biomedical-imagings-real-bottleneck-data-not-model","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"15a1daab0803","zh_title":"Lakebase Postgres 借助 LTAP 将 TB 级数据加载提速至分钟级","zh_summary":"传统 Postgres 在批量加载 TB 级数据或全表分析时，会与在线事务业务争抢资源，可能造成性能下降甚至停机。Lakebase Postgres 通过 LTAP 架构把重批量操作从主计算卸载到 Spark，让事务和分析引擎处理湖中的同一份数据。beta 客户每天用 Synced Tables 加载约 10 亿行；此前一次批量加载超过 8 小时，并打满 CPU 和内存，即使自动扩缩容也需大幅过度配置 OLTP 资源。卸载到 Spark 后，加载大幅加速，在线应用负载未受影响，应用可更及时获得新数据。","reason":"数据平台与湖仓从业者应关注其 LTAP 架构如何隔离批量导入与在线事务，并用 Spark 卸载每日十亿行级加载，保护 Postgres 生产性能。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","Lakebase","Spark"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":39,"quality_score":74,"trend_score":10,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"news","pinned":false,"published":"2026-10-09T02:49:31+08:00","first_seen":"2026-10-09T07:24:38.195968+08:00","original_url":"https://www.databricks.com/blog/load-terabytes-data-minutes-lakebase-postgres","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"fd1218fe1e81","zh_title":"Databricks：自然语言分析依赖治理与上下文","zh_summary":"Databricks 产品营销负责人 Richard Tomlinson 在访谈中讨论用自然语言而非 SQL 构建数据可视化时，治理与上下文为何是关键。治理不是合规勾选项，而是企业级自然语言分析的基础设施，系统需决定查询哪些表、如何 join、用哪个指标定义以及用户可见行列。Unity Catalog 通过细粒度访问控制、行过滤、列掩码、认证信号和弃用标记来约束 AI agent；语义层中的 Ontology Snippets 也遵循同样权限。对话分析中，Genie 通过维护会话状态、元数据和编辑者指令来理解追问中的指代。","reason":"面向 ChatBI/Text-to-SQL 从业者，文章具体说明治理如何嵌入 agent 决策，以及 Unity Catalog、Ontology Snippets 和 Genie 如何处理权限与多轮上下文，可作为产品设计参考。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["ChatBI","语义层"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","权限与治理"],"use_cases":["指标问答","自助分析"],"decision_concerns":["准确性与语义一致性","权限与安全"]},"heat":27,"quality_score":53,"trend_score":5,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":53,"shelf":"evergreen","pinned":false,"published":"2026-10-07T02:16:25+08:00","first_seen":"2026-10-09T07:24:38.195968+08:00","original_url":"https://www.databricks.com/blog/ai-powered-analytics-building-data-visualizations-natural-language-vs-sql","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"67a1d2d0cb76","zh_title":"Clera 一夜之间将 500GB 生产库迁至 ClickHouse Managed Postgres","zh_summary":"Clera 的 CTO 与创始工程师撰文讲述其将 500GB 生产数据库、500 多张表迁移到 ClickHouse Managed Postgres 的过程，整个迁移在一夜之间完成。迁移前旧数据库问题频发：单次候选人查询耗时约 3 秒，分析查询遍布，CPU 曾连续 6 天跑满 100%，还出现超时与写入失败。迁移后 CPU 使用率从 100% 降至 10–20%。数据规模目前已接近 1TB，支撑其 AI 招聘匹配系统的多智能体场景。","reason":"这是一份带真实数字的数据库迁移实践复盘，展示了从传统 Postgres 迁到 ClickHouse Managed Postgres 后 CPU 占用由 100% 降到 10–20% 的实际效果，对做数据平台选型与迁移的团队有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":33,"quality_score":61,"trend_score":10,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":61,"shelf":"news","pinned":false,"published":"2026-10-09T04:51:48+08:00","first_seen":"2026-10-09T07:24:38.195968+08:00","original_url":"https://clickhouse.com/blog/clera-migrates-to-clickhouse-managed-postgres","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"cd61831e0655","zh_title":"ClickHouse Cloud 推出 JWT 认证","zh_summary":"ClickHouse Cloud 在 26.4 及以上版本引入 JWT 认证，允许使用来自 Okta、Microsoft Entra 等 OpenID Connect 身份提供商的短期令牌连接服务，替代数据库密码。客户端出示 JWT 后，ClickHouse 会校验签名与 claims，并在内存中创建临时用户，按令牌中的角色和授权执行查询。令牌过期后访问权限随之失效，从而减少长期数据库凭证的管理、轮换和撤销负担。该功能属于 ClickHouse Cloud 安全与治理能力的一部分。","reason":"数据库访问凭证治理是平台与安全团队的核心问题；该更新给出了 JWT 认证在 ClickHouse Cloud 中的具体机制、claims 结构与角色映射方式，对数据平台选型和权限治理有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":[],"decision_concerns":["权限与安全","可维护性与复用"]},"heat":42,"quality_score":82,"trend_score":9,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"news","pinned":false,"published":"2026-10-08T21:55:14+08:00","first_seen":"2026-10-09T07:24:38.195968+08:00","original_url":"https://clickhouse.com/blog/introducing-jwt-authentication-in-clickhouse-cloud","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"7b6deb18642c","zh_title":"Looker 26.20 发布说明与部署时间","zh_summary":"Looker 26.20 将按计划面向 Looker（原始版）和 Looker（Google Cloud 核心版）实例推出，预计 2026 年 10 月 12 日开始部署，10 月 25 日完成最终部署并可下载。该版本包含一项破坏性变更：自定义 TopoJSON URL 校验更新以提升安全性，可能影响启用 Google Maps Enhancements 预览功能且使用自定义 TopoJSON 文件的仪表板和 Look。新功能包括可对 Looks 应用主题，而不只是内部仪表板；同时修复了计划复制、表格可视化、Slack 集成预览、仪表板无限重载、BigQuery JDBC 数据类型解析和仪表板联动筛选器自动补全等问题。","reason":"Looker 是主流 BI 与可视化平台，版本更新涉及安全性、可视化行为和集成稳定性，数据团队应关注升级影响与修复项。","category":"bi","category_label":"BI 与可视化","vendors":["Google","Looker","Google Cloud","BigQuery"],"topics":[],"product_ids":["looker"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化","权限与治理"],"use_cases":["看板与报告","自助分析"],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":46,"quality_score":70,"trend_score":26,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"news","pinned":false,"published":"2026-10-09T15:00:00+08:00","first_seen":"2026-10-09T07:24:38.195968+08:00","original_url":"https://docs.cloud.google.com/looker/docs/release-notes#October_08_2026","items":[{"source":"Google Looker Release Notes"},{"source":"Google Looker Release Notes"},{"source":"Google Looker Release Notes"}],"source_badge":"RSS"},{"event_id":"a5e85b0e5b72","zh_title":"语义层能否不靠人一条条建？Aloudata 口径自动盘点","zh_summary":"Aloudata 官方博客讨论 Data Agent 所需语义层如何构建，指出指标口径盘点中约 90% 的工作量花在找材料、读代码、还原口径和对齐分歧上。Aloudata BIG 通过解析 SQL 与任务日志建立算子级血缘，并做口径裁剪，结合大模型生成可核对的盘点报告。某客户选取两个业务域对约 2000 个指标自动盘点，客户校对后数据比对准确性超过 99%；某银行项目口径盘点效率提升 300 倍，原 60 个人月减少到一周。确认后的口径进入 Aloudata CAN，实现指标管理、执行和消费统一。","reason":"语义层建设长期卡在人工盘点指标口径，本文给出机器自动盘点、算子级血缘和可量化客户案例，对 Data Agent 与语义层落地成本很有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Aloudata"],"topics":["语义层","Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","知识与上下文"],"use_cases":["Agent构建"],"decision_concerns":["准确性与语义一致性","成本与性能"]},"heat":42,"quality_score":84,"trend_score":8,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":84,"shelf":"evergreen","pinned":false,"published":"2026-10-08T14:32:46+08:00","first_seen":"2026-10-08T21:33:56.614861+08:00","original_url":"https://aloudata.com/blogs/can-semantic-layer-be-built-without-manual-work","items":[{"source":"Aloudata 博客"}],"source_badge":"官网"},{"event_id":"dcacd92fda95","zh_title":"用Replit和Lakebase在Databricks构建受治理企业应用","zh_summary":"Databricks 官方博客介绍 Replit 与 Databricks 的集成，帮助企业在受治理环境中完成从开发到部署应用。团队可用 Replit Agent 基于实时 Databricks 数据构建前端，并自动配置 Lakebase Postgres 数据库，再部署为 Databricks Apps。部署后应用继承用户认证、安全访问控制，并与 Unity Catalog 集成，从而减少安全与基础设施审批环节。文章面向业务负责人、数据分析师和开发者，说明如何用自然语言提示构建生产级应用。","reason":"数据从业者可了解 Databricks 如何把 Agentic coding、Lakebase 与 Unity Catalog 治理结合，缩短企业数据应用从构建到生产部署的路径。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","Replit"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"ai-analysis","label":"AI 数据分析","priority":3,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理","场景与方案"],"use_cases":["Agent构建","方案封装与分发"],"decision_concerns":["权限与安全","用户采用与业务价值"]},"heat":31,"quality_score":59,"trend_score":9,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":59,"shelf":"news","pinned":false,"published":"2026-10-08T21:00:00+08:00","first_seen":"2026-10-08T21:33:56.614861+08:00","original_url":"https://www.databricks.com/blog/how-build-governed-enterprise-apps-databricks-replit-and-lakebase","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"21a48ac63d78","zh_title":"为什么BigQuery在实时分析上不及ClickHouse Cloud","zh_summary":"ClickHouse Cloud在CostBench中每美元性能比BigQuery高438倍。文章沿数据从摄入到查询服务的路径解释差距：ClickHouse Cloud用两节点2-CPU HA摄入服务，异步插入后按(sym,t)排序，并在同节点对增量MV按(sym,day)预聚合，使原始数据与预聚合同步推进。BigQuery的流式摄入、聚类和MV刷新则分开进行。该对比基于可复现的CostBench仓库，但股票行情数据集需单独授权。","reason":"对数据从业者而言，这是理解实时分析架构选型与成本性能差异的一手基准：文章用可复现的CostBench结果和摄入/预聚合路径，解释ClickHouse Cloud与BigQuery为何不同。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse","BigQuery"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入"],"decision_concerns":["成本与性能"]},"heat":43,"quality_score":86,"trend_score":9,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":86,"shelf":"evergreen","pinned":false,"published":"2026-10-08T18:49:15+08:00","first_seen":"2026-10-08T21:33:56.614861+08:00","original_url":"https://clickhouse.com/blog/clickhouse-vs-bigquery-real-time-performance-per-dollar","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"fa2922eb6e68","zh_title":"Anthropic发布经济指数连接器，让Claude直接查询AI使用数据","zh_summary":"Anthropic推出Economic Index连接器，允许用户在Claude中直接查询该指数数据。该指数衡量AI在经济中的实际使用情况，用户可询问哪些职业使用AI最多、教师用Claude做什么等。连接器在claude.ai中一分钟启用，无需安装，并会提示数据局限性。完整数据集仍在其网站免费提供。","reason":"提供了一种通过对话查询AI使用经济数据的范式，对Data Agent和分析Agent的产品设计有参考价值，同时揭示了AI对劳动市场的实际影响数据。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","Agent接口与工具"],"use_cases":["数据发现与搜索","指标问答"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"news","pinned":false,"published":"2026-08-26T00:13:14+08:00","first_seen":"2026-10-08T14:07:39.910785+08:00","original_url":"https://www.anthropic.com/news/anthropic-economic-index-connector","items":[{"source":"Anthropic Economic Index"}],"source_badge":"官网"},{"event_id":"e2626ff1bf17","zh_title":"一线员工调研：排班、薪酬透明度与数字工具期望差距扩大","zh_summary":"DailyPay与Workday发布《The Frontline Worker Expectation Gap》研究，指出一线员工期望与雇主供给之间存在显著差距。78%的一线员工在接受新排班前会计算通勤、儿童照护等成本，46%在两次发薪之间借钱，69%每班后查看工资。排班控制权重要度72%但满意度仅51%；薪酬清晰度重要度84%但仅57%非常满意；移动工具重要度70%但满意度53%。报告称缩小这些差距可在招聘、留任与生产率上带来关键优势。","reason":"该研究用调研数据揭示一线员工体验指标与招聘、留任、生产率之间的关联，可作为组织人才与HR分析场景的数据驱动洞察案例。","category":"insight","category_label":"AI分析","vendors":["Workday","DailyPay"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["用户采用与业务价值"]},"heat":29,"quality_score":64,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":64,"shelf":"news","pinned":false,"published":"2026-09-17T21:00:00+08:00","first_seen":"2026-10-08T14:07:39.910785+08:00","original_url":"https://newsroom.workday.com/2026-09-17-New-Research-on-Frontline-Workers-Finds-Widening-Expectation-Gap-in-Schedule-Flexibility,-Pay-Clarity-and-Digital-Tools","items":[{"source":"Workday Newsroom"}],"source_badge":"RSS"},{"event_id":"a5ce3472770d","zh_title":"Apache Iceberg C++ 0.4.0 发布","zh_summary":"Apache Iceberg 社区宣布 Apache Iceberg C++ 0.4.0 发布。该版本包含来自 26 位贡献者的 160 多个 PR，其中 12 位为首次贡献者。iceberg-cpp 是 Apache Iceberg 表格式的原生 C++ 实现，提供在 C++ 应用中读取、写入和管理 Iceberg 表的库。","reason":"Iceberg 是湖仓表格式关键基础设施，C++ 原生实现更新对需要在 C++ 生态中读写 Iceberg 表的数据平台与引擎团队有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Apache Iceberg"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":[]},"heat":25,"quality_score":56,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":56,"shelf":"news","pinned":false,"published":"2026-09-26T08:00:00+08:00","first_seen":"2026-10-08T14:07:39.910785+08:00","original_url":"https://iceberg.apache.org/blog/apache-iceberg-cpp-0.4.0-release/","items":[{"source":"Apache Iceberg Blog"}],"source_badge":"RSS"},{"event_id":"67a7cef4fcc2","zh_title":"Hex用评估驱动AI功能开发：错误率从21%降至3%","zh_summary":"Hex 的 Generative Apps 让用户通过聊天构建自定义数据应用；Quick Edits 用小模型（GPT-6 Luna/Claude Haiku 4.5）把图表样式修改做得比完整 agent 快 20 倍且更便宜。团队从开发初期就用 eval 驱动该功能，评测案例从最初几百条扩展到 1,800 条，并用编码 agent 对数百个改动做爬山式筛选。结果错误编辑率从 21% 降到 3%，且多数提升来自模型外围的 harness，而非提示词。文章还建议参考 Anthropic 的 eval 设计与 hill-climbing 指南，并强调要优先减少错误编辑而非错误转交。","reason":"对构建 ChatBI/Data Agent 的团队，Hex 给出了可落地的 eval 指标选择、评测集构建和 hill-climbing 调优经验，并指出收益常来自 harness 而非 prompt。","category":"agent","category_label":"Data Agent","vendors":["Hex"],"topics":["Data Agent"],"product_ids":["hex"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化","Agent接口与工具"],"use_cases":["看板与报告","生产评估与运营"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":43,"quality_score":86,"trend_score":7,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":86,"shelf":"evergreen","pinned":false,"published":"2026-10-08T08:00:00+08:00","first_seen":"2026-10-08T14:07:39.910785+08:00","original_url":"https://hex.tech/blog/we-used-evals-to-improve-ai-feature/","items":[{"source":"Hex Blog"}],"source_badge":"官网"},{"event_id":"052a4392ec5b","zh_title":"2023人才吸引力记分卡：美国各州与郡县排名","zh_summary":"Lightcast发布2023 Talent Attraction Scorecard，基于其数据平台分析美国各州、大县和小县的就业增长、教育程度、区域竞争力和迁移等指标。报告使用IRS报税地址变更数据追踪人口迁移，发现肯塔基州在迁移类别排名第4、密苏里州第5，偏离阳光地带和远程办公热门目的地的常规趋势。山区西部表现突出，爱达荷州、犹他州、亚利桑那州、内华达州等地在就业增长或教育程度进入前十，综合排名爱达荷第4、犹他第6、亚利桑那第8、内华达第9。报告旨在帮助社区和区域强化积极因素并识别增长所需调整。","reason":"用IRS迁移、就业与教育数据构建区域人才吸引力排名，展示数据驱动的人才与区域增长分析，对关注组织人才和劳动力市场数据应用的从业者有参考价值。","category":"insight","category_label":"AI分析","vendors":["Lightcast"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"news","pinned":false,"published":"2026-08-15T21:07:57.662000+08:00","first_seen":"2026-10-08T07:09:28.718756+08:00","original_url":"https://lightcast.io/resources/research/talent-scorecard","items":[{"source":"Lightcast Research"}],"source_badge":"官网"},{"event_id":"73a1ea512cd9","zh_title":"Lightcast发布2025人才吸引记分卡","zh_summary":"Lightcast发布《2025 Talent Attraction Scorecard》，基于人口增长、就业增长、人口结构和薪资数据，对美国各州及大都市区/小都市区的人才吸引力进行排名。佛罗里达州稳居人才吸引和就业增长第一，得克萨斯州第二；怀俄明州升至第4，爱达荷州第3。大都市层面，领先都会区形成从山地西部延伸至阳光地带和东南部的走廊，前十大都会区中五个在佛罗里达、三个在得克萨斯，达拉斯-沃斯堡和奥斯汀分列第一、第二。报告还总结六项人才流动趋势，供社区领导者制定人才吸引策略并对比周边地区。","reason":"该报告用人口、就业、薪资等数据给出美国州与都会区人才吸引力排名及流动趋势，适合关注组织人才、区域劳动力市场和数据驱动决策的从业者参考。","category":"insight","category_label":"AI分析","vendors":["Lightcast"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":33,"quality_score":74,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"news","pinned":false,"published":"2026-08-15T21:07:18.061000+08:00","first_seen":"2026-10-08T07:09:28.718756+08:00","original_url":"https://lightcast.io/resources/research/talent-attraction-scorecard-25","items":[{"source":"Lightcast Research"}],"source_badge":"官网"},{"event_id":"6fa801a59b33","zh_title":"Jev与DuckDB：在SQL中用自然语言条件","zh_summary":"TypeSafe AI于2026年9月15日发布Jev模型，它返回带概率的类型化答案而非文本段落，支持是/否、选项和评分三类问题。发布一周内，社区为DuckDB开发了扩展，可用自然语言条件对CSV、Parquet或表进行过滤、分类和打分，约1000行数据耗时约10秒。Jev报告端到端延迟70-500毫秒，输入token价格0.042美元/百万。文章介绍了Jev的机制、DuckDB扩展的工作方式及相关讨论。","reason":"把LLM式语义判断以类型化、可SQL集成的形式落地到DuckDB分析流程，为数据从业者提供了在数仓内做文本分类和过滤的新路径，并涉及成本、延迟与准确性的工程权衡。","category":"platform","category_label":"AI 数据平台","vendors":["DuckDB","TypeSafe AI"],"topics":["平台AI化","ChatBI"],"product_ids":[],"focus":{"id":"ai-analysis","label":"AI 数据分析","priority":3,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","知识与上下文"],"use_cases":["数据接入","指标问答"],"decision_concerns":["准确性与语义一致性","成本与性能"]},"heat":33,"quality_score":74,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"news","pinned":false,"published":"2026-09-29T08:00:00+08:00","first_seen":"2026-10-08T07:09:28.718756+08:00","original_url":"https://duckdb.org/2026/09/29/jev.html","items":[{"source":"DuckDB Engineering Blog"}],"source_badge":"RSS"},{"event_id":"248a0f91d772","zh_title":"Databricks 云数仓成本预算与告警设置","zh_summary":"文章指出，云数据仓库的 SQL 仓库常因 BI 看板、临时分析等突发负载导致月末账单超支，例如季度评审中一个临时仓库自动扩展服务 80 个 Tableau 用户。作者主张从被动看账单转为主动治理：按仓库、团队或 BI 工作负载设置预算和阈值告警，并用仪表板实时呈现使用趋势。文中还列出被动成本管理失效的四个原因，包括无法归因到团队/查询、无人负责预算、发现过晚和人工审查无法扩展，并强调在 Databricks Data & AI Platform 上落实归因、预算、告警、看板和优化。","reason":"数据平台成本治理是数据从业者必须面对的运营问题，文章给出了 Databricks SQL 仓库场景下的预算、告警与归因思路，可帮助控制 BI 与临时分析带来的云成本失控。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","Tableau","Power BI","Looker"],"topics":[],"product_ids":[],"focus":{"id":"ai-dashboard","label":"AI 看板","priority":4,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理","报表与可视化"],"use_cases":["看板与报告","生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":32,"quality_score":63,"trend_score":7,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":63,"shelf":"evergreen","pinned":false,"published":"2026-10-08T03:02:06+08:00","first_seen":"2026-10-08T07:09:28.718756+08:00","original_url":"https://www.databricks.com/blog/set-budgets-and-alerts-cloud-data-warehouse-costs","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"03313007af0f","zh_title":"Databricks Apps 全面可用：支持用户身份按需授权","zh_summary":"Databricks Apps 现全面支持 on-behalf-of-user（OBO）授权，开发者可在 Databricks 平台上构建权限感知的数据与 AI 应用。应用以登录用户身份调用受支持的 Databricks API 时，Unity Catalog 会沿用该用户的数据权限，包括行过滤和列掩码，API scopes 则限制应用可代表用户执行的操作。应用仍可用专属 service principal 处理共享配置、指标写入等自身操作。文中以销售洞察助手为例，说明它只能访问销售人员被授权的账户和字段，并建议按每个操作决定由应用还是用户身份来治理权限。","reason":"对数据平台与 Agent 开发者而言，OBO 把权限治理从应用代码中剥离并直接复用 Unity Catalog，是构建企业级数据/AI 应用的关键基础设施，尤其影响权限安全与用户采用。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化","Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理","Agent接口与工具"],"use_cases":["Agent构建","数据接入"],"decision_concerns":["权限与安全"]},"heat":41,"quality_score":84,"trend_score":7,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":84,"shelf":"news","pinned":false,"published":"2026-10-08T00:40:00+08:00","first_seen":"2026-10-08T07:09:28.718756+08:00","original_url":"https://www.databricks.com/blog/now-ga-building-permission-aware-databricks-apps-behalf-user-authorization","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"f00206fc1d6a","zh_title":"如何将 dbt ETL 管道迁移到 Databricks","zh_summary":"Databricks 官方博客介绍将现有 dbt 转换项目重新指向 Databricks Lakehouse 的迁移方法。文章称只需更换 dbt-databricks 适配器与连接配置、处理少量 SQL 方言差异，无需重写 DAG 或业务逻辑。Databricks 提供 Delta Lake、Apache Iceberg、Unity Catalog 与 Lakeflow Jobs 等能力，并称已有超过 3,000 家组织在 Databricks 上运行 dbt。作者建议从转换层开始增量迁移，以便逐模型验证输出、降低风险并更快看到成本收益。","reason":"对正在评估数仓/湖仓迁移或 dbt 落地 Databricks 的数据团队，这篇官方实践给出了从适配器切换、SQL 方言到治理与成本收益的迁移思路。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","dbt Labs"],"topics":["湖仓"],"product_ids":["dbt"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":[],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":34,"quality_score":69,"trend_score":5,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":69,"shelf":"evergreen","pinned":false,"published":"2026-10-07T02:53:48+08:00","first_seen":"2026-10-08T07:09:28.718756+08:00","original_url":"https://www.databricks.com/blog/how-repoint-dbt-etl-pipelines-databricks","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"c043c6996461","zh_title":"ClickHouse 回顾 Postgres Summit 2026 集成","zh_summary":"ClickHouse 团队回顾了在纽约举办的 Postgres Summit US 2026，并介绍了其对 Postgres 与 ClickHouse 集成的持续投入。演讲《Postgres in da ClickHouse》提到 ClickHouse 开源分析数据库、ClickHouse Cloud 以及新产品 ClickHouse Managed Postgres，目标是让 Postgres 处理 OLTP、ClickHouse 处理 OLAP。现场演示了 pg_stat_ch、pg_clickhouse、chdb_hook 和 WalShadow 四项技术，其中 pg_clickhouse 可将 22 条 TPC-H 查询中的 16 条下推到 ClickHouse，WalShadow 提供从 Postgres 到 ClickHouse 的物理复制，实现亚秒级分析可见性。chdb_hook 还支持通过 Postgres COPY 从 URL 导入导出数据湖文件，并支持 ClickHouse 数据格式与云对象存储。","reason":"该文来自 ClickHouse 官方博客，具体展示 Postgres 与 ClickHouse 在 OLTP/OLAP 集成、查询下推、数据导入导出和实时复制上的技术方案，对数据平台与实时分析从业者有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案"],"use_cases":["数据接入"],"decision_concerns":["成本与性能"]},"heat":35,"quality_score":70,"trend_score":7,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"news","pinned":false,"published":"2026-10-08T01:05:28+08:00","first_seen":"2026-10-08T07:09:28.718756+08:00","original_url":"https://clickhouse.com/blog/postgres-summit-us-2026","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"f2e20584f9b0","zh_title":"用iPhone跑TPC-H：DuckDB对比Databricks集群","zh_summary":"作者在iPhone 17 Pro上用DuckDB运行TPC-H基准测试（25/50/100/200 GB），对比Databricks Serverless SQL的XS/S/M集群。结果显示iPhone在多数规模下更快，最大规模也具竞争力。Databricks最小集群有24核CPU、128GB内存，成本4.2美元/小时。原因包括DuckDB单节点设计避免shuffle，以及查询规划编译固定成本占比高。","reason":"这篇实测挑战了大数据必须分布式的假设，用具体基准和成本数据说明现代单机硬件能处理多数实际分析负载，对数据平台选型与成本优化有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran","Databricks","DuckDB"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":42,"quality_score":84,"trend_score":7,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":84,"shelf":"evergreen","pinned":false,"published":"2026-10-08T07:06:43+08:00","first_seen":"2026-10-08T07:09:28.718756+08:00","original_url":"https://www.fivetran.com/blog/i-benchmarked-databricks-against-my-iphone","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"fb2ee3737ecf","zh_title":"Treehouse TDT 登陆 Snowflake 原生应用，打通大型机数据","zh_summary":"Snowflake 推出 Snowflake Datastream（私有预览），把与 Apache Kafka 兼容的流服务原生引入 Snowflake。Treehouse Software 借此重构 Treehouse Dataflow Toolkit（TDT），推出 TDT Snowflake Native App，使大型机数据交付完全运行在 Snowflake 内，并以 Datastream 作为 Kafka 层。该方案可把 Db2、VSAM、Adabas、IMS、IDMS 等大型机数据流式写入 Snowflake 原生表或 Apache Iceberg 表，数秒内可查询，并继承 RBAC、Horizon Catalog、分类、血缘和掩码策略。它面向希望减少独立 Kafka 基础设施、统一治理与降低数据交付延迟的企业数据集成场景。","reason":"该消息涉及 Snowflake 将 Kafka 兼容流服务原生化，以及大型机数据到 Snowflake 的原生交付方案，对数据集成、实时接入、治理与成本控制有直接影响。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake","Treehouse Software"],"topics":["湖仓","实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案","权限与治理"],"use_cases":["数据接入","方案封装与分发"],"decision_concerns":["权限与安全","成本与性能"]},"heat":30,"quality_score":58,"trend_score":6,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":58,"shelf":"news","pinned":false,"published":"2026-10-07T22:01:05+08:00","first_seen":"2026-10-08T07:09:28.718756+08:00","original_url":"https://medium.com/snowflake/mainframe-data-meets-snowflake-datastream-tdt-goes-snowflake-native-d68259fa00ad?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"6df9230e2f9b","zh_title":"不含数据的 DuckDB 数据库：远程 Parquet 视图目录","zh_summary":"文章介绍一种用法：DuckDB 数据库文件可以不存数据，只保存指向外部文件的视图定义，例如对象存储上的 Parquet。这样的文件无论描述的数据多大都保持几百 KB，附加后即可看到一组可查询的命名关系。作者引用 Nikolas Goebel 的 “DuckDB doesn't need data”，认为数据库已把数据存储与读取分离，DuckDB 可成为数据云的浏览器。文中以荷兰铁路开放数据集为例，演示安装 httpfs 并创建指向远程数据的视图，构建可分享的目录或语义层。","reason":"DuckDB 以零数据副本、远程 Parquet 视图和可分享目录的方式承载语义层，对湖仓、数据目录与轻量分析架构有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["DuckDB"],"topics":["语义层","湖仓"],"product_ids":[],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","指标与语义"],"use_cases":["数据接入","方案封装与分发"],"decision_concerns":["可维护性与复用","成本与性能"]},"heat":37,"quality_score":76,"trend_score":5,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":76,"shelf":"evergreen","pinned":false,"published":"2026-10-07T08:00:00+08:00","first_seen":"2026-10-08T07:09:28.718756+08:00","original_url":"https://duckdb.org/2026/10/07/view-only-mode.html","items":[{"source":"DuckDB Engineering Blog"}],"source_badge":"RSS"},{"event_id":"3bdb33764a67","zh_title":"Google Earth Engine 推出 AI 助手 Ask辅助地理空间编程","zh_summary":"Google Earth Engine 在其 Code Editor 中推出 Ask 面板，直接集成 Gemini 能力。用户可使用自己的 Gemini API key，在编辑器内编写、调试、理解和优化地理空间查询。Ask 会自动结合当前脚本、导入的资产与几何数据以及会话历史等上下文，并支持查看 diff 后合并进脚本。启动时可选 Gemini 3 Flash Preview、Gemini 3.1 Pro Preview 和 Gemini 3.5 Flash 等模型。","reason":"该功能展示了地理空间数据平台如何把上下文感知的 AI 助手嵌入开发工作流，提升查询编写与调试效率；对关注平台 AI 化和 Data Agent 落地的数据从业者有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Google","Google Cloud","Google Earth Engine","Gemini"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","Agent接口与工具"],"use_cases":[],"decision_concerns":["成本与性能","用户采用与业务价值"]},"heat":26,"quality_score":57,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":57,"shelf":"news","pinned":false,"published":"2026-09-28T08:00:00+08:00","first_seen":"2026-10-07T21:25:19.821983+08:00","original_url":"https://cloud.google.com/blog/products/data-analytics/accelerate-geospatial-coding-with-ai-in-google-earth-engine","items":[{"source":"Google Cloud Data Analytics Blog"}],"source_badge":"RSS"},{"event_id":"d31716d36370","zh_title":"让BI迁移不那么痛苦","zh_summary":"文章讨论从Tableau、Power BI、Looker等迁移到Metabase等BI工具时的复杂性，并分享降低迁移工作量的经验。建议迁移前按业务部门审计仪表板，定义“活跃”标准，例如最近30天是否被打开。对不活跃仪表板先归档而非删除，同时检查订阅，必要时了解其实际用途并把单指标合并到核心仪表板。这样可把250个仪表板的迁移范围显著缩小。","reason":"BI迁移和仪表板治理是数据团队常见的高成本项目，文章给出了可落地的审计、归档和收敛范围方法，能帮助从业者控制迁移项目风险与工作量。","category":"bi","category_label":"BI 与可视化","vendors":["Metabase","Tableau","Power BI","Looker"],"topics":[],"product_ids":["looker","metabase"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["看板与报告"],"decision_concerns":["用户采用与业务价值","可维护性与复用"]},"heat":31,"quality_score":63,"trend_score":5,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":63,"shelf":"evergreen","pinned":false,"published":"2026-10-07T08:00:00+08:00","first_seen":"2026-10-07T21:25:19.821983+08:00","original_url":"https://www.metabase.com/blog/making-bi-migration-suck-less","items":[{"source":"Metabase Blog"}],"source_badge":"RSS"},{"event_id":"7daf943a93a4","zh_title":"用Go构建会话有序的Kafka管道","zh_summary":"文章介绍如何在 Apache Kafka 分区之上实现会话级消息顺序，支持数千个独立通道的严格有序。方案包含应用层路由、一致哈希、按会话 worker、原地重试和连续水位提交。作者还讨论了再均衡排空、背压、卡住偏移检测、幂等、优雅关闭和死信队列等生产加固。该实践来自面向企业客户的实时对话 AI 平台，并经过大量性能测试。","reason":"文章虽非分析型数据产品，但属于数据基础设施中的流处理技术实践，对构建可靠实时数据管道、保证消息顺序和故障恢复的工程师有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":[],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["可靠性与评估"]},"heat":41,"quality_score":83,"trend_score":6,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":83,"shelf":"evergreen","pinned":false,"published":"2026-10-07T17:00:00+08:00","first_seen":"2026-10-07T21:25:19.821983+08:00","original_url":"https://www.infoq.com/articles/apache-kafka-golang-session-ordered-pipeline/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"e800e0369acc","zh_title":"Spanner Omni 正式 GA：用软件替代原子钟与 Colossus","zh_summary":"Google 宣布 Spanner Omni 正式 GA，这是可在客户本地数据中心、其他云或笔记本上运行的分布式 SQL 数据库版本。为脱离 Google 基础设施，Spanner Omni 用类似 Colossus 的抽象层替代 Colossus 文件系统，并用软件时间同步替代基于原子钟和 GPS 的 TrueTime。Paxos 共识、自动分片和同步复制保持不变，Google 内部基准称单区域部署可在 PB 级数据上支持每秒数百万查询，但该产品不提供可用性 SLA。实践者关注运维变化，认为故障域转移给客户后需重新推导仲裁/见证拓扑，并关心 p99 尾延迟、补丁升级和回滚等负担。","reason":"数据从业者应关注 Spanner Omni 如何把依赖专用硬件的分布式数据库带到任意环境，以及无 SLA 下的尾延迟、运维复杂度和一致性取舍。","category":"platform","category_label":"AI 数据平台","vendors":["Google"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","可维护性与复用"]},"heat":34,"quality_score":68,"trend_score":6,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"news","pinned":false,"published":"2026-10-07T12:43:00+08:00","first_seen":"2026-10-07T21:25:19.821983+08:00","original_url":"https://www.infoq.com/news/2026/10/spanner-omni-deploy-anywhere-ga/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"643b4690d563","zh_title":"湖仓能否取代数仓：2026基准与实证","zh_summary":"文章讨论湖仓是否比数仓更适合现代数据平台。Databricks称其生产SQL工作负载在2024年末较2022年基线快77%，性能指数约提升4倍，并给出BI、数据探索和ETL分别约14%、13%和9%的改进，归因于Photon、查询规划、缓存、预测优化等。Lumen Technologies将133 TB电信数据从Cloudera/本地迁移到Databricks Lakehouse后，查询性能提升90%，小时级查询缩短到分钟级。文章认为数仓适合分析人员写SQL查询干净表，而湖仓可同时服务BI、数据工程、ML、流处理和AI Agent。","reason":"对数据平台选型、湖仓/数仓架构取舍和SQL性能评估有直接参考，且提供生产负载与客户迁移量化证据；但需注意其来自Databricks官方博客，结论有厂商立场。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","Cloudera"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化","权限与治理"],"use_cases":["看板与报告","数据接入"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":36,"quality_score":74,"trend_score":5,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"evergreen","pinned":false,"published":"2026-10-07T00:35:12+08:00","first_seen":"2026-10-07T14:02:48.658718+08:00","original_url":"https://www.databricks.com/blog/lakehouse-better-data-warehouse-2026-benchmarks-and-proof","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"444b07d4567c","zh_title":"Fivetran、dbt与Databricks Lakeflow如何协同","zh_summary":"Fivetran 官方博客指出，Databricks Lakeflow 看似分别与 Fivetran、dbt 在数据集成和转换上竞争，实际可作为互补能力组合。Fivetran 提供覆盖 770+ 数据源的托管集成，将数据送入 Delta Lake 等开放表格式；dbt 用代码定义转换，并配套测试、版本控制和文档；Lakeflow 基于 Spark Declarative Pipelines 支持批流处理，并通过 Jobs 编排包括 dbt 项目在内的下游任务。三者可共同支撑现代开放数据平台，用于实时账户健康表等运营与分析场景。","reason":"帮助数据从业者理解 Databricks 生态下数据集成、转换与编排的分工，以及 Fivetran/dbt 如何与 Lakeflow 组合落地。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran","dbt","Databricks"],"topics":["湖仓","实时分析"],"product_ids":["dbt"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","场景与方案"],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":26,"quality_score":52,"trend_score":5,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":52,"shelf":"evergreen","pinned":false,"published":"2026-10-07T05:28:58+08:00","first_seen":"2026-10-07T14:02:48.658718+08:00","original_url":"https://www.fivetran.com/blog/how-fivetran-dbt-and-databricks-lakeflow-work-together","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"ddec884f46e7","zh_title":"单票价格从13跌到7块，快递行业接下来靠什么活","zh_summary":"文章依据国家邮政局9月18日数据及2015-2025年快递统计，指出收入增速7.4%跑赢件量增速4.6%，并非涨价，而是冷链、大件、生鲜、医药等高价值件占比提升，单票价格已从13元跌至约7.54元。作者认为末端成本占单票成本四到五成，规模经济见顶，行业需从规模经济转向范围经济，在同一张网络上叠加更多服务。真正的瓶颈不只是技术，而是一线组织能力和责任机制，能否让快递员承接冷链等新业务。结论是快递竞争将从更低价格转向更高服务结构与组织能力。","reason":"用行业数据解释快递收入增速跑赢件量的结构变化，给出规模经济到范围经济的判断，并指出组织能力落地瓶颈，对物流供应链和数据化经营分析有参考价值。","category":"insight","category_label":"AI分析","vendors":[],"topics":["供应链","组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":30,"quality_score":60,"trend_score":6,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-10-07T12:46:53+08:00","first_seen":"2026-10-07T14:02:48.658718+08:00","original_url":"https://www.woshipm.com/share/6473949.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"ae224a31c6ec","zh_title":"DuckDB 发布 1.5.6 补丁版本","zh_summary":"DuckDB 发布 1.5（Variegata）系列第六个补丁版本 1.5.6，包含 bug 修复、性能改进和安全补丁。官方按正确性、崩溃与内部错误、通用修复和杂项分类，列出了 LIMIT 下推、UNNEST 下推、Parquet、ICU、WAL 恢复等修复编号。安装方式见安装页面，完整发布说明在 GitHub。博客还预告了 DuckDB v2.0 on Windows。","reason":"DuckDB 是数据从业者常用的嵌入式分析数据库，本次补丁修复查询正确性、崩溃恢复、Parquet 读写等问题，使用该版本的用户应关注并评估升级。","category":"platform","category_label":"AI 数据平台","vendors":["DuckDB"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["可靠性与评估","准确性与语义一致性"]},"heat":30,"quality_score":66,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":66,"shelf":"news","pinned":false,"published":"2026-09-28T08:00:00+08:00","first_seen":"2026-10-07T14:02:48.658718+08:00","original_url":"https://duckdb.org/2026/09/28/announcing-duckdb-156.html","items":[{"source":"DuckDB Engineering Blog"}],"source_badge":"RSS"},{"event_id":"3bab1efbb5de","zh_title":"IFCO 在 Databricks 扩展大型 dbt 项目：性能、可见性与调试","zh_summary":"IFCO 运营着全球最大的可重复使用包装池之一，管理数亿个箱子和托盘，并通过 barcode/RFID/GPS 等追踪信号把数十亿原始事件转化为 KPI。其数据平台团队与 Databricks Forward Deployed Engineering 合作，将转换逻辑保留在 dbt 中，并在 Databricks 上把每个增量设置映射到具体的 Delta Lake 写入行为（聚类列、写入触及范围、merge/replace）。在正确数据粒度上优化后，核心语义层作业每日运行时间减少超过 60%，并停用了昂贵的夜间全量刷新。文章围绕大规模 dbt 项目的性能、可见性与调试展开。","reason":"如果团队在 Databricks/Delta Lake 上运行大规模 dbt 和语义层管道，这篇第一方实践提供了增量模型性能优化、成本下降与调试可见性的具体经验。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","dbt Labs"],"topics":["语义层","湖仓"],"product_ids":["dbt"],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","权限与治理"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能","准确性与语义一致性"]},"heat":41,"quality_score":85,"trend_score":5,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-10-07T00:00:00+08:00","first_seen":"2026-10-07T02:27:19.515831+08:00","original_url":"https://www.databricks.com/blog/scaling-and-operating-large-dbt-project-databricks-ifcos-data-team-performance-visibility-and-debugging","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"549d1d1ddade","zh_title":"Meta广告MCP服务器上线Databricks，接入Genie","zh_summary":"Databricks Marketplace 现已上架 Meta 的广告 MCP 服务器，企业可将其连接到 Genie，用自然语言同时探索 Meta 广告表现与 Databricks 中受治理的业务数据。该 MCP 服务器暴露 25+ 个覆盖活动生命周期的工具，包括创建活动/广告组、调整预算与出价、定义受众、管理创意与目录、拉取表现数据和诊断信号质量。这延续了双方此前的合作：Meta Conversions API 已登陆 Databricks Marketplace，用于发送第一方转化信号。目标是减少 CSV 导出和自维护 Marketing API 集成，让 churn 分数、LTV、归因和 margin 表等洞察更直接进入广告投放决策。","reason":"数据从业者应关注Databricks如何通过MCP把外部广告平台工具接入Genie，使受治理指标、业务模型与营销执行在同一对话中联动，代表数据平台与AI Agent接口融合的新方向。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","Meta"],"topics":["平台AI化","Data Agent"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","指标与语义"],"use_cases":["指标问答","自助分析"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":32,"quality_score":65,"trend_score":4,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"news","pinned":false,"published":"2026-10-06T20:45:00+08:00","first_seen":"2026-10-07T02:27:19.515831+08:00","original_url":"https://www.databricks.com/blog/meta-ads-mcp-databricks","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"7a101e693f8f","zh_title":"Databricks 为何在实时分析上难敌 ClickHouse Cloud","zh_summary":"ClickHouse 官方博客称，在 CostBench 中 ClickHouse Cloud 的每美元性能比 Databricks 高 752 倍，并沿数据准备到查询服务链路解释差距。ClickHouse Cloud 使用两节点 2 CPU 的高可用摄入服务，通过异步插入、按 (sym, t) 排序、增量物化视图预聚合和后台 merge 完成数据准备。Databricks 则将摄入、聚簇和物化视图刷新拆分为不同服务，原文以此对比两条数据准备链路。所有基准代码和结果在 CostBench 仓库，股票行情数据因授权不能重新分发。","reason":"对数据平台选型和实时分析架构设计有参考价值：文章给出 752× 成本性能差距及 ClickHouse/Databricks 在摄入、排序、预聚合与刷新机制上的具体差异。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse","Databricks"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":36,"quality_score":75,"trend_score":4,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-10-06T20:26:14+08:00","first_seen":"2026-10-07T02:27:19.515831+08:00","original_url":"https://clickhouse.com/blog/clickhouse-vs-databricks-real-time-performance-per-dollar","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"e1b8af84b84f","zh_title":"用 OpenSearch 与 AI Agent 监控 MWAA ETL 管道","zh_summary":"当 MWAA 编排的 ETL 管道跨多个 AWS 服务时，故障排查需要在 AWS Glue、Amazon EC2 和 Amazon MWAA 各自的 CloudWatch 日志组之间来回查找，凌晨 2 点排障尤其耗时。该方案通过 CloudWatch 实时流式传输把日志集中到 Amazon OpenSearch Service，并部署运行在 Amazon Bedrock AgentCore 上的 OpenSearch MCP server 与 ETL analysis agent。文章提供 CloudFormation 模板和 Amazon SageMaker AI notebook，用于搭建示例架构与演示 ETL 作业。目标读者是数据工程师、DevOps 工程师和云工程师，用 AI agent 加速根因定位、解读日志并给出修复建议。","reason":"展示如何把多服务 ETL 日志集中并接入 AI Agent 做根因定位，为数据平台可观测性与运维自动化提供可复制的架构参考。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon OpenSearch Service","Amazon MWAA","AWS Glue","Amazon EC2"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案","Agent接口与工具"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","可维护性与复用"]},"heat":35,"quality_score":72,"trend_score":5,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-10-07T00:17:46+08:00","first_seen":"2026-10-07T02:27:19.515831+08:00","original_url":"https://aws.amazon.com/blogs/big-data/monitoring-mwaa-orchestrated-etl-pipelines-with-amazon-opensearch-service/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"7b960331578f","zh_title":"AWS Glue 上使用 DuckDB 与 S3 Tables 的高性价比 ETL","zh_summary":"AWS 官方博客介绍在 AWS Glue 作业中运行 DuckDB 的模式：DuckDB 作为嵌入式、进程内、向量化 SQL 引擎，可直接读取 S3 上的 Parquet，并通过 Iceberg REST 端点将 Apache Iceberg 表写入 Amazon S3 Tables，无需单独同步目录。该模式适合以 SQL 为中心的过滤、连接、聚合，以及按小时或按天运行的聚合、增量加载和汇总等频繁调度任务，并强调快速启动。AWS Glue 6.0 是当前版本，运行在现代化运行时上，相比旧版本价格降低 30%。文章给出可运行代码和具体 ETL 用例，并将实测成本与运行时间同执行相同工作的 Spark 作业进行比较；该模式与 AWS Glue 上的 Apache Spark 互补而非替代。","reason":"数据从业者可了解如何在 Serverless ETL 中按任务形态选择 DuckDB 或 Spark，并利用 S3 Tables/Iceberg 降低频繁 SQL 作业的成本与启动开销。文中包含可运行代码和与 Spark 的实测成本、运行时间对比，具备直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","DuckDB"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":43,"quality_score":90,"trend_score":5,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":90,"shelf":"evergreen","pinned":false,"published":"2026-10-07T00:13:02+08:00","first_seen":"2026-10-07T02:27:19.515831+08:00","original_url":"https://aws.amazon.com/blogs/big-data/cost-effective-etl-with-duckdb-and-amazon-s3-tables-on-aws-glue/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"1683f2ca1c36","zh_title":"Amazon EMR 8.1.0 支持多目录跨账户跨格式查询","zh_summary":"Amazon EMR 8.1.0 推出 multi-catalog 支持，通过 RedirectingSessionCatalog（RSC）作为 Spark 默认 catalog，自动从 AWS Glue 元数据识别表格式并路由到对应处理器。它允许在单一统一 catalog 中查询 Iceberg、Hudi、Delta Lake 和 Hive 表，并支持跨 AWS 账户访问多个 AWS Glue Data Catalog。用户无需复制数据即可跨账户 join 表，并可在查询时动态发现远程 catalog。该方案面向数据网格中域团队分散持有数据、分析集中运行的常见场景。","reason":"对使用 AWS EMR 与 Glue 的数据平台团队，它直接解决多开放表格式和多账户数据网格下的统一查询与跨账户 join 痛点，减少数据拷贝和复杂权限变通。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon EMR","AWS Glue"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据接入"],"decision_concerns":["权限与安全","可维护性与复用"]},"heat":35,"quality_score":72,"trend_score":5,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"news","pinned":false,"published":"2026-10-07T00:05:27+08:00","first_seen":"2026-10-07T02:27:19.515831+08:00","original_url":"https://aws.amazon.com/blogs/big-data/query-across-accounts-and-table-formats-with-multi-catalog-in-amazon-emr/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"f00a1275a4aa","zh_title":"Strata：能对LLM说不的语义层","zh_summary":"Hacker News 热帖（25赞、16评论）介绍 Strata，一个自称兼具受治理语义层与自助分析能力的产品，可与自有 BI 工具配合并内置仪表板。它对比 dbt/MetricFlow、Cube、Snowflake Semantic Views、Looker、Power BI 和 Metabase，强调 grain-safe、联邦热层与亚秒级查询。面向 Agent，Strata 提供安全检索和自然语言解析，并把验证循环作为 Agent API。页面称通过 Docker 和自有编码 Agent 可在 15 分钟从设置到洞察。","reason":"语义层是 Text-to-SQL/ChatBI 与 Data Agent 准确性的关键组件；该产品直接面向 Agent 治理与检索，值得数据从业者评估其定位和技术差异。","category":"platform","category_label":"AI 数据平台","vendors":["Strata","dbt/MetricFlow","Cube","Snowflake","Looker"],"topics":["语义层","Data Agent"],"product_ids":["dbt","looker","metabase"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","Agent接口与工具"],"use_cases":["自助分析","Agent构建"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":18,"quality_score":29,"trend_score":9,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":29,"shelf":"news","pinned":false,"published":"2026-09-30T22:59:57+08:00","first_seen":"2026-10-07T02:27:19.515831+08:00","original_url":"https://strata.do/","items":[{"source":"Hacker News（数据关键词）"}],"source_badge":"HN"},{"event_id":"ca06eb030d88","zh_title":"如何在 Snowflake 中构建自主 AI Agent？","zh_summary":"文章探讨能否在 Snowflake 中构建自主 AI Agent，并以“自动解决支持工单”为例，说明从读取工单、解释问题到请求补充信息、修改记录或重启失败流程的可能行动。作者区分了对话式助手与自主运营 Agent：后者由工单、监控事件或调度触发，可自行选择下一步、调用工具并检查结果。文中介绍用 Snowflake Cortex Agents 等能力搭建 Agent harness，并讨论代理何时有足够证据采取行动以及如何监督执行。","reason":"为 Data Agent 在企业数据平台上的落地提供架构分层与监督边界参考，尤其适合评估 Snowflake 内构建自主运营 Agent 的可行性与治理要求。","category":"agent","category_label":"Data Agent","vendors":["Snowflake"],"topics":["Data Agent","平台AI化"],"product_ids":["snowflake-cortex"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","权限与安全"]},"heat":34,"quality_score":70,"trend_score":5,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-10-06T22:01:03+08:00","first_seen":"2026-10-07T02:27:19.515831+08:00","original_url":"https://medium.com/snowflake/can-you-build-autonomous-ai-agents-in-snowflake-c251bab066cf?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"7d03159f7684","zh_title":"2026年RevOps团队最佳BI工具盘点","zh_summary":"Hex 盘点了 2026 年面向 RevOps 团队的 6 款最佳 BI 工具，核心论点是 AI 正改变 RevOps 与数据团队的分工。文章引用 Hex《State of Data Teams 2026》数据称，AI 与自动化在数据负责人首要目标中的占比六个月内从 4% 跃升至 27%。以 Clay 为例，一位企业销售负责人用 Hex 在一小时内搭建了三个销售业绩看板，替代了原有零散工具。作者认为好工具应让 RevOps 用自然语言自行探究管道变化原因，而数据团队继续维护底层治理数据与上下文。","reason":"文章结合 Hex 自研调研数据，讨论 AI 如何扩大 RevOps 自助分析边界、BI 工具选型标准随之变化，对关注 BI 变局与 Data Agent 落地的数据从业者有参考价值。","category":"bi","category_label":"BI 与可视化","vendors":["Hex","Clay"],"topics":["BI变局"],"product_ids":["hex"],"focus":{"id":"ai-dashboard","label":"AI 看板","priority":4,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["自助分析","看板与报告"],"decision_concerns":["用户采用与业务价值"]},"heat":29,"quality_score":64,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":64,"shelf":"news","pinned":false,"published":"2026-10-01T08:00:00+08:00","first_seen":"2026-10-07T02:27:19.515831+08:00","original_url":"https://hex.tech/blog/best-bi-tools-for-revops-teams/","items":[{"source":"Hex Blog"}],"source_badge":"官网"},{"event_id":"a749656d502d","zh_title":"Hex：评估BI工具对Databricks指标视图支持","zh_summary":"Hex 的文章指出，Databricks 正从湖仓扩展为更广泛的分析平台，Unity Catalog 指标视图于 2026 年 4 月 2 日 GA。指标视图可集中定义受治理的度量、维度和关系，并在消费 Databricks 数据的工具和 Agent 间复用。文章认为，连接 Databricks 只是基础，BI 工具更应原生保留指标视图作为事实来源，支持自助分析与仪表板工作流，并兼顾其他业务上下文。目标是从已有语义工作获得更多杠杆，而不是在另一套专有建模层中重建。","reason":"帮助数据从业者理解 Databricks 指标视图 GA 后如何评估 BI 工具的语义层兼容性，尤其是 MEASURE 语义与跨工具复用，这直接影响指标一致性和 AI/BI 分析质量。","category":"bi","category_label":"BI 与可视化","vendors":["Databricks","Hex"],"topics":["语义层","BI变局"],"product_ids":["hex"],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","报表与可视化"],"use_cases":["自助分析","看板与报告"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":29,"quality_score":63,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":63,"shelf":"evergreen","pinned":false,"published":"2026-10-01T08:00:00+08:00","first_seen":"2026-10-07T02:27:19.515831+08:00","original_url":"https://hex.tech/blog/best-bi-tools-for-databricks-metric-views/","items":[{"source":"Hex Blog"}],"source_badge":"官网"},{"event_id":"c975ecb799c8","zh_title":"BigQuery 上最佳 BI 工具：8 个平台对比","zh_summary":"Hex 发布面向 BigQuery 的 BI 工具选型对比，评估 8 个平台。文章指出 BigQuery 已不仅用于静态报表，还支撑自助分析、交互式看板、应用以及 AI 问答代理。选型关键不只是连接器，还包括生成 SQL、slot 争用与查询账单、BigQuery 治理保留，以及仓库数据和上下文能否支撑可信自助服务。Power BI 和 Tableau 采用 Import 模式/Hyper 抽取，会降低扫描成本但带来滞后和容量限制。","reason":"对以 BigQuery 为核心数据栈的团队，这篇对比给出了 BI 选型的评估框架：查询下推、成本、身份治理与 AI 可信问答。能帮助数据从业者判断工具在自助分析、看板和 Agent 场景下的真实差异。","category":"bi","category_label":"BI 与可视化","vendors":["Hex","BigQuery","Power BI","Tableau"],"topics":["BI变局","ChatBI"],"product_ids":["hex"],"focus":{"id":"ai-analysis","label":"AI 数据分析","priority":3,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化","权限与治理"],"use_cases":["自助分析","看板与报告"],"decision_concerns":["成本与性能","权限与安全"]},"heat":26,"quality_score":58,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":58,"shelf":"evergreen","pinned":false,"published":"2026-10-01T08:00:00+08:00","first_seen":"2026-10-07T02:27:19.515831+08:00","original_url":"https://hex.tech/blog/bi-tools-for-bigquery/","items":[{"source":"Hex Blog"}],"source_badge":"官网"},{"event_id":"c4451479dae7","zh_title":"Hex：兼容 Snowflake Semantic Views 的 BI 工具","zh_summary":"Hex 官方博客讨论哪些 BI 工具最能利用 Snowflake Semantic Views。Snowflake Semantic Views 是在数仓内定义指标、维度、事实和实体关系的 schema 级对象，相关 DDL 于 2025 年 Summit 正式可用，标准 SQL 查询在 2026 年跟进，Cortex Analyst 也能基于同一对象生成 SQL。文章认为受治理的定义应靠近底层数据并供多个下游工具复用；随着智能体能力提升，可访问的业务上下文质量比能否生成 SQL 更关键。Hex 的 State of Data Teams 调研还显示，31% 受访者把数据质量和缺乏信任视为 AI 应用最大障碍。","reason":"数据从业者可借此理解 Snowflake Semantic Views 对 BI/分析平台的兼容要求，以及语义层如何成为 AI 智能体共享业务上下文的关键基础设施。","category":"bi","category_label":"BI 与可视化","vendors":["Snowflake","Hex"],"topics":["语义层","BI变局"],"product_ids":["snowflake-cortex","hex"],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","报表与可视化"],"use_cases":["指标问答","看板与报告"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":26,"quality_score":57,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":57,"shelf":"evergreen","pinned":false,"published":"2026-10-01T08:00:00+08:00","first_seen":"2026-10-07T02:27:19.515831+08:00","original_url":"https://hex.tech/blog/snowflake-semantic-views/","items":[{"source":"Hex Blog"}],"source_badge":"官网"},{"event_id":"4e03fd51d0a6","zh_title":"当Agent写代码，开源为何仍重要","zh_summary":"知名开源项目的维护者正面对新式收件箱：拉取请求数量更高，且格式整洁、初看合理。一个人一下午就能生成上百个PR，维护者仍需逐一阅读以找出三个真正有价值的。文章认为，贡献成本趋近于零，过去三十年作为承诺信号的开源贡献机制正在失效。作者还指出开放权重模型并非开源软件，并认为SQL在查询与检索上仍比自然语言更精确完整。","reason":"从数据基础设施开源生态视角，讨论AI Agent降低贡献成本后，维护者如何评估贡献、开源信号与治理的变化；对理解数据平台开源项目协作与AI生成内容的可靠性有参考价值。","category":"product","category_label":"数据产品","vendors":["PingCAP","TiDB"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":25,"quality_score":50,"trend_score":5,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-10-06T23:45:08+08:00","first_seen":"2026-10-07T02:27:19.515831+08:00","original_url":"https://www.pingcap.com/blog/open-source-agents-write-code/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"ef1ba3c7dd5a","zh_title":"Snowflake 10.33 发布：动态表洞察正式可用","zh_summary":"Snowflake 10.33 版本发布说明覆盖 2026 年 9 月 13 日至 18 日，核心是 Dynamic Tables Insights 正式 GA。该功能主动分析动态表定义与刷新执行指标，在 Snowsight 中给出影响刷新延迟或计算成本的性能洞察。用户可在动态表列表或单表详情页查看 Insights，并用 Analyze with CoCo 打开会话解释问题、生成可直接使用的修复 DDL。更新日志显示 9 月 14 日预览发布、9 月 16 日最终发布，9 月 18 日补充 DT Insights GA 条目。","reason":"Snowflake 动态表用户可关注刷新性能与成本优化；CoCo 自动生成 DDL 修复也体现平台 AI 化运维趋势。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":38,"quality_score":79,"trend_score":4,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":79,"shelf":"news","pinned":false,"published":null,"first_seen":"2026-10-06T14:25:23.441706+08:00","original_url":"https://docs.snowflake.com/en/release-notes/2026/10_33","items":[{"source":"Snowflake Release Notes"}],"source_badge":"官网"},{"event_id":"e7a841a9d56c","zh_title":"用 Amazon Redshift MCP 服务器自动执行运营审查","zh_summary":"季度末，Redshift 工作负载随业务增长，定期运营审查可确认集群是否仍适配当前用量并发现成本与性能优化空间。Redshift 自带自动表优化、自动 WLM、自动 vacuum 等自主功能，Serverless 还提供 AI 驱动的弹性扩缩容。但表设计、连接模式、查询模式变化和部署规格仍需人工判断，企业支持流程通常每集群消耗 4–8 小时整理诊断查询、解读结果并形成优先级报告。本文介绍如何用 Amazon Redshift MCP server（结合此前 Kiro 自然语言查询实践）自动化这一运营审查流程。","reason":"数据从业者可了解如何用 MCP/Agent 自动化数仓运营审查，在成本、性能与人工判断之间建立可复用的周期流程。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon Redshift"],"topics":["Data Agent","平台AI化"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":35,"quality_score":74,"trend_score":3,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"evergreen","pinned":false,"published":"2026-10-05T23:44:45+08:00","first_seen":"2026-10-06T08:08:17.726042+08:00","original_url":"https://aws.amazon.com/blogs/big-data/run-an-automated-operational-review-with-the-amazon-redshift-mcp-server/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"661daa33a256","zh_title":"Elastic分享：构建可复用的Agent评估框架","zh_summary":"Elastic首席数据科学家Susan Chang分享了如何将孤立的、临时的AI Agent评估转变为统一的生产级框架。她讨论了如何平衡LLM-as-a-judge与确定性规则，并打通Python数据科学评估与TypeScript生产代码。该框架通过深度追踪在复杂RAG和网络安全工作负载中捕捉回归，同时保留领域上下文。","reason":"对于正在构建Data Agent或分析Agent的团队，该分享提供了从临时评估到生产级评估框架的工程实践，尤其涉及LLM评估与确定性规则结合、跨语言集成和追踪回归，具有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["Elastic"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","知识与上下文"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","准确性与语义一致性"]},"heat":34,"quality_score":72,"trend_score":3,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-10-05T19:19:00+08:00","first_seen":"2026-10-06T08:08:17.726042+08:00","original_url":"https://www.infoq.com/presentations/elastic-ai-agent-evaluations/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"66638a56112b","zh_title":"生产级LLM的平台工程手册：幻觉率从15%降至1.5%","zh_summary":"作者分享了在大型零售企业库存准确率平台中运行多Agent LLM系统的经验：早期约15%的Agent回复是幻觉，6个月后降至1.5%，关键不是更换基础模型，而是把LLM栈当作平台基础设施而非应用功能。文章提出共享LLM平台应具备提示词注册与版本管理、schema强制、按请求归属token成本等能力，并通过自动重试循环、意图校验门、资源服务器默认拒绝授权、请求入口埋点监控幻觉率与团队token成本来实现治理。作者强调标准APM工具无法发现语义退化，事后补做成本归因会耗费数周工程时间。","reason":"文章用真实零售库存场景给出可量化的LLM平台治理机制，对构建Data Agent、分析Agent的团队在可靠性、权限控制和成本归因上有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":[],"topics":["Data Agent","平台AI化"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":40,"quality_score":85,"trend_score":3,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-10-05T19:00:00+08:00","first_seen":"2026-10-06T08:08:17.726042+08:00","original_url":"https://www.infoq.com/articles/platform-engineering-playbook-production-llms/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"04fb8493780b","zh_title":"英国技能革命：构建数据驱动技能体系","zh_summary":"Lightcast发布《Future-Ready Workforce Collection》中的《The UK Skills Revolution》报告，讨论英国劳动力市场在技术采用和新政策推动下的转型。报告指出，英国普通岗位的前20项技能自2021年以来变化了33%。它使用Lightcast Occupation Taxonomy（LOT）构建UK Skills Disruption Index，衡量400多个职业从2021到2024年的技能构成变化。变化最大的是信息技术与计算机科学、市场营销与公共关系、设计媒体与写作，最小的是表演艺术、社区与社会服务、交通。","reason":"这是一份用职业分类法和技能变化指数分析人才与技能需求的数据驱动报告，对数据从业者理解组织人才分析、指标构建和证据驱动决策有参考价值。","category":"insight","category_label":"AI分析","vendors":["Lightcast"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","指标与语义"],"use_cases":["看板与报告"],"decision_concerns":["准确性与语义一致性"]},"heat":36,"quality_score":79,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":79,"shelf":"evergreen","pinned":false,"published":"2026-08-15T21:01:52.702000+08:00","first_seen":"2026-10-05T22:42:04.242217+08:00","original_url":"https://lightcast.io/resources/research/uk-skills-revolution-25","items":[{"source":"Lightcast Research"}],"source_badge":"官网"},{"event_id":"480c1590c586","zh_title":"自信地犯错：AI分析师在Snowflake上有无语义模型对比","zh_summary":"文章用一个可复现实验，让运行在Claude Sonnet 4.5上的AI agent扮演分析师，通过JDBC访问Snowflake的TPC-H演示库（LINEITEM 6000万行、SALES_ORDER 1500万行、CUSTOMER 150万行，X-Small仓库）。在“前”场景中，agent只有JDBC连接和数据模型；在“后”场景中，它获得Snowflake语义视图。没有语义模型时，agent六道题只答对两题，准确率33%。作者指出，错误答案的共性更能揭示企业AI数据策略的脆弱点，并强调语义层对AI分析准确性的重要性。","reason":"它用具体实验量化了语义模型对AI分析师准确率的影响，并分析错误答案的共性，对评估Data Agent、Text-to-SQL和语义层落地很有参考价值。","category":"agent","category_label":"Data Agent","vendors":["Snowflake"],"topics":["Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","Agent接口与工具"],"use_cases":["指标问答","Agent构建"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":40,"quality_score":85,"trend_score":3,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-10-05T22:01:06+08:00","first_seen":"2026-10-05T22:42:04.242217+08:00","original_url":"https://medium.com/snowflake/confidently-wrong-i-let-an-ai-analyst-loose-on-snowflake-with-and-without-a-semantic-model-3ac30c6fe10a?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"ddc6673776cd","zh_title":"DuckDB 与 Hugging Face：直接查询数据集","zh_summary":"DuckDB 与 Hugging Face 合作推出 hf:// 路径方案，自 DuckDB v0.10.3（2024年5月22日发布）起，用户可用 SELECT 直接查询 Hugging Face Hub 上的数据集，无需先下载。Hugging Face 数据集以 git 仓库形式存储，常见格式包括 CSV、JSONL 和 Parquet，DuckDB 通过 httpfs 扩展解析 hf://datasets/... 路径并读取文件。文章介绍了该集成的工作方式、示例查询和适用场景，例如直接分析 cais/mmlu 等数据集。","reason":"数据从业者可直接在 DuckDB 中查询 Hugging Face 上的 CSV、JSONL 和 Parquet 数据集，减少数据搬运，适合机器学习数据集分析与复用。","category":"platform","category_label":"AI 数据平台","vendors":["DuckDB","Hugging Face"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["成本与性能"]},"heat":36,"quality_score":81,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":81,"shelf":"evergreen","pinned":false,"published":"2026-09-25T08:00:00+08:00","first_seen":"2026-10-05T13:44:15.423806+08:00","original_url":"https://duckdb.org/2026/09/25/hugging-face.html","items":[{"source":"DuckDB Engineering Blog"}],"source_badge":"RSS"},{"event_id":"93d95b246d70","zh_title":"Vercel 与 TiDB Cloud Starter：AI 应用全栈数据库实践","zh_summary":"文章介绍在 Vercel 上运行 AI 应用时，如何选择能适配 serverless 和 edge runtime 的数据库，并重点推荐 TiDB Cloud Starter。它指出边缘运行时会破坏传统 TCP 连接池，而 TiDB Cloud Starter 通过 HTTPS 连接；从 v0.dev 默认数据库迁移到 TiDB 只需改连接字符串。TiDB 提供原生 VECTOR 类型，可把 embeddings 与业务行数据放在一起，避免额外同步向量库；Vercel Marketplace 集成会自动写入连接环境变量。TiDB 是开源分布式 SQL 数据库，兼容 MySQL，TiDB Cloud Starter 为全托管、自动扩缩容版本，约一秒完成配置。","reason":"对数据从业者，本文具体讨论 serverless/edge 场景下数据库连接、向量存储与部署集成，涉及 AI 应用数据架构的选型和落地。","category":"platform","category_label":"AI 数据平台","vendors":["PingCAP","TiDB","Vercel"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","场景与方案"],"use_cases":["数据接入"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":28,"quality_score":63,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":63,"shelf":"evergreen","pinned":false,"published":"2026-09-25T04:52:55+08:00","first_seen":"2026-10-05T13:44:15.423806+08:00","original_url":"https://www.pingcap.com/blog/build-with-tidb-cloud-starter-vercel-database/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"6104559e9a96","zh_title":"通过 REGISTER/UNREGISTER API 防止目录锁定","zh_summary":"随着组织采用湖仓架构，数据正从专有数据仓库迁移到开放存储和表格式，使 Spark、Trino 等引擎无需复制即可访问。开放格式只是一部分，真正开放还需要目录之间的互操作性与灵活治理。REGISTER 端点可将已有表挂载到任意 IRC 目录；UNREGISTER 端点被加入 Apache Iceberg REST 目录规范，让旧目录忘记该表并返回指针，避免 DROP 清理底层数据与元数据。这样可在不重写、导出或复制文件的情况下在目录间迁移表。","reason":"目录锁定是湖仓选型的关键风险；文章解释 Iceberg REST 目录 REGISTER/UNREGISTER 机制，帮助数据平台团队评估跨引擎、跨目录可移植性。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":[],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":34,"quality_score":72,"trend_score":3,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-10-05T05:29:27.035783+08:00","first_seen":"2026-10-05T05:29:27.035783+08:00","original_url":"https://www.databricks.com/blog/unlocking-data-portability-preventing-catalog-lock-register-and-unregister-apis","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"cdc582d9ae58","zh_title":"Agent记忆不在对话：企业数仓沉淀为可治理共享语义记忆","zh_summary":"QCon 上海站演讲预告，卡奥斯 COSMOPlat 工业智能首席科学家余锦泽将分享《Agent 的记忆不在对话里：把企业数仓沉淀为可治理的共享语义记忆》。他指出 Mem0、Zep、Letta/MemGPT 等主流框架多解决跨会话记住用户，而工业多智能体更缺的是指标分子分母、工单号多表写法等企业数据语义。方案包括写入侧由大模型提议、真实数据裁决、证据分级入库，冲突用时间轴校验、双源融合与对抗评审消解，使用侧按对象锚定动态构建上下文。其结论是企业语义记忆需治理，写错比遗忘更危险，实测只注入一半语义时正确率反而低于不注入。","reason":"对 Data Agent、语义层和数仓治理从业者，这篇提纲给出了把企业数据语义做成可治理 Agent 记忆的工程路径与反例，尤其适合关注指标口径、冲突消解和评估的人。","category":"agent","category_label":"Data Agent","vendors":["卡奥斯 COSMOPlat","Mem0","Zep","Letta/MemGPT"],"topics":["Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","知识与上下文"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":32,"quality_score":68,"trend_score":2,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-10-04T18:00:00+08:00","first_seen":"2026-10-05T05:29:27.035783+08:00","original_url":"https://www.infoq.cn/article/M4mgbKf4RDv5AKTwQvFH?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"5e7420583c0b","zh_title":"Lightcast发布2024数字技能展望报告","zh_summary":"Lightcast发布《Digital Skills Outlook 2024》，以交互页面呈现15个全球劳动力市场的数字技能趋势。报告引用数据称，92%的岗位需要至少部分数字技能；2023年Gallup与Amazon基于Lightcast数据的研究估算，数字技能年全球价值约18.5万亿美元，占全球GDP的12%。欧盟委员会数据显示，70%欧洲企业认为缺乏数字技能阻碍投资，40%欧洲成年人缺乏基础数字技能。报告分为Changing Skills、City Hotspots、Occupation Focus三部分，并附方法论、数据与工具。","reason":"Lightcast是劳动力市场数据厂商，该报告用技能数据揭示数字技能供需缺口、热点城市与职业需求，对组织人才分析、行业报告和数据产品从业者具有参考价值。","category":"product","category_label":"数据产品","vendors":["Lightcast"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-15T21:04:51.630000+08:00","first_seen":"2026-10-03T19:44:22.646446+08:00","original_url":"https://lightcast.io/resources/research/the-lightcast-digital-skills-outlook-2024","items":[{"source":"Lightcast Research"}],"source_badge":"官网"},{"event_id":"3fd2fe2ea75f","zh_title":"OECD与Lightcast：全球AI技能需求趋势","zh_summary":"Lightcast与OECD发布报告，基于14个国家的招聘数据，分析2019至2022年AI技能需求变化。研究发现，AI技能需求平均增长33%，但AI岗位占比仍较低，美国为0.84%，新西兰为0.11%。报告认为这些岗位将对就业市场产生超比例影响，并为企业识别AI所需技能提供参考。","reason":"为数据团队和组织人才规划提供全球AI技能需求的量化参考，帮助判断招聘与技能投资方向。","category":"insight","category_label":"AI分析","vendors":["Lightcast"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":36,"quality_score":72,"trend_score":7,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-15T21:00:24.336000+08:00","first_seen":"2026-10-03T19:44:22.646446+08:00","original_url":"https://lightcast.io/resources/research/oecd-ai-emerging-trends","items":[{"source":"Lightcast Research"},{"source":"Lightcast Research"}],"source_badge":"官网"},{"event_id":"60ad2a548483","zh_title":"Genie One 如何重塑财务团队工作","zh_summary":"文章介绍数据智能 AI 同事 Genie One 如何帮助财务团队从汇报数字转向解释业务变化并支持决策。它基于已批准的指标、财年逻辑、实体结构和企业术语，帮助分析预算差异、收入差异及其驱动因素。文中以 EMEA 收入差异、实际支出超计划 15% 等查询为例，说明财务业务伙伴可在分享前审查答案背后的表格和定义。Genie One 还能把重复分析转化为可复用工作流，同时不替代财务判断或现有控制。","reason":"这是 Data Agent/ChatBI 在财务分析场景的典型落地案例，涉及指标定义、业务上下文和可复用分析工作流，数据从业者可借此了解 Genie One 的产品定位与财务团队用法。","category":"agent","category_label":"Data Agent","vendors":["Databricks","Genie One"],"topics":["Data Agent","财务经营"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","知识与上下文"],"use_cases":["指标问答","生产评估与运营"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":22,"quality_score":48,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":48,"shelf":"evergreen","pinned":false,"published":"2026-10-02T06:46:51+08:00","first_seen":"2026-10-03T13:22:16.393713+08:00","original_url":"https://www.databricks.com/blog/how-genie-one-reshapes-work-finance-teams","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"d366d7dca12f","zh_title":"数据库即产品：AI记忆设备规模化时什么会崩","zh_summary":"文章复盘 AI 笔记产品 Plaud 的架构问题：早期用 MySQL 存元数据、S3 存内容，二者没有共享事务边界，一致性压力被推到应用层。数据量约 3 亿行时，schema 变更需要维护窗口，数据库发布节奏反过来限制产品迭代。对 AI 记忆产品而言，每次交互都是数据库操作，架构债会直接变成产品故障。将元数据层迁移到 TiDB 后，Plaud 获得在线 DDL、约 10 倍 QPS 余量和 P95 低于 10ms。","reason":"数据从业者可从中看到 AI 产品背后的数据库选型、元数据/内容拆分一致性、规模化 DDL 与延迟瓶颈，对设计高并发低延迟数据层有直接参考。","category":"platform","category_label":"AI 数据平台","vendors":["PingCAP","TiDB","MySQL","AWS S3"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":34,"quality_score":75,"trend_score":1,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-10-02T04:06:50+08:00","first_seen":"2026-10-03T13:22:16.393713+08:00","original_url":"https://www.pingcap.com/blog/ai-hardware-data-architecture-at-scale/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"c4c3bbd6249e","zh_title":"如何选择首批 Genie Agents 以最大化影响","zh_summary":"文章指出，仅2026年就创建了超过100万个 Genie Agents，数据团队面临的问题已不是能否构建，而是先构建哪些。作者基于金融服务、能源、零售等行业的数十次 Genie Agents 部署，提出围绕5个核心变量评估候选工作流，以提升采用率、性能与效果。文中将“万能 Agent”和“炫技 Demo”列为常见失败类型，并强调优先选择能加速具体决策、需求高频重复、数据与元数据就绪的工作流。","reason":"对正在落地 Data Agent/ChatBI 的团队，这篇提供了从业务影响、重复需求和数据就绪度筛选首批 Agent 的实操框架，可减少 pilot 失败并提升采用。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["Data Agent"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案","数据资产"],"use_cases":["Agent构建"],"decision_concerns":["用户采用与业务价值","准确性与语义一致性"]},"heat":33,"quality_score":72,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-10-03T00:15:00+08:00","first_seen":"2026-10-03T06:19:03.336456+08:00","original_url":"https://www.databricks.com/blog/how-choose-your-first-genie-agents-maximum-impact","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"de87ef36dd84","zh_title":"Snowflake原生表迁移Iceberg：决策与权衡（上）","zh_summary":"本文分两部分，第一部分讨论为何以及如何将 Snowflake 原生表转换为 Iceberg。Snowflake 原生表在性能优化、灾备、复制和治理方面集成最完整，适合纯 Snowflake 负载。但企业环境需要 Spark、Trino、Athena、Databricks、DuckDB 等多引擎读写同一 Iceberg 表，避免 ETL 复制带来延迟和复杂度。Iceberg 生态更复杂、功能仍有差距，通常总拥有成本更高，需要权衡。","reason":"帮助数据平台团队理解 Snowflake 原生表与 Iceberg 的取舍，适合做湖仓开放格式选型与迁移决策。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake","Databricks","DuckDB","Trino","Amazon Athena"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":[],"decision_concerns":["可维护性与复用","成本与性能"]},"heat":24,"quality_score":52,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":52,"shelf":"evergreen","pinned":false,"published":"2026-10-02T22:01:08+08:00","first_seen":"2026-10-03T06:19:03.336456+08:00","original_url":"https://medium.com/snowflake/converting-snowflake-native-tables-to-iceberg-part-1-603fdb0fdcd1?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"b5d78eb75dbc","zh_title":"Anthropic用Claude托管代理重构入站销售","zh_summary":"Anthropic销售团队基于Claude Managed Agents（beta）搭建了一个采购代理，把潜在客户从“想为公司购买Claude”一路引导到完成购买。此前入站表单回复常需数天，每月数万条请求让BDR团队难以应付，客户问题多是价格、席位下限、HIPAA合同合规等文档里已有的内容。该代理每天进行数千次对话，回答问题并完成结账，升级给人工的线索转化为商机的概率是旧表单的两倍多，成交周期约快五天。整个体验为可选加入（opt-in），客户可自行选择对话代理还是销售代表。","reason":"提供了企业用Agent承接高并发入站咨询、提升转化并缩短成交周期的第一方真实数据，对构建面向业务的Agent和评估其生产落地价值有直接参考。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["销售增长","客户运营"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","场景与方案"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["用户采用与业务价值","可靠性与评估"]},"heat":31,"quality_score":68,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-10-01T01:03:50.428000+08:00","first_seen":"2026-10-02T20:39:13.154591+08:00","original_url":"https://claude.com/blog/how-anthropics-sales-team-rebuilt-inbound-with-claude-managed-agents","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"62e265af89f4","zh_title":"Databricks 实时推荐：Lakebase 与 AI Search","zh_summary":"Databricks 官方博客给出面向时尚电商的实时推荐参考架构，基于 Lakebase 与 AI Search，并运行在 Unity Catalog 治理下。案例平台月活超100万、SKU超10万，系统每秒摄入约1000个点击流事件。架构强调实时推理时绕过湖仓存储，将当前会话信号直接放入 API 请求并送到 Model Serving。文章称有效个性化可提升转化率10–30%，但需要实时摄取、特征工程和毫秒级服务。","reason":"该文展示了湖仓、实时摄取、模型服务与 AI 搜索如何组合成生产级推荐系统，对设计实时数据平台和 AI 应用的数据团队有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["湖仓","实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案"],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":37,"quality_score":80,"trend_score":1,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-10-02T19:00:00+08:00","first_seen":"2026-10-02T20:39:13.154591+08:00","original_url":"https://www.databricks.com/blog/real-time-retail-intelligence-building-e-commerce-recommendations-lakebase-and-ai-search","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"320f80a74cba","zh_title":"ClickHouse托管Postgres用直接I/O加速备份","zh_summary":"ClickHouse Managed Postgres 备份时需要从服务查询的 NVMe 盘读取全库并传到对象存储，默认缓冲 I/O 会污染 page cache，进而影响查询延迟。直接 I/O 跳过 page cache，测试中把备份期间查询延迟影响降低约三分之二，并减少约14% CPU，但会关闭内核预读。ClickHouse 按 RAID0 stripe 大小设置直接读取，并扩展 reader 数；在 48 vCPU、4 块 NVMe、467GB 数据库测试中，直接 I/O 备份未驱逐 40GiB 热数据，71 秒完成。","reason":"数据库备份与在线查询争抢 I/O 是生产环境常见痛点；该文给出 direct I/O、预读、RAID0 stripe 与 reader 数的可复现调优思路和量化收益，对数据平台与数据库从业者有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse","PostgreSQL"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":44,"quality_score":96,"trend_score":1,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":96,"shelf":"evergreen","pinned":false,"published":"2026-10-02T19:57:44+08:00","first_seen":"2026-10-02T20:39:13.154591+08:00","original_url":"https://clickhouse.com/blog/direct-io-managed-postgres-backups","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"ce25c73d71b2","zh_title":"Databricks：以代理式营销连接客户上下文与可衡量ROI","zh_summary":"Databricks官方博客指出，营销负责人面对更多客户数据、渠道和测量工具，但客户旅程更非线性、身份信号快速衰减，且各系统带来重复数据与定义。文章引用15,000+ martech工具和State of Martech 2026，认为营销价值正从曝光经济转向预测经济。其主张在正确的客户、业务和决策上下文下，由代理在护栏内推荐或执行下一步最佳行动，并通过反事实衡量增量效果，帮助判断营销预算是否应继续投入。","reason":"文章把客户数据、语义定义、Agent行动与增量ROI测量串成一条链路，对关注Data Agent落地以及营销/客户运营数据产品的从业者有参考价值。","category":"insight","category_label":"AI分析","vendors":["Databricks"],"topics":["销售增长","客户运营"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","指标与语义"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","用户采用与业务价值"]},"heat":21,"quality_score":45,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":45,"shelf":"evergreen","pinned":false,"published":"2026-10-01T20:11:31+08:00","first_seen":"2026-10-02T06:45:05.378455+08:00","original_url":"https://www.databricks.com/blog/connecting-customer-context-measurable-roi-agentic-marketing","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"17b3b16903c0","zh_title":"AI分析时代的语义层是什么？定义与实践","zh_summary":"文章讨论在AI分析时代语义层的角色，作者原本认为语义层是任何AI分析工作的前提，但近期测试后观点有所松动。语义层是机器可读的业务含义所在，统一定义收入、活跃用户、客户等，让工具、人员和AI模型得到一致数字。它包含指标、维度和业务逻辑，Metabase中的segments和glossary可将规则转为保存过滤并以自然语言解释。AI提高了跳过语义层的代价，也降低了构建语义层的成本。","reason":"语义层是AI分析与Text-to-SQL准确性的关键基础设施，文章解释其定义演变及AI时代的实践方式，值得数据从业者关注。","category":"platform","category_label":"AI 数据平台","vendors":["Metabase"],"topics":["语义层"],"product_ids":["metabase"],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","知识与上下文"],"use_cases":["指标问答"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":24,"quality_score":53,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":53,"shelf":"evergreen","pinned":false,"published":"2026-10-01T08:00:00+08:00","first_seen":"2026-10-02T06:45:05.378455+08:00","original_url":"https://www.metabase.com/blog/semantic-layer-ai-analytics","items":[{"source":"Metabase Blog"}],"source_badge":"RSS"},{"event_id":"f9f138495fde","zh_title":"Amazon MSK：用下一代协议优化消费者再均衡","zh_summary":"AWS 官方博客介绍如何在 Amazon MSK 上使用 Apache Kafka 4.0 引入的 KIP-848 消费者协议，优化大规模消费者组的再均衡。传统协议依赖客户端逻辑和全局同步屏障，单个消费者加入或离开都会让所有消费者暂停，可能引发“rebalance storms”并延长恢复时间。KIP-848 将协调逻辑从客户端转移到 Broker 端组协调器，实现完全增量、服务端驱动的再均衡，并可在 MSK Standard 和 Express Broker 的所有 4.x Kafka 版本上使用。文章还说明如何启用该协议，以及诊断和解决再均衡缓慢问题。","reason":"数据从业者若运行 Kafka/MSK 大规模消费组，可据此降低再均衡停顿与恢复时间，提升实时数据管道稳定性与运维效率。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon MSK"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":33,"quality_score":73,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":73,"shelf":"evergreen","pinned":false,"published":"2026-10-02T00:43:54+08:00","first_seen":"2026-10-02T06:45:05.378455+08:00","original_url":"https://aws.amazon.com/blogs/big-data/optimize-consumer-rebalancing-on-amazon-msk-with-next-generation-protocol/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"c167f613aaf5","zh_title":"Snowflake Code Bundles 实战指南（一）：Python","zh_summary":"本文是 Snowflake Code Bundles 系列第一篇，聚焦 Python 运行时。Code Bundle 是 schema 级对象，可把代码、依赖和配置打包成可移植单元，从 stage 或 workspace 创建并上传到 Snowflake 计算上执行。它支持在本地 IDE 开发测试，再把代码运行在数据所在位置，避免将数据移出 Snowflake。文章还概览了可观测性、版本管理、进阶模式以及将 Code Bundle 调度为 Job 等主题。","reason":"对使用 Snowflake 的数据工程师和分析师，这篇指南说明如何把本地 Python 工程化代码直接部署到 Snowflake 计算，涉及依赖、版本、可观测性和作业调度，有助于将探索性代码转为可复用自动化。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可维护性与复用","可靠性与评估"]},"heat":37,"quality_score":81,"trend_score":1,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":81,"shelf":"evergreen","pinned":false,"published":"2026-10-01T22:01:05+08:00","first_seen":"2026-10-02T06:45:05.378455+08:00","original_url":"https://medium.com/snowflake/a-practical-guide-to-snowflake-code-bundles-part-1-python-6278ed2caf26?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"14614cd42402","zh_title":"PayPal 将分析负载迁至 Google Managed Spark","zh_summary":"PayPal 分享了将分析工作负载从本地 Hadoop 平台迁移到 Google Cloud Managed Service for Apache Spark 的历程。原有分析环境因快速扩张和收购变得复杂，平台分散、运维开销高，扩展困难。其遗留平台每天处理 PB 级数据，但峰值零售事件或全球发布扩容需要数月规划。迁移后，Managed Spark 可在数分钟内配置集群并按处理需求弹性伸缩，减少等待和闲置资源。","reason":"这是数据平台现代化与 Spark 工作负载上云的实践案例，涉及从本地 Hadoop 迁移到托管 Spark 的挑战、选型理由和弹性伸缩收益，对数据基础设施从业者有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Google","Google Cloud"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":26,"quality_score":58,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":58,"shelf":"evergreen","pinned":false,"published":"2026-10-01T08:00:00+08:00","first_seen":"2026-10-02T06:45:05.378455+08:00","original_url":"https://cloud.google.com/blog/products/data-analytics/paypals-journey-with-managed-service-for-apache-spark","items":[{"source":"Google Cloud Data Analytics Blog"}],"source_badge":"RSS"},{"event_id":"fad0d9b82b18","zh_title":"用维度表加速 DuckDB 字符串聚合","zh_summary":"DuckDB 官方博客以荷兰铁路 train services 数据集为例，说明分析查询中重复字符串会带来大量哈希与比较开销：该表有 380,959 行，但 station_name 仅 537 个不同值，例如 Amsterdam Centraal 出现 7,591 次。文章建议采用数仓星型模式，把每个不同字符串映射为小整数，仅在最后再查回字符串，从而减少分组聚合时逐行处理完整字符串的成本。原文展示了可直接从 URL 查询 Parquet、建表并 GROUP BY station_name 的示例。","reason":"面向数据从业者，提供 DuckDB 查询优化与维度建模结合的具体实践，有助于降低分析工作负载的字符串聚合成本。","category":"platform","category_label":"AI 数据平台","vendors":["DuckDB"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":[],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":41,"quality_score":91,"trend_score":1,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":91,"shelf":"evergreen","pinned":false,"published":"2026-10-02T08:00:00+08:00","first_seen":"2026-10-02T06:45:05.378455+08:00","original_url":"https://duckdb.org/2026/10/02/dimension-tables.html","items":[{"source":"DuckDB Engineering Blog"}],"source_badge":"RSS"},{"event_id":"c02e6f3fe00c","zh_title":"为什么AI Agent的能力取决于它能触达的工具","zh_summary":"文章指出，推理能力让AI Agent做出决策，但真正让它能操作系统的关键在“触达”能力。工具需要类型化契约和清晰的输入输出，否则Agent会因猜测而破坏工作流。读取权限与执行操作权限风险不同，应作为独立权限处理。AgentSpot强调，赋予Agent行动能力应是有意且可见的选择，而不是默认设置；单纯升级模型无法弥补工具薄弱的问题。","reason":"对构建Data Agent/分析Agent的团队，工具契约与读写权限分离是落地关键，能避免工作流静默失败和安全风险。","category":"agent","category_label":"Data Agent","vendors":["ThoughtSpot","AgentSpot"],"topics":["Data Agent"],"product_ids":["thoughtspot"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","权限与治理"],"use_cases":["Agent构建"],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":18,"quality_score":39,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":39,"shelf":"evergreen","pinned":false,"published":"2026-10-01T09:11:46+08:00","first_seen":"2026-10-01T21:18:18.004298+08:00","original_url":"https://www.thoughtspot.com/blog/ai-agent-tool-access","items":[{"source":"ThoughtSpot Blog"}],"source_badge":"RSS"},{"event_id":"b5e0a3db863f","zh_title":"LinkedIn如何将ClickHouse从分布式追踪扩展到指标发现与分析","zh_summary":"LinkedIn 将其基于 ClickHouse 的可观测性栈从分布式追踪扩展到指标发现与分析，把 130 亿+ 指标整合到一个索引中，支持每分钟 15 万+ 查询。该公司两年前先在三个数据中心投产分布式追踪，每天处理约 8000 亿个 span。在 Open House SF 2026 上，LinkedIn 工程师分享了如何把旧指标元数据系统迁移到单一 ClickHouse 索引，从而降低运行成本并回答旧栈无法回答的问题。该实践展示了大规模实时指标索引与查询的架构方向。","reason":"数据从业者可了解超大规模可观测性场景下 ClickHouse 的指标索引、查询性能与成本优化实践，对实时分析平台和指标治理架构有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义"],"use_cases":["数据发现与搜索","生产评估与运营"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":36,"quality_score":78,"trend_score":1,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-10-01T19:47:10+08:00","first_seen":"2026-10-01T21:18:18.004298+08:00","original_url":"https://clickhouse.com/blog/linkedin-observability-at-scale","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"d927e58a6db6","zh_title":"2026指南：Unity Catalog托管表存储规则","zh_summary":"Databricks 官方博客介绍 Unity Catalog 托管表的存储模型：表数据仍存放在用户自有的云存储账户（如 S3、ADLS、GCS）中，而非厂商控制的存储或专有格式。无论使用 Iceberg 还是 Delta，Databricks 都会在用户选择的位置自动处理数据布局、调优和清理。Unity Catalog 通过开放 API 和凭证下发，让 Apache Spark、Flink、Trino、Kafka Connect、Snowflake 等外部工具以受治理方式读写托管表，避免复制数据。文章说明如何选择或更改 Databricks 托管存储位置。","reason":"对数据平台与湖仓从业者，理解 Unity Catalog 托管表的存储归属、开放格式互操作和治理访问机制，有助于评估数据主权、跨引擎架构与平台选型。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","Snowflake"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":[],"decision_concerns":["权限与安全","成本与性能"]},"heat":28,"quality_score":61,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":61,"shelf":"evergreen","pinned":false,"published":"2026-09-30T00:40:16+08:00","first_seen":"2026-10-01T13:57:37.331888+08:00","original_url":"https://www.databricks.com/blog/your-data-your-storage-your-rules-2026-guide-storing-unity-catalog-managed-tables","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"1e5e06d6ee03","zh_title":"明尼苏达劳动力萎缩：人口干旱与应对策略","zh_summary":"Lightcast 联合 Presbyterian Homes and Services、Minnesota Business Partnership 和 SullivanCotter 发布报告，分析明尼苏达州劳动力人口干旱的成因与缓解策略。受生育率下降、人口老龄化和退休增加影响，2023年6月该州就业仍比疫情前少11,500个，而全美已恢复。报告预测到2030年所有婴儿潮一代将年满65岁，明州劳动年龄人口占比将降至历史低点，带来人才短缺和经济增长放缓风险。缓解措施包括提升劳动参与率、扩大移民劳动池，以及投资新技术和商业模式。","reason":"该报告用劳动力市场数据回答企业普遍面临的人才短缺问题，给出人口趋势、量化缺口和应对方向，适合关注组织人才、用工风险与劳动力分析的从业者参考。","category":"insight","category_label":"AI分析","vendors":["Lightcast"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-15T21:05:42.994000+08:00","first_seen":"2026-10-01T13:57:37.331888+08:00","original_url":"https://lightcast.io/resources/research/minnesotas-vanishing-workforce","items":[{"source":"Lightcast Research"}],"source_badge":"官网"},{"event_id":"e8eee7d3d631","zh_title":"Lakebase Postgres 成本优化实践指南","zh_summary":"Lakebase 是 Databricks 提供的全托管 Postgres 数据库，采用存储计算分离、无服务器计算层，并与 Lakehouse 深度集成。本文解析其成本效率来源：数据库分支共享底层存储，避免为开发/测试环境复制物理数据；自动扩缩容按用量调整计算资源，并可设置最大规格控制成本。空闲时可缩容至零，计算成本降至零，并可在数百毫秒内从零恢复。文章还给出实际优化建议。","reason":"文章来自厂商官方博客，聚焦 Lakebase 的架构级成本优化：分支、自动扩缩容和缩容至零。对评估 Lakehouse 生态内 Postgres 工作负载成本与弹性的数据平台从业者有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","Lakebase"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["成本与性能"]},"heat":26,"quality_score":58,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":58,"shelf":"evergreen","pinned":false,"published":"2026-10-01T00:53:12+08:00","first_seen":"2026-10-01T06:18:23.926476+08:00","original_url":"https://www.databricks.com/blog/practical-guide-cost-optimization-lakebase-postgres","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"6de6a0da5d3d","zh_title":"如何规模化Agent应用而不产生AI蔓延","zh_summary":"构建单个Agent正变得更容易，但在企业内运营大量Agent是另一回事。随着Agent从回答问题转向执行动作，它们依赖模型、企业数据、业务语义、工具和应用，若各团队独立拼接，会导致集成重复、策略不一致、AI支出增加、上下文碎片化等问题。文章认为规模化需要基础设施提供选择、上下文和控制，让团队灵活使用模型/工具/框架，并基于受治理数据和业务语义工作，同时保持一致权限、策略、评估、可观测性和成本管理。Databricks将Agent Bricks、Omnigent和Unity Gateway组合为这一基础，支持构建治理优化Agent舰队、跨Agent harness协作，以及集中管理模型/Agent/工具的访问、成本和可观测性。","reason":"数据从业者应关注企业级Agent规模化中的治理、语义上下文、成本和可观测性挑战，以及Databricks对Agent平台层的产品布局。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可维护性与复用","成本与性能"]},"heat":17,"quality_score":38,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":38,"shelf":"evergreen","pinned":false,"published":"2026-10-01T00:46:25+08:00","first_seen":"2026-10-01T06:18:23.926476+08:00","original_url":"https://www.databricks.com/blog/how-scale-agentic-applications-without-creating-ai-sprawl","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"ec72634f6edf","zh_title":"ClickHouse 的 Postgres 扩展如何处理 C/C++ 内存安全","zh_summary":"ClickHouse 开发了 pg_clickhouse、pg_re2、pg_chdb、pg_stat_ch 等 Postgres 扩展，并将 C++ 引入原本用 C 编写的 Postgres，由此产生内存管理冲突。Postgres 采用 MemoryContext 与 palloc/pfree，并用基于 setjmp/longjmp 的 PG_TRY/PG_CATCH/PG_FINALLY 处理错误；C++ 则使用 new/delete 和异常，二者交互会跳过析构、触发未定义行为，未捕获异常还会导致进程 abort。各扩展采取不同策略：pg_clickhouse 完全移除 C++，用新的 C 库 clickhouse-c 替代 clickhouse-cpp，并包装为 pg-clickhouse-c 以整合 Postgres 逻辑、保持通用库复用。clickhouse-c 被设计为传输无关，支持 Native 协议之外的 Native 格式，使 HTTP 驱动复用大量编解码逻辑。","reason":"对数据库扩展、FDW 与数据集成组件的开发者有直接参考价值：它讲清 C/C++ 内存安全边界、错误处理和进程隔离的坑，可帮助避免崩溃与共享内存损坏。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入"],"decision_concerns":["可靠性与评估","可维护性与复用"]},"heat":40,"quality_score":89,"trend_score":1,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":89,"shelf":"evergreen","pinned":false,"published":"2026-09-30T21:56:27+08:00","first_seen":"2026-10-01T06:18:23.926476+08:00","original_url":"https://clickhouse.com/blog/memory-safety-postgres-extensions-c-cpp","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"e704c420a297","zh_title":"用 Snowflake Cortex AI 自动生成报表评论","zh_summary":"Snowflake 官方博客介绍如何用 Cortex AI functions 对结构化报表指标自动生成叙述性评论。以金融机构流动性风险管理为例，日报有 40+ 指标，需逐行撰写关于当前值、阈值突破、利用率和趋势的评论。文中示例 LCR 为 70.54%，突破 75.00% 的 Level 3 阈值 4.46 个百分点，且日/周/月趋势一致下行。该方案无需部署模型服务或集成外部 LLM API，并讨论架构决策因素。","reason":"数据从业者可了解在数仓内用 Cortex AI functions 把结构化指标转为可审阅的报表评述，评估 LLM 自动化报告的生产化架构与边界。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"ai-platform","label":"AI 数据平台","priority":1,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","报表与可视化"],"use_cases":["看板与报告"],"decision_concerns":[]},"heat":32,"quality_score":70,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-10-01T03:01:02+08:00","first_seen":"2026-10-01T06:18:23.926476+08:00","original_url":"https://medium.com/snowflake/automating-report-commentary-with-snowflake-cortex-ai-functions-from-metrics-to-narrative-b91f0ca553be?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"7600831240d2","zh_title":"Snowflake 经单一私有端点访问 Azure 存储账户","zh_summary":"文章讨论客户在 Azure 上运行 Snowflake、数据落在 Azure Blob Storage 的场景；因合规要求，存储账户不能暴露公网，传统把 Snowflake VNet 子网加入防火墙 allowlist 的做法会触发 XrpErrorTaggedTrafficConsumerCountLimitReached。可行方案是改用 Snowflake 出站私有连接，在存储集成上设置 USE_PRIVATELINK_ENDPOINT=TRUE，从而避免 service endpoint 与 tagged-consumer 配额限制。该能力要求 Business Critical 或更高版本，文章第一部分解释问题及为何简单修复会失效。","reason":"对使用 Snowflake + Azure Blob 外部阶段或 Iceberg 外部卷的数据平台团队，本文给出公私网接入配额限制的根因和官方私有连接方案，涉及合规、网络与版本门槛，工程参考价值高。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake","Azure"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["数据接入"],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":36,"quality_score":80,"trend_score":1,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-09-30T22:01:07+08:00","first_seen":"2026-10-01T06:18:23.926476+08:00","original_url":"https://medium.com/snowflake/access-azure-storage-accounts-over-single-private-endpoint-b12bd687b74b?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"98b74dfc9301","zh_title":"向量与全文检索解析：AI Agent 为何两者都需要","zh_summary":"文章解释向量检索与全文检索的差异：全文检索用倒排索引和 BM25 匹配字面词，向量检索比较嵌入语义，二者互补。混合检索并行运行并合并结果，可用 RRF 按排名融合，避免分数不可比。面向 AI Agent 的检索还依赖租户过滤、权限和新鲜事务数据；统一 SQL 与向量数据可减少索引同步任务。文中称 Dify.AI 迁移到 TiDB Cloud 后基础设施成本降低 80%。","reason":"帮助数据从业者理解 AI Agent 混合检索的召回机制、RRF 排序融合，以及权限、数据新鲜度和 SQL+向量统一架构的工程取舍。","category":"platform","category_label":"AI 数据平台","vendors":["PingCAP","TiDB","TiDB Cloud","Dify.AI"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["Agent构建","数据发现与搜索"],"decision_concerns":["准确性与语义一致性","权限与安全"]},"heat":29,"quality_score":64,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":64,"shelf":"evergreen","pinned":false,"published":"2026-09-30T08:03:48+08:00","first_seen":"2026-09-30T20:38:07.310177+08:00","original_url":"https://www.pingcap.com/blog/vector-and-full-text-search-for-ai-agents/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"a3fccdbe66ce","zh_title":"一个忘关的开关，与企业Agent的全栈技术账单","zh_summary":"文章从云栖大会企业级 Agent 论坛前的一通电话切入：某 AI 应用因开关未关，Token 费用从预估约 1 万元变成 3 万元，暴露任务启动、运行时长、费用归属和异常发现等治理问题。文中引用 IDC 预测 2029 年全球部署 AI 智能体超 10 亿个，约为 2025 年的 40 倍，以及 Gartner 预测 2027 年底超四成 Agentic AI 项目会因成本、价值或风险被取消。满帮集团 AI 算法总监高艺铭分享物流交易 Agent 在上下文、行业术语知识、执行规模上的挑战，如扩展到 2000 个 Agent 时系统故障；易方达 CIO 刘硕凌强调金融系统四个 9 可用性。文章认为企业级 Agent 需要算力、模型、数据、执行平台与治理机制全栈协同。","reason":"企业 Agent 落地不只是模型问题，更涉及数据上下文、权限治理、成本归属和可观测性，对数据平台与 Agent 工程协同有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":[],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":34,"quality_score":74,"trend_score":1,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"evergreen","pinned":false,"published":"2026-09-30T13:37:02.720529+08:00","first_seen":"2026-09-30T13:37:02.720529+08:00","original_url":"https://www.infoq.cn/article/z9VP6ZQ3vCxTrk1VdU5D?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"80b6ab9f4ca1","zh_title":"为 Amazon MWAA 构建 LLM 驱动的 DAG 故障分析插件","zh_summary":"Apache Airflow 已成为数据管道编排核心，但当管道扩展到数百个 DAG 并跨 AWS Glue、Amazon EMR、Amazon Athena、Amazon Redshift 等服务时，单个任务失败排查非常耗时。本文介绍如何构建自定义 Airflow 插件，集成 Amazon Bedrock（Anthropic Claude）自动分析 DAG 任务失败，并给出可操作的诊断洞察。插件部署在 Amazon MWAA 上，在 Airflow UI 中提供按需 AI 根因分析。完整源码已发布在 GitHub 示例仓库中。","reason":"数据从业者可了解如何用 LLM 增强数据管道可观测性与故障排查，降低 SLA 风险与数据工程运维负担。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon MWAA","Amazon Bedrock"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","用户采用与业务价值"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-09-30T00:17:09+08:00","first_seen":"2026-09-30T06:19:55.706919+08:00","original_url":"https://aws.amazon.com/blogs/big-data/building-an-llm-powered-dag-failure-analysis-plugin-for-amazon-mwaa/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"60bf8e4b7542","zh_title":"Snowflake交互式数仓上的一体化AI应用与可观测性","zh_summary":"作者在单个 Snowflake Interactive Warehouse 上同时构建零售运营 AI 应用和其可观测性管线。Cortex Agents 基于 Semantic View 生成 Text-to-SQL，查询约 2500 万行销售数据；AI Observability 自动将 trace、span、工具调用和 token 数写入 SNOWFLAKE.LOCAL.AI_OBSERVABILITY_EVENTS，无需 SDK 或 collector。监控看板与 Agent 共用同一仓库，最终发现了一个被 Agent 100% 成功率掩盖的语义视图缺陷。完整 SQL、代码和 Streamlit 应用已发布在 GitHub。","reason":"对想落地 Data Agent 并解决其可观测性、语义一致性与评估问题的数据团队有直接参考价值；也展示了 Snowflake 交互式数仓、Cortex Agents 与 AI Observability 的一体化实践。","category":"agent","category_label":"Data Agent","vendors":["Snowflake"],"topics":["Data Agent","语义层"],"product_ids":["snowflake-cortex"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","Agent接口与工具"],"use_cases":["指标问答","生产评估与运营"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":41,"quality_score":91,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":91,"shelf":"evergreen","pinned":false,"published":"2026-09-29T22:01:07+08:00","first_seen":"2026-09-30T06:19:55.706919+08:00","original_url":"https://medium.com/snowflake/running-an-ai-app-and-its-observability-on-one-snowflake-interactive-warehouse-21f36ad739fa?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"e4034125cc97","zh_title":"Databricks 如何让1.4万员工首日接入前沿模型","zh_summary":"Databricks 官方博客介绍其让上万名员工在新模型发布首日即可试用前沿模型的机制，核心依托 Unity Gateway 进行自适应发布、评估与成本控制。文中披露：被宣传为前沿的模型未必更好，如 Opus 5.0 成本更高且工程师质量评分低于 Opus 4.8。无成本约束地开放 GPT Astra 时，开发者平均支出增加 60%，因此采用按用户预算限制与用量引导。在 Opus 5、GPT-6 Sol 与 GPT-Luna 密集发布的当周，Databricks 全员首日接入，第 3 天即用数据确认其处于效率前沿并纳入基础设施。","reason":"这是一份难得的超大规模企业内部 AI 模型接入与治理第一手实践，涉及模型评估、成本控制与灰度发布，对正在建设模型网关与 AI 平台治理的数据团队有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":42,"quality_score":85,"trend_score":8,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-09-29T04:11:23+08:00","first_seen":"2026-09-29T07:20:47.713356+08:00","original_url":"https://www.databricks.com/blog/how-databricks-rolls-out-frontier-models-14000-employees-day-1","items":[{"source":"Databricks Blog"},{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"0de08774e321","zh_title":"制造业数据与AI：连接产品价值链","zh_summary":"文章指出制造缺陷往往跨越机器设置、供应商批次、物流事件和质量系统，相关数据被分割在工厂、职能和系统边界中。它回顾了50多年前Joseph Harrington提出的计算机集成制造(CIM)愿景，并认为现代数据与AI平台正让连接产品价值链变得可行。核心跨阶段问题包括：受影响产品涉及哪些供应商批次、缺陷是否曾出现及纠正措施是否有效、哪些客户或服务案例可能受影响。文章强调制造商需要的是带治理和业务上下文的跨系统信息流，而不是更多孤立报表。","reason":"制造数据跨系统集成与AI平台落地是典型行业场景，涉及数据接入、治理和业务上下文，能帮助数据从业者理解制造价值链的数据架构与决策问题。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化","供应链"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["数据接入"],"decision_concerns":["准确性与语义一致性","权限与安全"]},"heat":22,"quality_score":48,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":48,"shelf":"evergreen","pinned":false,"published":"2026-09-29T03:47:19+08:00","first_seen":"2026-09-29T07:20:47.713356+08:00","original_url":"https://www.databricks.com/blog/manufacturing-data-and-ai-connecting-product-value-chain","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"82b17f45b54e","zh_title":"Genie One 企业级推广分步 playbook","zh_summary":"区域销售总监想了解东北 pipeline 本季走弱的原因，却要等懂可信数据的分析师到周四，最终只能在缺少答案的情况下决策。Genie One 旨在让业务人员用自然语言提问，获得基于受治理数据并引用来源的回答，并快速启动后续多步工作。原文认为，AI 推广停滞常因一次性铺开过多数据域、不同团队对“活跃客户”定义不一、语义层无人负责且缺乏答案校验机制。其落地 playbook 建议从窄问题集开始，先赢得早期采用者信任，再依据反馈逐步扩展到更多业务线，并包含 Genie One、领域特定 Genie Agents、Genie Ontology 等组件。","reason":"对数据从业者而言，这是一份 Data Agent/ChatBI 在企业内推广的序列化方法：先解决语义一致、来源引用和答案校验，再通过早期采用者扩展到业务线，对减少 AI 分析工具落地失败有参考价值。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["Data Agent","语义层"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","知识与上下文"],"use_cases":["指标问答","自助分析"],"decision_concerns":["准确性与语义一致性","用户采用与业务价值"]},"heat":30,"quality_score":66,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":66,"shelf":"evergreen","pinned":false,"published":"2026-09-29T00:30:00+08:00","first_seen":"2026-09-29T07:20:47.713356+08:00","original_url":"https://www.databricks.com/blog/how-roll-out-genie-one-step-step-enterprise-playbook","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"b6c0f5d8a2e4","zh_title":"营销与数据工程最常误解的24个数据术语","zh_summary":"文章以“inactive customers”“real-time”等为例，说明营销团队与数据工程团队常对同一数据术语理解不同：前者可能指90天未购买，后者却按30天未打开应用定义；前者期待15分钟刷新，后者理解为秒级更新。文中围绕营销活动执行的五个问题，整理了24个常见误解术语，并给出营销与数据工程两方的对照定义。作者建议在项目开始前用这些定义澄清假设、对齐“客户”“受众就绪”“信号新鲜度”等含义，以避免活动返工。","reason":"帮助数据从业者理解营销侧对字段、事件、实时性等术语的真实预期，并给出可复用的对齐框架，减少数据交付与活动执行间的返工。","category":"product","category_label":"数据产品","vendors":["Databricks"],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义"],"use_cases":[],"decision_concerns":["准确性与语义一致性"]},"heat":27,"quality_score":59,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":59,"shelf":"evergreen","pinned":false,"published":"2026-09-28T15:01:10+08:00","first_seen":"2026-09-29T07:20:47.713356+08:00","original_url":"https://www.databricks.com/blog/helping-marketing-data-engineering-same-word-different-meaning","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"167559854496","zh_title":"你的 Postgres 能扛住坏查询吗？","zh_summary":"该文比较 ClickHouse Managed Postgres、Cloud SQL、PlanetScale 和 Amazon RDS 在递归查询耗尽内存时的表现，关注查询失败与集群存活。文章还解释 Postgres 的 work_mem 默认仅 4MB，且限制按查询计划中的操作而非整条查询生效，实际内存可远超该值。作者认为，在托管 Postgres 选择中，异常负载下的可靠性是一个常被忽略的维度，尤其当数据库由 Agent 自动配置和驱动时。","reason":"对数据库选型和平台可靠性评估有参考价值：它把“坏查询”下的故障隔离与集群存活作为托管 Postgres 的比较维度，并拆解 work_mem 等内存调优陷阱。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse","Cloud SQL","PlanetScale","Amazon RDS"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"evergreen","pinned":false,"published":"2026-09-28T23:37:06+08:00","first_seen":"2026-09-29T07:20:47.713356+08:00","original_url":"https://clickhouse.com/blog/can-your-postgres-survive-a-bad-query","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"d2e6d3dce3a0","zh_title":"Redshift Iceberg 写入支持 Part 3：模式与分区演进","zh_summary":"AWS 官方博客 Part 3 以客户和订单数据集为例，演示如何通过 ALTER 操作演进 Amazon Redshift 中的 Apache Iceberg 表模式与分区布局。操作包括重命名/新增/删除列、扩展列类型、设置表属性，以及新增/删除/替换分区字段，这些变更均为元数据操作，无需重写数据或重建管道。文章还介绍在 Amazon S3 Tables 目录中创建 AWS Lake Formation 资源链接，以单一权限模型向其他分析引擎共享表。该系列前两部分分别覆盖 Iceberg 表创建与写入，以及 DELETE/UPDATE/MERGE 行级修改。","reason":"Redshift 对 Iceberg 的写入与 ALTER 演进能力，关系到湖仓架构中多引擎共享、模式变更和权限治理的实现方式。数据平台从业者可借此了解如何避免重写数据和重建管道来维护 Iceberg 表。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon Redshift","AWS Lake Formation","Amazon S3 Tables"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据接入"],"decision_concerns":["权限与安全","成本与性能"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-09-28T23:48:35+08:00","first_seen":"2026-09-29T07:20:47.713356+08:00","original_url":"https://aws.amazon.com/blogs/big-data/getting-started-with-apache-iceberg-write-support-in-amazon-redshift-part-3/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"871c27bf0387","zh_title":"Snowflake AI 账单的三层成本控制：多数团队只建了一层","zh_summary":"文章讨论 Snowflake 上 AI 支出与仓库计算支出的差异，指出单靠预算无法治理 AI 成本，因为 agent 循环、应用默认调用大模型或开发者全天使用编码 agent 都可能快速消耗 credits。作者提出三层控制：资源预算、每用户配额和 Cortex AI Gateway，分别像烟雾探测器、限制单人和塑造路径，各有盲点。文中还标注截至 2026 年 9 月 21 日的状态：资源预算和共享资源预算 GA，每用户配额 GA 但 AI Gateway 域为 Preview，Cortex AI Gateway 自 2026 年 9 月 15 日起为 Preview。","reason":"Snowflake 用户和 AI 数据平台团队可借此理解 AI 成本治理为何不同于数仓成本，并获得预算、配额、网关三层落地的边界与组合思路。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":35,"quality_score":77,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":77,"shelf":"evergreen","pinned":false,"published":"2026-09-28T22:01:06+08:00","first_seen":"2026-09-29T07:20:47.713356+08:00","original_url":"https://medium.com/snowflake/your-ai-bill-has-three-control-layers-most-teams-only-build-one-c10e314ba97c?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"d769b4f2c54f","zh_title":"Forter：两周让200名团队成员成为Agent构建者","zh_summary":"Forter首席工程师Ben Maraney分享如何降低AI Agent创建门槛，让技术和非技术员工都能参与。团队利用自定义MCP服务器、结合无代码与代码平台，并有意避开复杂RAG方案。他们还协调安全与法务团队，以加速R&D内部的Agent采用。标题称两周内将200名团队成员转化为Agent创建者。","reason":"该实践展示了企业内部规模化构建Agent的落地路径，涉及MCP、无代码/代码平台、RAG取舍与安全法务协同，对数据团队建设Data Agent和提升内部采用率有参考价值。","category":"agent","category_label":"Data Agent","vendors":[],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","知识与上下文"],"use_cases":["Agent构建"],"decision_concerns":["权限与安全","用户采用与业务价值"]},"heat":26,"quality_score":58,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":58,"shelf":"evergreen","pinned":false,"published":"2026-09-28T19:00:00+08:00","first_seen":"2026-09-28T21:58:23.837516+08:00","original_url":"https://www.infoq.com/presentations/building-internal-ai-agents/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"7fd21eb8c5a2","zh_title":"数据揭示 Reddit 刀具推荐或存水军操纵","zh_summary":"Hacker News 热帖（26 赞）中，作者用数据调查 Reddit 刀具社区是否存在水军。作者微调 GLiNER 模型，从 r/knives、r/chefknives 等六个 subreddit 评论中抽取品牌、型号和钢材。初步发现某厨师刀品牌在“该买什么”类提及中有 31% 来自 5% 的账号，是随机预期的 4 倍。随后作者拉取这些账号历史，并预先定义 astroturfing 的数据模式以判断推荐是否被操纵。","reason":"该文把 Reddit 推荐社区的可信度问题转成可量化、可复核的数据分析，并用 NER 抽取品牌/型号/钢材，对做评论数据、推荐信号和风险识别的数据团队有方法参考。","category":"insight","category_label":"AI分析","vendors":[],"topics":["风险管理"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":40,"quality_score":78,"trend_score":9,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-09-28T21:30:54+08:00","first_seen":"2026-09-28T21:58:23.837516+08:00","original_url":"https://www.petervijeh.com/projects/reddit-astroturf","items":[{"source":"Hacker News（数据关键词）"}],"source_badge":"HN"},{"event_id":"fe759b807f34","zh_title":"Anthropic经济指数：Claude使用学习曲线","zh_summary":"Anthropic 发布经济指数报告，基于 2026 年 2 月 5 日至 12 日的 Claude 使用数据，延续此前经济基元框架。报告发现 Claude.ai 用例更多样化，前 10 任务占比从 2025 年 11 月的 24% 降至 2026 年 2 月的 19%；编码任务继续从 Claude.ai 增强式使用迁移到 API 自动化工作流。高使用时长用户更可能尝试高价值任务，并更可能获得成功回复；约 49% 职业至少四分之一任务已用 Claude。","reason":"报告用第一方使用数据揭示 Claude 采用学习曲线、任务迁移和成功率差异，对组织评估 AI 采用、技能培养及 Agent 产品运营有参考价值。","category":"product","category_label":"数据产品","vendors":["Anthropic","Claude"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["用户采用与业务价值","可靠性与评估"]},"heat":36,"quality_score":81,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":81,"shelf":"evergreen","pinned":false,"published":"2026-09-10T04:49:46+08:00","first_seen":"2026-09-28T01:02:52.304122+08:00","original_url":"https://www.anthropic.com/research/economic-index-march-2026-report","items":[{"source":"Anthropic Economic Index"}],"source_badge":"官网"},{"event_id":"62fa1dd33601","zh_title":"爱分析访谈飞数：AI接管数据生产，标注升级为数据服务","zh_summary":"爱分析访谈飞数执行总裁谭昶，讨论AI如何改造数据生产。飞数前身可追溯至科大讯飞2001年成立的语音制作部门，2024年4月孵化成立安徽飞数，定位人工智能高质量数据生产者。原文称语音、语言、文本等成熟场景中超过90%的数据可由模型自动处理，但医疗、教育等高标准场景最后1%仍需专家兜底。飞数业务覆盖规划、采集、治理、标注、质检和持续运营，并判断具身数据将从规模竞争转向知识密度竞争。","reason":"数据标注正升级为覆盖治理、质检与持续运营的数据生产服务，其中自动化与专家分工、高质量数据集评价标准对数据治理和数据平台团队有参考价值。","category":"product","category_label":"数据产品","vendors":["飞数","科大讯飞"],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["生产评估与运营"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":33,"quality_score":74,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"evergreen","pinned":false,"published":null,"first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.ifenxi.com/research/content/6960","items":[{"source":"爱分析"}],"source_badge":"RSS"},{"event_id":"4ce08dbfa3a3","zh_title":"爱分析访谈海致科技：Harness工程是AI可控的关键一环","zh_summary":"爱分析与海致科技联合创始人杨娟围绕Harness工程展开访谈，讨论其如何从Prompt、Context扩展到Skill管理与任务调度，成为支撑企业AI可解释、可追溯、高可信落地的系统工程。海致科技将图数据库、图模融合平台与Harness能力结合，用高性能图计算重构task、skill、审计等环节，并强调企业客户更关注结果稳定、过程可验证和责任可追溯。文章还讨论了图智能的新一轮爆发，以及从RAG走向可验证推理、企业Ontology从分析走向执行等方向。","reason":"文章对Data Agent与企业AI平台建设者理解可控性工程、图模融合和Ontology落地有参考价值，尤其适合关注AI进入核心业务后的可靠性与审计问题。","category":"platform","category_label":"AI 数据平台","vendors":["海致科技"],"topics":["Data Agent","平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","权限与安全"]},"heat":24,"quality_score":53,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":53,"shelf":"evergreen","pinned":false,"published":null,"first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.ifenxi.com/research/content/6957","items":[{"source":"爱分析"}],"source_badge":"RSS"},{"event_id":"4b8fffa27e50","zh_title":"Anthropic经济指数：AI使用新度量","zh_summary":"Anthropic发布经济指数报告，基于2025年11月Claude.ai及一方API的匿名对话，提出用户与AI技能、任务复杂度、自主性、成功率、用途五个维度。报告称Claude.ai可见超3000种工作任务，前10大任务占样本对话24%，增强型对话略超一半，而一方API以自动化使用为主。美国、印度、日本、英国、韩国在Claude.ai使用上领先，全球采用差异与人均GDP相关，美国各州采用差异与计算机和数学职业人员比例相关。数据覆盖消费者与企业使用及国家地区细分。","reason":"该报告用大规模真实对话样本量化AI在经济中的使用结构，为数据从业者理解AI采用差异、任务自动化与增强模式提供可核验的基准数据。","category":"product","category_label":"数据产品","vendors":["Anthropic","Claude"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["用户采用与业务价值","可靠性与评估"]},"heat":49,"quality_score":90,"trend_score":15,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":90,"shelf":"evergreen","pinned":false,"published":"2026-09-10T05:22:54+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.anthropic.com/research/anthropic-economic-index-january-2026-report","items":[{"source":"Anthropic Economic Index"},{"source":"Anthropic Economic Index"},{"source":"Anthropic Economic Index"}],"source_badge":"官网"},{"event_id":"d44ed50d0181","zh_title":"美国公共部门与私营部门AI岗位差异","zh_summary":"Lightcast与Christos Makridis、Gil Alterovitz教授联合发布白皮书，比较美国公共部门与私营部门AI相关岗位的需求、薪资和学历要求。研究使用Lightcast 2017-2023年职位发布数据库，并沿用其与斯坦福HAI合作定义的AI岗位口径。私营部门AI岗位占比从2017年的0.5%升至2023年约2%，公共部门则基本持平在0.25%。私营部门AI岗位平均发布薪资高约50%，技术类AI岗位要求学历的可能性是公共部门两倍；2017-2023年私营部门每发布1个公共部门AI岗位，约对应174个私营岗位。","reason":"该报告用多年职位发布数据量化AI人才在公共/私营部门的需求、薪资与学历差距，并为联邦层面的技术人才招聘提供参考，适合关注AI人才市场与组织能力建设的数据从业者。","category":"insight","category_label":"AI分析","vendors":["Lightcast"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":36,"quality_score":79,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":79,"shelf":"evergreen","pinned":false,"published":"2026-08-15T21:14:08.155000+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://lightcast.io/resources/research/ai-public-sector-private-sector","items":[{"source":"Lightcast Research"}],"source_badge":"官网"},{"event_id":"f79f63c63e0d","zh_title":"S&P Global 用 Databricks Genie+MCP 实现数据对话","zh_summary":"S&P Global Energy 希望让客户通过自然语言访问其跨商品的结构化数据，以更快做出决策。其数据覆盖化学品、原油、成品油、天然气与电力、LNG 等，分布在 Databricks 和多个非 Databricks 来源。团队评估多种方案后，采用 Databricks Genie Agents 作为受管 MCP 服务器，并通过 MCP 代理层组合成领域专用包。业务专家（SME）按数据集组维护聚焦的 Genie Agent，使客户和自有助手能获得可信、受治理的答案。","reason":"该案例展示了如何用 Genie Agents 与 MCP 将复杂结构化数据资产开放给 AI 智能体，涉及数据上下文、治理与 MCP 组合架构，对构建 ChatBI/Data Agent 的团队有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["Databricks","S&P Global"],"topics":["Data Agent"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","Agent接口与工具"],"use_cases":["指标问答","Agent构建"],"decision_concerns":["准确性与语义一致性","权限与安全"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-09-26T00:00:00+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.databricks.com/blog/data-dialogue-how-sp-global-energy-made-its-structured-data-estate-conversational-databricks","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"b96997bdba83","zh_title":"在 Databricks SQL 中运行开放决策模型","zh_summary":"Databricks 官方博客介绍如何在 Databricks 上托管开放权重决策模型，并以 SemIf-OpenJev 为例在 SQL 中运行。流程由可导入 Notebook 完成：选择模型名/schema、选择 Serverless GPU、Run All；AI Runtime 提供无服务器 GPU 计算，自动下载模型、登记并创建 GPU Model Serving 端点。用户可通过 SQL 的 ai_query 直接调用任意自定义模型 API，把模型应用于受治理数据，例如将酒店评论分类为好/坏。文中还提到可用 AI Runtime 定制或后训练模型，并通过 Lakeflow 的生产作业调用。","reason":"该实践展示 Databricks 把开放权重模型接入受治理数据与 SQL 工作流的路径，覆盖从模型部署到 ai_query 调用和生产作业，对建设数据平台 AI 能力、降低 GPU 运维与调用成本的团队有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理","场景与方案"],"use_cases":["生产评估与运营"],"decision_concerns":["权限与安全","成本与性能"]},"heat":36,"quality_score":81,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":81,"shelf":"evergreen","pinned":false,"published":"2026-09-25T00:55:01+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.databricks.com/blog/running-open-jev-sql-databricks","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"e7dff550bb3c","zh_title":"在Databricks上构建Agent化安全审查","zh_summary":"作者在已有安全审查自动化基础上，用Agent层扩展流程，目标不是替代人，而是让系统理解请求、应用安全标准、补全缺失信息并识别人工介入时机。首个版本只覆盖一条审查路径，随后团队将其扩展为支持更多安全受理与审查环节的多个Agent。实现全部构建在Databricks上：Unity Catalog提供受治理的标准、请求、证据、决策与系统输出空间，Databricks托管基础模型（Claude Haiku、Sonnet、Opus）负责分类、风险评估和起草要求，Lakeflow Jobs在Serverless Compute上编排Notebook工作流，Databricks Apps提供受理应用和高管看板。请求在统一受治理表中连续流转，从Intake到Reasoning逐步处理。","reason":"对数据从业者的价值在于展示如何在受治理的数据平台上落地生产级Agent：统一元数据/权限、模型编排、应用入口和人在回路如何组合，可迁移到安全、风控等专家审查场景。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化","风险管理"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["Agent构建"],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":30,"quality_score":67,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":67,"shelf":"evergreen","pinned":false,"published":"2026-09-24T10:00:00+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.databricks.com/blog/how-i-built-agent-based-security-reviews-databricks","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"f76140abac25","zh_title":"Concurrence 用 Unity Gateway 治理万亿级临床 AI","zh_summary":"Concurrence 在 Databricks 上运行临床 AI 代理，近 30 天处理约 1008 亿输入 token 和 1120 万次 LLM 调用，年化约 1.2 万亿输入 token。为满足合规与可靠性，它用 Lakebase 承载运营和对话状态，用 Unity Catalog 治理数据与 AI 资产，用 Unity Gateway 集中管理 AI 访问与安全。Concurrence 将新信息记录为不可变事件并计算当前患者状态，保留来源与溯源，形成其 world model，使代理获得一致的患者视图和历史。文章展示了高风险医疗场景下，代理测试、受治理数据与 AI 访问如何支撑规模化生产。","reason":"数据从业者可看到湖仓、目录与 AI 网关如何统一支撑规模化 Agent 的状态、治理与安全，并了解医疗临床场景的生产 token 指标。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化","湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理","Agent接口与工具"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-09-23T20:19:55+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.databricks.com/blog/how-concurrence-governs-clinical-ai-trillion-token-scale-unity-gateway","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"91c492ef27ba","zh_title":"用Databricks系统表查询理解成本的Top 5","zh_summary":"Databricks 官方博客介绍了用于理解 Databricks 成本的五个系统表查询。系统表可提供关于 Databricks 使用方式和费用构成的丰富信息。文章面向需要分析、监控或优化 Databricks 支出的数据团队。读者可据此通过系统表查询定位成本来源。","reason":"该文提供官方系统表查询实践，对需要监控和优化 Databricks 使用成本的数据平台团队有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-09-23T00:22:39+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.databricks.com/blog/top-5-system-table-queries-understanding-your-databricks-costs","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"951b7e33e52c","zh_title":"dbt：在数据仓库中开始上下文工程","zh_summary":"文章提出，分析团队过去为 BI 建模数据，而上下文工程是为 AI Agent 建模数据，起点是语义搜索。AI Agent 正成为最大数据用户，其所需上下文不再局限于结构化表，还包括转录、工单、PDF 和邮件。团队可复用 dbt 的工程模式：转换数据、关联富化、描述字段含义并治理访问权限；栈仍是 Fivetran 入仓、dbt 建模。仓库厂商正加大对非结构化数据的投入，文末还介绍了 dbt_context_engineering 包和一场相关 session。","reason":"数据从业者可借此理解从 BI 建模到为 Agent 准备上下文的范式变化，并看到 dbt/Fivetran/数仓栈在语义、治理和非结构化数据上的落地路径。","category":"platform","category_label":"AI 数据平台","vendors":["dbt Labs","Fivetran"],"topics":["Data Agent","语义层"],"product_ids":["dbt"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","指标与语义"],"use_cases":["数据发现与搜索","Agent构建"],"decision_concerns":["准确性与语义一致性","权限与安全"]},"heat":22,"quality_score":48,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":48,"shelf":"evergreen","pinned":false,"published":"2026-09-24T23:57:00+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.getdbt.com/blog/context-engineering-in-your-warehouse","items":[{"source":"dbt Blog"}],"source_badge":"RSS"},{"event_id":"f2cae75df487","zh_title":"AI智能体的上下文问题：语义层采购前先解决治理与定义","zh_summary":"文章指出，多数AI Agent能写SQL，但常基于错误的收入定义、错误团队和错误业务规则，演示中很难发现。语义层市场拥挤，各大分析厂商、数据平台和BI工具都宣称有语义层，但技术可信度取决于采购前的治理与定义决策。作者建议在评估语义层厂商前先确认治理机制，锁定核心指标、KPI和术语定义，并要求厂商在自身技术栈中压力测试核心能力。","reason":"对负责语义层、ChatBI/Data Agent选型的数据从业者，这篇文章指出AI分析失败常源于上下文与指标定义治理，而非模型能力，并给出采购前评估框架。","category":"platform","category_label":"AI 数据平台","vendors":["ThoughtSpot"],"topics":["语义层","Data Agent"],"product_ids":["thoughtspot"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","权限与治理"],"use_cases":["指标问答"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":21,"quality_score":46,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":46,"shelf":"evergreen","pinned":false,"published":"2026-09-24T01:09:35+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.thoughtspot.com/blog/evaluate-semantic-layer-for-ai","items":[{"source":"ThoughtSpot Blog"}],"source_badge":"RSS"},{"event_id":"4509822decea","zh_title":"从仪表盘到AI Agent：Huel的分析转型之路","zh_summary":"Huel 数据团队从已建成的现代数据栈和自助式仪表盘，转向 AI 驱动的 agentic analytics，并重新定义数据团队角色。ThoughtSpot 的 Jane Smith 与作者在伦敦 CDO Retail Exchange 上围绕 The Power of Trust + Context for Agentic Analytics 对谈。Huel 曾尝试在 Snowflake 中建模并通过 Claude 提供给员工，但发现通用 LLM 更像缺乏透明度的中间人，因此强调可解释性与商业化优先。文中还提到 Spotter 在 Huel 场景中的作用。","reason":"对数据从业者，这是一份消费品牌如何从自助 BI 迈向 AI/Agent 分析的一线经验，尤其适合关注通用 LLM 在信任、上下文与可解释性上的边界。","category":"agent","category_label":"Data Agent","vendors":["ThoughtSpot","Snowflake"],"topics":["Data Agent","BI变局"],"product_ids":["thoughtspot"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","报表与可视化"],"use_cases":["看板与报告","自助分析"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":18,"quality_score":40,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":40,"shelf":"evergreen","pinned":false,"published":"2026-09-22T06:13:02+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.thoughtspot.com/blog/huels-analytics-journey","items":[{"source":"ThoughtSpot Blog"}],"source_badge":"RSS"},{"event_id":"b94c6c9a09dd","zh_title":"13个员工留存策略：留住顶尖人才","zh_summary":"Visier 发布文章，提出 13 个员工留存策略，帮助企业在 AI 重塑技能需求、工作负荷加重和重组频繁的背景下留住核心人才。文章指出，员工流失会带来招聘、入职和培训成本上升，并导致技能与组织知识流失；Visier 研究显示，37% 的领导者已将流失带来的招聘和培训成本视为劳动力规划不佳的主要后果。企业可通过劳动力数据识别留存风险，并衡量留存措施是否有效。","reason":"虽然主题是人力资源，但来自 people analytics 厂商 Visier，涉及用劳动力数据识别留存风险，对关注组织人才分析的数据从业者有参考价值。","category":"insight","category_label":"AI分析","vendors":["Visier"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":16,"quality_score":35,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":35,"shelf":"evergreen","pinned":false,"published":"2026-09-25T08:00:00+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.visier.com/blog/employee-retention-strategies/","items":[{"source":"Visier Blog"}],"source_badge":"RSS"},{"event_id":"44fb880837be","zh_title":"Visier研究：48%员工夸大AI使用，表演式AI源于领导层不清","zh_summary":"Visier与第三方研究机构合作，对1000名美国全职员工进行调查，并访谈医疗、金融、HR、软件等领域员工。报告显示，48%员工至少有时夸大自己的AI使用或专业程度；54%认为过去两年角色或职业因AI显著变化；59%不相信或不确定雇主有清晰计划应对AI对岗位的影响。报告将这种“表演式AI”归因于领导层计划不清晰，并指出员工最希望获得培训和透明度，而非岗位保障。","reason":"用1000名员工调查和访谈数据解释职场AI采用中的表演式行为，给出组织人才与AI转型的量化发现，对数据/技术团队的AI落地与变革管理有参考价值。","category":"insight","category_label":"AI分析","vendors":["Visier"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["用户采用与业务价值"]},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-09-22T08:00:00+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.visier.com/blog/ai-in-the-workplace-new-research-on-performative-ai/","items":[{"source":"Visier Blog"}],"source_badge":"RSS"},{"event_id":"2f57edb18020","zh_title":"Fountain 在 ClickHouse Cloud 上重建数据平面支撑 Cue","zh_summary":"Fountain 为零售、物流、餐饮、医疗和酒店等前线时薪员工提供招聘与排班平台，已处理超 9100 万申请和 1400 万入职。过去其分析依赖三小时批处理，架构包含 13 个 Postgres、4 个 MongoDB，经第三方复制到 S3/Iceberg/Parquet，再进入 BigQuery 和 ClickHouse。为支撑 agentic AI 平台 Cue，Fountain 用 ClickPipes 和 ClickHouse Cloud on AWS 重建数据平面，将分析延迟从三小时降至两分钟以内，并实现亚秒级查询。新架构还使成本降低约 66%，在 Open House SF 2026 上由数据平台负责人和高级分析工程师分享。","reason":"对正在建设实时数据平面、评估 ClickHouse/湖仓迁移或为 AI Agent 提供低延迟数据的团队有直接参考，尤其关注延迟、成本和架构简化。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse","AWS","BigQuery","PostgreSQL","MongoDB"],"topics":["实时分析","平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["成本与性能","用户采用与业务价值"]},"heat":33,"quality_score":73,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":73,"shelf":"evergreen","pinned":false,"published":"2026-09-22T22:52:36+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://clickhouse.com/blog/fountain-agentic-ai-for-high-volume-hiring","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"478f1b088f17","zh_title":"Delivery Hero 用 Apache Flink 重建实时广告测量","zh_summary":"Delivery Hero 与 AWS 合作，将其广告测量管道从小时级批处理迁移到 Amazon Managed Service for Apache Flink 的实时流处理。该平台每秒处理数万条消息、每天数十亿广告事件，支撑 2025 年近 15 亿欧元的广告收入，覆盖约 65 个国家和超过 150 万餐厅及本地商户。新管道把基础设施成本降低一半以上，并达到旧系统无法实现的数据质量。旧系统按处理时间而非事件发生时间分桶，并通过同步 API 查询活动元数据，扩展后暴露出事件时间语义缺失和处理缓慢等结构性问题。","reason":"这是实时流处理在广告计费与测量场景中的一线工程实践，展示了事件时间语义、成本优化和数据质量之间的具体权衡，对构建实时数据平台有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Apache Flink"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义"],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-09-25T00:09:12+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://aws.amazon.com/blogs/big-data/how-delivery-hero-rebuilt-real-time-ad-measurement-with-apache-flink/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"dfd3a445a252","zh_title":"SageMaker Unified Studio 域级 VPC 网络配置指南","zh_summary":"企业运营团队在 Amazon SageMaker Unified Studio 中运行域级 VPC 网络时，通常要支持数据工程、分析和机器学习等多个项目。每个项目都需要私有连接内部数据库、Amazon S3 桶和 AWS 服务；若缺少域级 VPC 配置，项目所有者需逐个与网络团队协调，导致子网选择不一致、VPC 端点缺失和故障排查困难。文章介绍如何为使用 IAM 认证的 SageMaker Unified Studio 域配置域级 VPC，包括选择子网与安全组、实现多可用区韧性、让无 VPC 项目继承域 VPC，以及何时必须重建项目并从项目内验证网络连通性。","reason":"数据平台与 ML 平台在 AWS 上的网络隔离、私有连接和安全审计是落地关键；此文给出 SageMaker Unified Studio 域级 VPC 的配置、继承与迁移边界，适合平台与数据工程团队参考。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon SageMaker"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["数据接入"],"decision_concerns":["权限与安全","可维护性与复用"]},"heat":35,"quality_score":77,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":77,"shelf":"evergreen","pinned":false,"published":"2026-09-24T02:36:56+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://aws.amazon.com/blogs/big-data/configure-domain-level-vpc-networking-in-amazon-sagemaker-unified-studio/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"9013c2752aa4","zh_title":"在 Amazon SageMaker Catalog 中用生成式 AI 查询非结构化数据","zh_summary":"这是系列文章第二部分，介绍非结构化数据消费侧流程。数据消费者登录 SageMaker Unified Studio，利用 AI 生成元数据关键词在 Amazon SageMaker Catalog 中搜索并订阅 S3 数据资产，经生产者审批后使用两种方式查询：面向分析师和业务用户的无代码聊天 Agent 自然语言查询，以及面向应用工程师的 Amazon Bedrock 模型推理编程访问。生产侧此前使用 Amazon Textract 和 Amazon Bedrock 上的 Anthropic Claude 提取并丰富元数据，目标是让组织更易发现并利用 PDF、图像、邮件等非结构化数据中的业务知识。","reason":"数据从业者可了解如何把数据目录、元数据增强、订阅审批与生成式 AI 查询串成可落地的非结构化数据消费链路，覆盖从业务分析到应用集成的两种模式。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon SageMaker","Amazon Bedrock","Anthropic"],"topics":["平台AI化","Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","Agent接口与工具"],"use_cases":["数据发现与搜索","自助分析"],"decision_concerns":["权限与安全","用户采用与业务价值"]},"heat":30,"quality_score":66,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":66,"shelf":"evergreen","pinned":false,"published":"2026-09-24T02:22:00+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://aws.amazon.com/blogs/big-data/query-unstructured-data-in-amazon-sagemaker-catalog-using-generative-ai/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"58f44ab1fece","zh_title":"Amazon MSK 大型消费组扩展最佳实践","zh_summary":"Amazon MSK 上扩展大型 Kafka 消费组时，重平衡期间 GroupMetadata 记录会写入内部 __consumer_offsets topic，组过大时可能超过默认 1 MB 限制，触发 RecordTooLargeException 和重平衡重试循环。本文解释消费组元数据如何增长、如何估算大小，并给出提高 topic 级大小限制的分步操作。文章还补充拆分消费组、调整分区数量和优化命名等策略，并讨论容量规划、监控及 Apache Kafka 4.0 中 KIP-848 在协议层的改进。","reason":"该文面向 Kafka/MSK 数据基础设施的生产运维，提供消费组扩展的具体故障机理、参数配置、容量规划与监控方法，对维护流处理平台的团队有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon MSK","Apache Kafka"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":38,"quality_score":84,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":84,"shelf":"evergreen","pinned":false,"published":"2026-09-22T23:16:06+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://aws.amazon.com/blogs/big-data/best-practices-for-scaling-large-consumer-groups-on-amazon-msk/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"72a01216eb46","zh_title":"Moeve 用 Athena 标准化数据湖中的 dbt 运行","zh_summary":"Moeve 的 analytics 团队用 dbt 构建转换，但项目增多后运行逻辑分散在各团队管道中，计算引擎不统一、成本可见性差。公司因此构建了基于 Amazon Athena 的集中式无服务器 dbt 运行方案，并用 AWS Step Functions 和 Fargate 解耦编排。方案把运行参数存入 Amazon DynamoDB，将结果发布到 Amazon EventBridge，使运行层与编排层独立演进。新 dbt 项目的接入时间从数天缩短到约 15 分钟。","reason":"对需要规模化运行 dbt、统一数据湖转换和优化成本治理的数据平台团队有直接参考价值；文中给出了编排解耦、参数管理和事件驱动的具体架构。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","dbt Labs","Amazon Athena"],"topics":[],"product_ids":["dbt"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":32,"quality_score":71,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":71,"shelf":"evergreen","pinned":false,"published":"2026-09-22T23:13:31+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://aws.amazon.com/blogs/big-data/how-moeve-standardized-dbt-runs-across-data-lakes-with-amazon-athena/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"d2044403b905","zh_title":"Fivetran 与 Airbyte 对比：功能、定价与关键差异","zh_summary":"文章对比了 Fivetran 与 Airbyte 两款数据集成平台的功能与定价，帮助读者选择合适的数据集成方案。Airbyte 是 2020 年成立的开源 ELT 引擎，提供自托管 Core、云版 Cloud 以及混合部署的 Enterprise Flex 三种形态；Fivetran 是 2012 年成立的全托管数据移动平台。截至 2026 年 9 月，Fivetran 覆盖 700+ 数据源，Airbyte 为 600+ 数据源（云版约 550 个），两者均支持全量、列级与基于 CDC 的增量复制。","reason":"数据集成是数仓与湖仓建设的关键环节，本篇对两大主流 ELT 工具在连接器数量、部署形态与复制能力上的横向对比，可作为技术选型的参考依据。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran","Airbyte"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":25,"quality_score":56,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":56,"shelf":"evergreen","pinned":false,"published":"2026-09-25T23:55:22+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.fivetran.com/blog/fivetran-vs-airbyte-features-pricing-services-and-more","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"bfde167efa74","zh_title":"实验：dbt 项目对 AI Agent 究竟值多少","zh_summary":"Fivetran 作者用同 4 张零售演示表向两个 AI Agent 提同一个问题（总营收是多少），Haiku 直接对明细行求和，Opus 先看订单表剔除了已取消订单并注明，两者给出自信却不同的答案。作者因此对比了 5 种接入同一 dbt 项目的方式，发现要求 Haiku 先读 dbt 文档后，其 join 问题的错误答案从 4 个降到 0 个；Semantic Layer 是唯一让两个模型都做到 0 错、且每个可信答案成本最低的接口。结论是对话式分析中，受治理的数据访问方式可能与模型本身同样重要。","reason":"用可量化的对照实验说明 Semantic Layer 相比裸 SQL 在准确率与成本上的价值，为 Data Agent/ChatBI 选型提供了直接依据。","category":"agent","category_label":"Data Agent","vendors":["Fivetran","dbt Labs","MotherDuck"],"topics":["Data Agent","语义层"],"product_ids":["dbt"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","知识与上下文"],"use_cases":["指标问答"],"decision_concerns":["准确性与语义一致性","成本与性能"]},"heat":41,"quality_score":91,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":91,"shelf":"evergreen","pinned":false,"published":"2026-09-25T01:38:12+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.fivetran.com/blog/what-a-dbt-project-is-worth-to-an-agent","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"c2ec32b4904f","zh_title":"演讲：真实世界中的自适应推荐系统——推理、评估与系统设计","zh_summary":"Mallika Rao 在演讲中指出，自适应推荐系统的真正复杂度并不在模型架构，而在于系统本身。她讨论了实时反馈循环、检索新鲜度、多阶段编排与端到端延迟预算，说明这些机制如何让系统在生产环境中持续学习与演进。她认为推荐系统多年来积累的经验——反馈循环、评估、在线学习、不确定性下运营——正随着 AI 变得更具自适应性而具有更广泛的适用性。","reason":"推荐系统的工程经验（反馈循环、检索新鲜度、编排与延迟预算、评估）正被迁移到 Data Agent 与 AI 数据平台的生产落地中，对关注系统可靠性和成本性能的数据从业者有直接参考价值。","category":"insight","category_label":"AI分析","vendors":[],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":26,"quality_score":57,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":57,"shelf":"evergreen","pinned":false,"published":"2026-09-26T19:00:00+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.infoq.com/presentations/adaptive-recommendation-systems-architecture/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"fb7a958f0064","zh_title":"Perplexity 自研 Rust 键值库 CobbleDB 替换 DynamoDB，查询延迟降低 5 倍","zh_summary":"Perplexity 将核心搜索服务层从 Amazon DynamoDB 迁移至自研分布式键值存储 CobbleDB（用 Rust 编写）。该迁移解决了在大查询量下向大语言模型提供多 KB 文档批次所引发的延迟与成本瓶颈。通过将持久化文档存储与热层检索解耦，工程团队实现批量读取延迟降低五倍，整体存储费用至少降低 20%。","reason":"这是一次典型的自研数据基础设施替换云托管服务的实践，给出了延迟、成本、吞吐等具体数字与架构解耦思路，对评估键值存储选型与 LLM 检索场景的数据从业者有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Amazon DynamoDB","Perplexity"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","知识与上下文"],"use_cases":["数据接入"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-09-25T22:14:00+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.infoq.com/news/2026/09/cobbledb-perplexity/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"6f777771ef7a","zh_title":"Agent Harness 解析：概念与两种构建方式","zh_summary":"本文以金融助手 FinBot 为例，讲解 agent harness（智能体生产化所需的模型外围层）的开发与运维两层结构。文章对比 AWS AgentCore Harness（托管式 HaaS）与 Kubernetes 上 LangChain 配合 Agent Router（原 Envoy AI Gateway）的自管方案，比较二者在工具、记忆、模型访问、成本控制与可观测性上的处理差异，并讨论团队在控制权、成本与可移植性之间的取舍。指出真正的区别不在能力有无，而在于由谁运维、支付多少以及是否用控制换速度。","reason":"为 Data Agent 从 demo 走向生产提供了清晰的架构分层与托管/自管选型框架，对负责智能体落地的数据与平台工程团队有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["AWS","LangChain"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","知识与上下文"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":33,"quality_score":74,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"evergreen","pinned":false,"published":"2026-09-25T17:00:00+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.infoq.com/articles/agent-harness-build-one/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"e21d73e20f8f","zh_title":"从Kafka依赖到直连接入：Snowpipe Streaming Elastic Channels生产实践","zh_summary":"文章介绍用 Snowpipe Streaming Elastic Channels 替代 Kafka 等中间消息总线，直接将数据流式写入 Snowflake 的生产级架构。作者用一个三行 SDK 调用从 MacBook 直接将 1,010 行数据流入 Snowflake，并展示了持久化确认、实时分析和异常检测能力。实现覆盖 RBAC、密钥对认证、Python SDK 生产者、Dynamic Tables 实时转换、至少一次投递去重与监控，所有 SQL 均在真实 Snowflake 账户验证并附完整代码仓库。","reason":"为数据工程师提供了替代 Kafka 缓冲层的可落地流式接入方案，含认证、去重、实时转换与监控全链路细节，对湖仓与实时分析架构选型有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["实时分析","湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","知识与上下文"],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-09-25T22:01:02+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://medium.com/snowflake/from-kafka-dependency-to-direct-ingestion-a-production-architecture-with-snowpipe-streaming-a8db39369593?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"34bc72cca022","zh_title":"用备份为 Snowflake 数据加一层保护","zh_summary":"文章介绍 Snowflake Backups 在 Time Travel 之外提供的数据保护能力，可对表、模式和数据库等对象创建快照。备份支持手动或自动执行，并通过备份策略定义计划与保留期，所有 Snowflake 版本均可用，保留锁和法律保留等高级功能需 Business Critical 及以上版本。文中以每日备份 gold 模式并保留 30 天为例，演示了创建 BACKUP_ADMIN 自定义角色、专用仓库并授予最小权限的完整配置流程。","reason":"面向数据平台从业者，给出 Snowflake 备份的最小权限角色设计与策略配置实操，可作为数据保护与治理的落地参考。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":[],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":31,"quality_score":69,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":69,"shelf":"evergreen","pinned":false,"published":"2026-09-25T03:01:01+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://medium.com/snowflake/protecting-your-snowflake-data-with-backups-51aeac1b7a2d?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"e8e737d1c54c","zh_title":"从dbt Core v1迁移到Snowflake上的dbt v2实践指南","zh_summary":"dbt v2于2026年9月16日正式GA，将代号Fusion的引擎产品化。本文给出一套Snowflake存量dbt项目的迁移路径：先升级到dbt v1.12并处理废弃项与包兼容性，再运行dbt parse --use-v2-parser，随后切换到v2并编译测试。作者指出真正关键的不是引擎本身，而是迁移前的准备工作，并提醒切换后静态分析可能暴露v1未标记的仓库专属SQL，需区分解析器限制与实际的Snowflake运行时问题。","reason":"面向数据工程团队的一手迁移实践，给出可逐步执行的命令与验证顺序，并点出v1到v2架构变化与静态分析的边界，对正在做dbt升级的团队有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake","dbt Labs"],"topics":[],"product_ids":["dbt"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["可维护性与复用","可靠性与评估"]},"heat":31,"quality_score":69,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":69,"shelf":"evergreen","pinned":false,"published":"2026-09-24T22:01:05+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://medium.com/snowflake/from-dbt-core-v1-to-dbt-v2-on-snowflake-a-practical-migration-guide-4eb137573a1f?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"a2e6f6d71810","zh_title":"Snowflake托管Iceberg表的事件驱动Glue Catalog注册方案","zh_summary":"Snowflake在2025_01 BCR版本中为托管的Iceberg表引入新写入路径，会在基础路径后追加8位随机后缀以保证表删除重建时的唯一性，导致Glue crawler抓取到 customers_f0xgvx1a 这类杂乱表名，影响用户写SQL探索数据。Glue本身不提供关闭该后缀或重命名的设置，作者在无法采用新Catalog服务的前提下，改用事件驱动方式将近实时地把表直接注册进Glue Catalog，成本仅每天几美分。文章也提示，已采用Horizon Catalog或其他兼容REST API的Catalog的组织不必自建此方案。","reason":"面向受限于既有AWS技术栈、无法引入新Catalog服务的数据团队，给出绕开Glue crawler随机后缀问题的可落地工程做法。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","知识与上下文"],"use_cases":["数据接入","数据发现与搜索"],"decision_concerns":["可维护性与复用","成本与性能"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-09-24T03:01:01+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://medium.com/snowflake/event-driven-glue-catalog-registration-for-snowflake-managed-iceberg-tables-35f3556d3358?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"1b6c9f3bf4a5","zh_title":"从Cassandra到Snowflake：NoSQL数据集成蓝图","zh_summary":"本文介绍利用Snowpark Python将Apache Cassandra数据集成到Snowflake的实践方案：借助官方DataStax cassandra-driver直接在Python环境中读取Cassandra行数据，并通过Snowpark DataFrame API生成单一SQL执行计划。方案支持在Snowflake内用Tasks或Snowpark Container Services进行无服务器化调度，并通过显式StructType声明模式，绕过pandas/pyarrow以降低内存开销。该方法尤其适合需要保留完整变更历史（SCD Type 2）的高规模源系统，典型场景如属性频繁变动的产品目录。","reason":"对需要将高吞吐NoSQL源接入数仓的数据工程师有直接参考价值，讲清了驱动直连、模式声明与无服务器调度的具体机制与边界。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake","DataStax"],"topics":["湖仓","数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["成本与性能"]},"heat":36,"quality_score":79,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":79,"shelf":"evergreen","pinned":false,"published":"2026-09-22T23:01:06+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://medium.com/snowflake/modernizing-nosql-data-a-cassandra-to-snowflake-integration-blueprint-fbb60557d63c?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"113da8bd65f9","zh_title":"Snowflake PERIOD 数据类型：用原生时间范围查询生效记录","zh_summary":"Snowflake 发布 10.32 版本说明，覆盖 2026 年 9 月 5 日至 9 月 9 日。该版本包含行为变更捆绑包 2026_07（默认禁用，管理员可启用测试）、2026_06（默认启用，可退出）和 2026_05（普遍启用，管理员不能再开关）。SQL 方面，PERIOD 数据类型正式可用，用于存储锚定的半开时间范围 [begin, end)，并提供 PERIOD_* 函数族。数据治理方面，ALTER TABLE 或 ALTER VIEW … MODIFY DATA METRIC FUNCTION 新增 FILTER 子句，可设置、替换或清除数据指标函数的行过滤条件，空括号 FILTER () 表示清除过滤。","reason":"这是 Snowflake 官方版本说明，涉及新数据类型与数据指标函数治理能力，使用 Snowflake 的数据平台和数仓从业者需关注行为变更状态并评估兼容性。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据接入"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":40,"quality_score":80,"trend_score":7,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-09-22T22:01:07+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://medium.com/snowflake/query-time-ranges-with-snowflakes-period-data-type-ce229d2306bd?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"},{"source":"Snowflake Release Notes"}],"source_badge":"RSS"},{"event_id":"2f576701d80e","zh_title":"在托管计算上用工作负载证明换取自有身份","zh_summary":"Netflix 工程博客介绍如何在 Amazon EMR 等托管计算上为 Apache Spark 工作负载打通身份体系。组织通常并行运行两套身份系统：云厂商的 IAM 角色/实例配置/执行角色，以及内部服务实际校验的自有身份。文章讲述如何让一个仅有 AWS 身份的工作负载最终获得一等公民的内部身份，并强调交换过程本身简单，难的是让它可信。","reason":"涉及数据平台的身份认证与工作负载证明机制，对在托管云环境上运行数据作业、需要统一内部权限与审计的数据平台工程师有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":[],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":[],"decision_concerns":["权限与安全"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-09-26T00:01:03+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://netflixtechblog.com/trading-a-cloud-identity-for-your-own-workload-attestation-on-managed-compute-516d5a29b252?source=rss----2615bd06b42e---4","items":[{"source":"Netflix Technology Blog"}],"source_badge":"RSS"},{"event_id":"0715f0d3b7c0","zh_title":"Plaid 从 Aurora 迁移到分布式 SQL 的零停机实践","zh_summary":"Plaid 的 Amazon Aurora MySQL 集群面临大版本升级时，评估需要耗费六个工程月并伴随数十分钟停机。为支撑数千个金融应用的 API，Plaid 转而迁移至分布式 SQL，首次在 TiDB 上升级即覆盖六个生产集群、一周内完成且零停机。文章分析了金融科技在高并发、实时分析与一致性审计下面临的架构挑战，以及分布式 SQL 如何应对。","reason":"面向金融科技高并发与零停机诉求，给出分布式 SQL 迁移的真实生产案例与架构权衡，对数据库选型和升级策略有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["PingCAP","TiDB","Plaid","Amazon Aurora"],"topics":["实时分析","湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":[],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":30,"quality_score":67,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":67,"shelf":"evergreen","pinned":false,"published":"2026-09-26T16:31:01+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.pingcap.com/blog/fintech-scalability-crisis-how-distributed-sql-unlocks-innovation-zero-downtime/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"382fa24348cc","zh_title":"Lakebase与TiDB X：AI需求下的数据库架构","zh_summary":"文章对比Databricks的Lakebase（基于对象存储的无服务器Postgres）与TiDB X的架构设计，两者都将持久化数据放在对象存储中、与计算分离。作者指出AI Agent需要快速创建、低成本闲置、可安全试错的数据库生命周期，而不只是查询速度。Lakebase对单一Postgres主库做分支，TiDB X把分支能力带入分布式SQL；TiDB Cloud Lake则通过导出加载实现独立分析计算，而非零拷贝访问。","reason":"对关注AI Agent工作负载下数据库架构演进的数据从业者，文章拆解了计算存储分离、数据库分支等关键机制及其生产验证缺口。","category":"platform","category_label":"AI 数据平台","vendors":["PingCAP","TiDB","Databricks"],"topics":["湖仓","Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":33,"quality_score":74,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"evergreen","pinned":false,"published":"2026-09-23T23:35:42+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.pingcap.com/blog/separation-of-compute-and-storage-lakebase-tidb-x/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"30b83b28a4ab","zh_title":"AI Agent 状态解析：持久化记忆与任务进度","zh_summary":"文章解释 AI Agent 状态是记忆、任务进度与上下文的持久化记录，使 Agent 能在重启、重试和多步任务中存活。据 LangChain 2026 年报告，57% 的组织已有 Agent 在生产环境运行，较上年 51% 上升；输出质量以 32% 成为扩展最大障碍，超过成本与延迟。文章区分了上下文窗口与状态，并介绍了架构模式及 TiDB 作为数据层的定位。","reason":"对构建 Data Agent/分析 Agent 的从业者而言，状态持久化直接决定多步分析任务能否可靠恢复与审计，是落地生产的关键工程问题。","category":"agent","category_label":"Data Agent","vendors":["PingCAP","TiDB","LangChain"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":["Agent构建"],"decision_concerns":["可靠性与评估","准确性与语义一致性"]},"heat":30,"quality_score":67,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":67,"shelf":"evergreen","pinned":false,"published":"2026-09-22T05:35:41+08:00","first_seen":"2026-09-26T22:27:28.257662+08:00","original_url":"https://www.pingcap.com/blog/ai-agent-state/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"1f0497343807","zh_title":"欧洲技能转型指数：职业技能变化分析","zh_summary":"文章介绍“技能指数”（The Skills Index），衡量奥地利、比利时、法国、德国、爱尔兰、意大利、荷兰、西班牙、瑞士9个欧洲国家及英国职业的雇主技能要求变化。方法为分析2021至2022年间每个4位ISCO职业的技能占比变化，并按0-100指数化。图表列出前25个职业，多属专业人员组，尤其是软件开发、系统分析、Web与多媒体开发等数字岗位。文章由此引出哪些数字技能更受需求的问题，并指向后续需求技能板块。","reason":"数据从业者可借此了解如何用大规模职业与技能数据构建可比较指数，并观察数字技能需求变化；其方法对劳动力市场分析和人才数据应用有参考价值。","category":"insight","category_label":"AI分析","vendors":[],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-15T21:20:10.988000+08:00","first_seen":"2026-09-22T06:02:05.038652+08:00","original_url":"https://lightcast.io/resources/research/the-european-skills-transformation-index","items":[{"source":"Lightcast Research"}],"source_badge":"官网"},{"event_id":"188ddde3038b","zh_title":"Lightcast：连接课堂与职业的技能错配分析","zh_summary":"Lightcast发布关于技能错配的Lightpaper，提出技能对齐分数（SAS），用140万份个人资料和1080万条职位发布衡量专业与劳动力需求的匹配度。研究发现，专业与劳动力市场对齐度每提高20%，毕业生陷入不充分就业的可能性降低10%。近五分之一本科毕业生进入与专业无关的职业。文章建议教育机构更清晰地展示课程与就业机会的连接，帮助学生和院校弥合技能差距。","reason":"该研究展示了如何用大规模劳动力市场数据构建可量化的技能对齐指标，并给出对教育机构人才供给与就业结果有决策价值的发现，适合关注组织人才与数据驱动分析的数据从业者。","category":"insight","category_label":"AI分析","vendors":["Lightcast"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":40,"quality_score":89,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":89,"shelf":"evergreen","pinned":false,"published":"2026-08-15T21:15:37.427000+08:00","first_seen":"2026-09-22T06:02:05.038652+08:00","original_url":"https://lightcast.io/resources/research/skills-mismatch-educators","items":[{"source":"Lightcast Research"}],"source_badge":"官网"},{"event_id":"dd8cfe06050b","zh_title":"什么是AI分析？为何它只能在受治理数据上运行","zh_summary":"Databricks 产品营销负责人 Richard Tomlinson 在访谈中解释 AI analytics：系统可理解业务问题、确定相关数据与上下文、生成并执行查询，甚至进行多步调查。文章对比传统 BI，强调 AI 原生 BI 不只是给 BI 加聊天机器人，治理在真实企业环境中反而更重要。面对指标定义冲突、可能相关的多张表和权限限制，数据负责人应重点评估供应商的治理能力，而不是只问使用哪个基础模型。","reason":"帮助数据从业者理解 AI analytics/agentic analytics 与传统 BI 的差异，以及语义一致性、权限治理在 NL2SQL/Agent 场景中的关键作用。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["ChatBI","语义层"],"product_ids":[],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","权限与治理"],"use_cases":["指标问答","自助分析"],"decision_concerns":["准确性与语义一致性","权限与安全"]},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-09-16T00:45:03+08:00","first_seen":"2026-09-22T06:02:05.038652+08:00","original_url":"https://www.databricks.com/blog/what-ai-analytics-why-it-only-works-governed-data","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"d5de35c54292","zh_title":"蚂蚁Altum大模型训练数据处理系统设计与实践","zh_summary":"QCon上海将分享蚂蚁集团新一代大模型训练数据处理系统Altum，面向大模型训练数据规模增长下的GPU效能、任务稳定性和数据交付时效挑战。方案涵盖算力、引擎、平台与数据多层体系，包括异构算力融合调度、基于Paimon数据湖的端到端升级、算子优化与增量计算、样本级重试及Agentic数据处理。分享还介绍在阿福、百灵等内部场景的落地效果与AI Data Infra方向。","reason":"内容涉及大模型训练数据处理系统、异构算力调度、数据湖Paimon端到端优化及Agentic数据处理，对数据平台与AI Infra从业者理解训练数据工程体系有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["蚂蚁集团","Apache Paimon"],"topics":["平台AI化","湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","知识与上下文"],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-09-21T18:00:00+08:00","first_seen":"2026-09-22T06:02:05.038652+08:00","original_url":"https://www.infoq.cn/article/AGIRRRtM1lBDFIvwWuRX?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"741e2c14aac4","zh_title":"把未来做成基础设施｜亚马逊 CTO Werner Vogels 与云计算 20 年","zh_summary":"文章回顾亚马逊CTO Werner Vogels与云计算20年：2004年圣诞季，亚马逊单日订单超280万件、每秒32件，但一套Oracle数据库因极端规模bug宕机12小时。这次事故促使包括Werner在内的九名工程师发表Dynamo论文，影响Cassandra、Riak等NoSQL系统，并成为DynamoDB乃至AWS的技术前史之一。文中还提到S3、EC2、Lambda等服务，以及“You build it, you run it”的工程组织原则；Werner自2025年后不再登上re:Invent主舞台，并将于今年10月13日出席深圳亚马逊云科技软件企业峰会。","reason":"文章虽以云计算史和人物为主线，但Dynamo/NoSQL、数据库极端规模故障与工程组织原则对理解数据基础设施的可靠性和平台演进有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Oracle","Microsoft"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["可靠性与评估"]},"heat":31,"quality_score":69,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":69,"shelf":"evergreen","pinned":false,"published":"2026-09-21T19:00:08+08:00","first_seen":"2026-09-22T06:02:05.038652+08:00","original_url":"http://www.geekpark.net/news/370759","items":[{"source":"极客公园"}],"source_badge":"RSS"},{"event_id":"230eabee1072","zh_title":"用 Snowflake 与 WRITER 构建营销内容供应链飞轮","zh_summary":"Snowflake 与 WRITER 官方博客介绍如何把 Snowflake 中的客户分群、LTV、流失信号等数据与 WRITER 的企业 AI Agent 平台集成，形成营销内容供应链飞轮。该方案让营销人员通过自然语言调用 Snowflake 数据，在受治理的工作流中生成并发布合规的多渠道营销活动。每一次输出会回写 Snowflake，用于改进下一轮决策。文章还给出整体架构，并深入一个 AI 驱动营销内容供应链的具体示例。","reason":"数据从业者可关注数据平台与 AI Agent 在营销场景的闭环集成，尤其是自然语言取数、数据回写和治理合规如何串成工作流。对评估 Data Agent 落地边界有参考价值。","category":"agent","category_label":"Data Agent","vendors":["Snowflake","WRITER"],"topics":["Data Agent","客户运营"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["指标问答","方案封装与分发"],"decision_concerns":["权限与安全","用户采用与业务价值"]},"heat":28,"quality_score":63,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":63,"shelf":"evergreen","pinned":false,"published":"2026-09-22T01:01:02+08:00","first_seen":"2026-09-22T06:02:05.038652+08:00","original_url":"https://medium.com/snowflake/building-a-marketing-content-supply-chain-flywheel-with-writer-snowflake-cb13d76641ad?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"0db2ede356a0","zh_title":"FDE这么火，产品经理要不要跟？我来泼点冷水","zh_summary":"文章讨论FDE岗位热度：截至2025年底FDE岗位约922个、一年涨五倍，今年9月初美国462家公司招982个FDE、同比涨729%，猎头调研显示招聘意愿从年初5%-10%升至二季度末70%。作者认为FDE本质是平台落地最后一公里，国内存在同名不同岗，若平台不可复用大量招FDE可能只是换名实施。对产品经理，文章判断适合懂ToB/行业、有技术底子且愿驻场的人，不适合纯C端增长或只靠文档原型的人。签约前建议问清一线反馈能否进产品路线图、考核看产品化率还是交付工时、未来晋升路径。","reason":"文章把FDE放回AI/Agent落地最后一公里与产品化复用的框架，拆解国内岗位变形和实施化风险，并给出产品经理转型判断与签offer前的核查问题，对数据从业者职业选择和ToB产品边界有参考。","category":"insight","category_label":"AI分析","vendors":["Palantir","Anthropic","腾讯云","字节跳动","飞书"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["Agent构建"],"decision_concerns":["权限与安全","用户采用与业务价值"]},"heat":34,"quality_score":76,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":76,"shelf":"evergreen","pinned":false,"published":"2026-09-20T18:33:56+08:00","first_seen":"2026-09-21T00:08:36.274964+08:00","original_url":"https://www.woshipm.com/ai/6467287.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"76d282dae0bb","zh_title":"未来的 AI 产品应该怎么被“定义”","zh_summary":"文章以一家有百来款商品、经营两个线上渠道的服装品牌为例，推演 AI 如何围绕减少积压和退换货的问题，接入订单、库存和售后数据。AI 先按款式、尺码和渠道拆解问题，再自主构建应用，并在发现“尺码不合适”信息不足后增加试穿反馈和版型视图。文中提到 Shopify Sidekick 能按描述生成、修改后台应用但受运行范围和权限限制，并强调该案例仍是未来能力推演。","reason":"文章把 AI Agent/数据产品从功能清单转向围绕业务问题组织数据和动作，对做分析 Agent、数据产品与 AI 应用迭代有启发。","category":"product","category_label":"数据产品","vendors":["Shopify"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案","权限与治理"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","权限与安全"]},"heat":24,"quality_score":54,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":54,"shelf":"evergreen","pinned":false,"published":"2026-09-20T14:59:22+08:00","first_seen":"2026-09-21T00:08:36.274964+08:00","original_url":"https://www.woshipm.com/share/6467146.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"a1ebe51c3113","zh_title":"能源团队用Genie将盗电检测转为受治理行动","zh_summary":"Databricks 官方博客介绍能源行业如何将燃气/电力盗窃检测转化为受治理的行动闭环。文章指出英国能源消费者每年因盗窃损失超过 14 亿英镑，目标案件中仅 40% 被侦测。团队已有 ML 模型标记可疑账户，但真正挑战是打通检测、调查、损失回收和报告流程。方案在 Databricks App 中运行，并用 Lakebase 保存实时案件状态，通过 Genie 和 AI 业务流程把洞察推进为行动并反馈模型。","reason":"对数据从业者，该案例展示 ML 洞察如何借助 Lakebase、Databricks App、Genie 进入受治理运营闭环，对平台 AI 化和 Data Agent 落地有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化","风险管理"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案","权限与治理"],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","用户采用与业务价值"]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"evergreen","pinned":false,"published":"2026-09-16T00:50:00+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.databricks.com/blog/how-energy-teams-turn-theft-detection-governed-action-genie-and-ai-business-processes","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"ae192c8958aa","zh_title":"具身数据先于机器人出货，2026年或成AI数据服务最大增量","zh_summary":"爱分析访谈数据堂COO何鸿凌，他认为具身智能数据需求先于机器人出货形成规模，2026年或成为AI数据服务市场的主要增长点。按10万小时、100元/小时估算，单个模型公司的数据投入约1000万元，部分公司规划达100万甚至1000万小时。大模型后训练阶段，数据服务从大兵团转向特种兵团，更依赖高素质人才并随模型反馈动态调整。具身数据呈金字塔：遥操作价值高成本高，第一视角更易规模化；仿真是必要训练手段但外部商业化未成共识。","reason":"对关注AI数据平台、数据服务与训练数据供给的数据从业者，本文给出具身智能数据需求的规模、成本结构和组织模式变化，并提示数据服务商跨周期能力建设。","category":"product","category_label":"数据产品","vendors":["数据堂"],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","场景与方案"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":33,"quality_score":73,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":73,"shelf":"evergreen","pinned":false,"published":null,"first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.ifenxi.com/research/content/6945","items":[{"source":"爱分析"}],"source_badge":"RSS"},{"event_id":"841b5b975437","zh_title":"每日互动方毅：让AI用好私有数据的中国式路径","zh_summary":"爱分析与每日互动CEO方毅探讨企业AI落地，指出个人AI普及但企业核心业务落地仍慢，关键在于让AI接入私有数据、业务系统和决策流程。每日互动以个知·智能工作站为入口，构建办公、科研、知识管理及仝系列产品，并采用数据本地化、模型分层使用策略。公司通过CCE与DVD协同推进共创开发、系统连接和场景挖掘，形成标品、标类、标杆三种业务模式；方毅称已形成约100名CCE，可同时服务约50家企业，并要求企业负责人带队、5至10名骨干参与共创。每日互动将自身定位为模型和算力之上的中间层Dataware，类比Windows+Office，从DI走向AI，兼顾生产力释放与私有数据安全。","reason":"企业私有数据与AI结合是数据平台和Data Agent的重要落地方向，文章给出了产品架构、交付机制和业务模式，对数据从业者理解中国式企业AI落地路径有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["每日互动"],"topics":["平台AI化","组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["Agent构建","方案封装与分发"],"decision_concerns":["权限与安全","用户采用与业务价值"]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"evergreen","pinned":false,"published":null,"first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.ifenxi.com/research/content/6941","items":[{"source":"爱分析"}],"source_badge":"RSS"},{"event_id":"ffc9d0d8b95f","zh_title":"研究：AI高暴露岗位广告薪资涨得更快，溢价随资历递增","zh_summary":"Indeed Hiring Lab 分析数百万条带薪资的美国招聘信息，按生成式AI可改造的岗位技能占比计算“AI暴露度”。结果显示，AI高暴露岗位（软件开发、IT系统与支持、数据与分析、市场、银行与金融）的广告薪资自2021年以来上涨约46%，低暴露岗位仅涨25%，两者在ChatGPT发布后第一年走势接近，但从2024年起差距明显扩大。薪资溢价随资历上升：高级岗位最大、中级中等、初级几乎可忽略。","reason":"用海量招聘数据量化AI对薪酬结构的实际影响，直接关系到数据与分析从业者的岗位价值判断与职业路径选择，而非泛泛的AI焦虑叙事。","category":"insight","category_label":"AI分析","vendors":["Indeed"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-09-17T23:36:26+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://hiringlab.indeed.com/2026/09/17/ai-exposure-isnt-squeezing-advertised-pay-in-the-us-its-boosting-it/","items":[{"source":"Indeed Hiring Lab"}],"source_badge":"RSS"},{"event_id":"177c2ac1fe39","zh_title":"用技能数据强化区域经济","zh_summary":"该报告延续《The New Geography of Skills》研究，提出用技能通用语言连接教育机构、企业与劳动力/经济发展部门，以满足特定区域或行业的人才需求。报告结合广泛劳动力市场数据与更细粒度的技能集群数据，分析明尼苏达州医疗器械制造业的人才缺口，并与加州同产业进行比较。基于高度细化的数据，报告提出四步应用建议：了解自身优势并寻求多元化、识别技能提升的竞争机会、强化本地人才管道、开发紧缺微证书。文末引用哈佛肯尼迪学院Stephen Goldsmith的观点，强调该方法能提升区域技能战略效果。","reason":"该报告展示如何用劳动力市场与技能集群数据识别区域产业人才缺口，并给出四步人才战略，对关注数据驱动组织人才决策的从业者有参考价值。","category":"insight","category_label":"AI分析","vendors":[],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":[],"decision_concerns":["准确性与语义一致性","用户采用与业务价值"]},"heat":30,"quality_score":67,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":67,"shelf":"evergreen","pinned":false,"published":"2026-08-25T09:45:00.851000+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://lightcast.io/resources/research/using-skills-to-strengthen-regions","items":[{"source":"Lightcast Research"}],"source_badge":"官网"},{"event_id":"c83867043e41","zh_title":"消费银行如何解决技术人才短缺：劳动力市场洞察","zh_summary":"该报告与 Josh Bersin 合作，分析美国消费银行业的技术人才挑战。美国消费银行业拥有超过 1,367,000 名从业者，平均年薪 127,618 美元，但近 324,000 名员工年龄超过 55 岁，面临退休潮。2023 年全行业发布了 2,746,417 个下一代技术岗位，来自 87,994 家雇主，而消费银行仅占技术人才岗位的 13%。报告旨在为银行制定招聘与留才策略提供劳动力市场洞察。","reason":"用劳动力市场数据量化消费银行技术人才缺口与退休风险，为组织人才策略提供决策依据。","category":"insight","category_label":"AI分析","vendors":[],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":33,"quality_score":74,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"evergreen","pinned":false,"published":"2026-08-15T21:20:29.790000+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://lightcast.io/resources/research/consumer-banking-tech-talent-report","items":[{"source":"Lightcast Research"}],"source_badge":"官网"},{"event_id":"042bbfa5ed32","zh_title":"Databricks RADAR：用异常检测捕获灰色故障","zh_summary":"Databricks 介绍其系统 RADAR，利用异常检测捕获“灰色故障”。这类故障表面健康检查正常，但部分客户静默失败，导致用户和收入流失。文章以一次 checkout 流程 bug 为例，从 9:30 到 16:00 近七小时才修复，期间每 20 个信用卡支付客户有 1 个失败。内容面向 SRE、平台与数据工程师、on-call 人员，说明如何为关键指标构建异常检测。","reason":"Databricks 第一方可靠性工程实践，展示如何用异常检测发现监控盲区，对数据平台和 SRE 团队构建生产监控有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义"],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-09-19T08:00:00+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.databricks.com/blog/radar-catch-gray-failures-anomaly-detection","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"4f77f168f10e","zh_title":"Databricks 分享个人设备移动安全实践","zh_summary":"Databricks IT 介绍其在个人设备上安全开展工作的内部方法，目标是在不侵犯隐私的前提下保护公司数据。文章提出设备管理、身份认证、零信任和应用管理四层方案，并采用 iOS 的账户驱动用户注册（ADUE）仅管理工作相关组件，避免完全管理个人手机。随着 AI Agent 及 Genie、Omnigent、Claude Code 等工具改变工作方式，员工希望在手机上延续桌面会话并保持上下文，移动 BYOD 安全因此更复杂。Databricks 强调不主张查看或完全擦除个人设备，以提升员工对移动安全控制的采纳信任。","reason":"Databricks 官方披露其移动 BYOD 安全框架，涉及 AI Agent 工具在个人设备上的使用边界与零信任/应用管理，对关注数据平台安全治理与 Agent 落地的从业者有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化"],"product_ids":["databricks-genie"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":[],"decision_concerns":["权限与安全","用户采用与业务价值"]},"heat":30,"quality_score":67,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":67,"shelf":"evergreen","pinned":false,"published":"2026-09-19T01:45:00+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.databricks.com/blog/enabling-secure-productive-work-personal-devices","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"686054379e87","zh_title":"为 AI Agent 选择数据库的 5 项评估标准","zh_summary":"该文提出评估 AI Agent 数据库的五项标准：每个 Agent 独立分支、计算缩容至零、混合搜索、ACID 保证和统一平台。文章以 Lakebase 与 Databricks 湖仓为例，称分支可在约一秒内完成且直到产生分歧前无存储成本，计算可在数百毫秒内恢复且暂停时不计费。混合搜索可在单查询、100ms 内完成向量、关键词与结构化过滤，并发写入不丢失。若候选数据库无法满足多项最低标准，大规模运行 Agent 时可能构成生产风险。","reason":"文章给出可操作的数据库选型清单，帮助数据团队在构建 AI Agent 时评估分支隔离、弹性、混合检索、事务与湖仓一体化能力，避免只看功能列表而忽视生产风险。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化","湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":32,"quality_score":71,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":71,"shelf":"evergreen","pinned":false,"published":"2026-09-18T01:27:40+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.databricks.com/blog/database-for-ai-agents","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"a0e0653ed731","zh_title":"Agent内置网页搜索不够好：跨工具重复构建","zh_summary":"文章描述一名软件公司工程师构建 Agent，用于监控几十万个潜在客户和客户账户的外部信号（如融资、领导层变动、产品发布或招聘激增），并结合 Databricks 中受 Unity Catalog 治理的 Delta 表及公司自身使用与管道数据，帮助销售判断本周该联系哪些账户。第一版并非单一系统：同一套账户丰富逻辑在 Claude Code、Codex 和直接调用 API 三种方式中分别重建，分别适配各自的工具声明、MCP 连接和内置网页搜索。不同工具内置的网页搜索并不等价，返回的数据不同，某些来源在一个工具中可达、在另一个中却会漏掉。工程师大量时间花在学习各工具的配置差异，而不是改进账户丰富逻辑。","reason":"对构建数据/分析 Agent 的团队有参考价值：它揭示 Agent 网页搜索与工具链碎片化会直接影响结果一致性和维护成本，并涉及 Databricks/Unity Catalog 等数据平台集成。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","数据资产"],"use_cases":["Agent构建","数据接入"],"decision_concerns":["可靠性与评估","可维护性与复用"]},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-09-18T01:00:00+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.databricks.com/blog/web-search-your-agent-inherited-isnt-good-enough","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"d9c324ff0826","zh_title":"什么是 AIOps？AI 驱动的 IT 运维解析","zh_summary":"AIOps 将 AI 和机器学习应用于 IT 运维，用于检测异常、关联事件、定位根因并加快响应。文章称 Gartner 于 2017 年提出该词，并解释在 2026 年微服务、多云、AI 负载和 agent 驱动系统带来海量运维信号后，为何重新受到关注。AIOps 位于可观测性与行动之间，补充而非替代可观测性和 DevOps，同时保留人工监督。文章还概括了选型前应评估平台的能力边界。","reason":"AIOps 与数据/可观测性平台相邻，涉及用 AI 处理海量运维数据、异常检测和根因分析，对运营数据平台或 AI 负载的团队有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":12,"quality_score":27,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":27,"shelf":"evergreen","pinned":false,"published":"2026-09-18T00:49:43+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.databricks.com/blog/what-is-aiops","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"dd5a53569de5","zh_title":"用受治理数据与AI现代化交易生命周期","zh_summary":"资本市场机构正因数据量增长、实时洞察要求、AI项目走向生产以及结算周期缩短而重新审视交易生命周期。Databricks资本市场GTM负责人Andrea DeSosa在访谈中指出，研究、交易、风控、运营与合规常依赖彼此割裂的系统和不一致的数据视图，拖慢决策并影响风险可见性。她认为可持续优势不在于孤立模型，而在于让订单、成交、持仓、研究、风险和客户等专有数据在生命周期中更可发现、可靠且受治理。该访谈还提及预交易、执行、后交易与监控工作流，并关联一本相关电子书。","reason":"文章展示了资本市场在AI生产化过程中如何把数据治理、可发现性和一致性作为交易生命周期现代化的前提，可作为金融数据平台与治理方案的行业参考。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化","风险管理"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据发现与搜索","生产评估与运营"],"decision_concerns":["准确性与语义一致性","权限与安全"]},"heat":17,"quality_score":38,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":38,"shelf":"evergreen","pinned":false,"published":"2026-09-17T22:00:00+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.databricks.com/blog/modernizing-trade-lifecycle-governed-data-and-ai","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"40c2caf96019","zh_title":"AI分析引擎难题评测：Spotter领跑BIRD","zh_summary":"该文将 Spotter 与四款竞争性 agentic analytics 引擎放在 BIRD 基准上对比：1,533 道题、11 个数据库、统一评分、每题一次机会。Spotter 总体执行准确率 82.8%，高于前沿 LLM 的 78.4% 和编码 agent 的 72.5%；在挑战级题目中为 70.6%，最低引擎仅 46.8%。作者强调应看准确率斜率而非单一总体准确率，且仅更换更新模型、底层 agent harness 不变，就带来整体 3.4 个百分点提升。文中还引用 BARC 调查估算：万人员工企业约 65 万次数据问题/年，1 个准确率点对应 6,500 个答案对错。","reason":"提供可核验的 AI 分析引擎横向评测与难度分层结果，有助于数据团队用准确率斜率评估 Text-to-SQL/Data Agent 选型，而不是只看厂商宣传的单一准确率。","category":"agent","category_label":"Data Agent","vendors":["ThoughtSpot","Spotter"],"topics":["Data Agent","ChatBI"],"product_ids":["thoughtspot"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["指标问答","生产评估与运营"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":40,"quality_score":88,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":88,"shelf":"evergreen","pinned":false,"published":"2026-09-16T08:18:54+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.thoughtspot.com/blog/ai-analyst-accuracy-bird-benchmark","items":[{"source":"ThoughtSpot Blog"}],"source_badge":"RSS"},{"event_id":"7438410f9370","zh_title":"AI就绪劳动力数据：定义、信任与归属不可妥协","zh_summary":"文章指出，AI会让数据问题更显著且修复成本更高；AbbVie、Corning、UW Health、T. Rowe Price、ABM Industries等机构的数据从业者围绕定义、信任、合规和归属展开讨论。文中举例称，HR、IT、财务对同一入职事件可能记录不同日期，导致报表数字不一致。Corning为每个指标写正式规范，AbbVie将数据分为金、银、铜三级，ABM Industries要求每项HR指标具备明确负责人、标准定义、定期质量检查和透明计算。EU AI Act等法规使隐私与法务进入原本HR与财务的数据讨论。","reason":"数据从业者可从中看到AI-ready数据治理的关键障碍：指标定义不一致、信任机制缺失与责任归属不清；文中跨企业实践对建设可信数据平台有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Visier"],"topics":["语义层"],"product_ids":[],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","权限与治理"],"use_cases":[],"decision_concerns":["准确性与语义一致性","权限与安全"]},"heat":25,"quality_score":55,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":55,"shelf":"evergreen","pinned":false,"published":"2026-09-15T08:00:00+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.visier.com/blog/non-negotiables-ai-ready-workforce-data/","items":[{"source":"Visier Blog"}],"source_badge":"RSS"},{"event_id":"4c809899a4af","zh_title":"SageMaker Unified Studio治理Snowflake数据","zh_summary":"AWS 官方博客介绍如何通过 Amazon SageMaker Unified Studio 将 Snowflake 数据联邦接入 AWS Glue，并在 SageMaker Catalog 中注册、查询和治理。用户无需迁移或复制数据，即可用 AWS Glue Visual ETL 配置数据质量规则并发布带质量评分的资产。传统编目 Snowflake 数据需要构建抽取管道、耗时数天，该集成可将查询、编目和质量校验缩短到 5–15 分钟。该方案适合混合云数据环境，旨在减少治理缺口、发现摩擦和重复工作。","reason":"面向混合云数据治理和数据发现，展示了跨 Snowflake/AWS 的联邦编目与质量校验落地方式；对需要打通多云资产、减少复制和自定义 ETL 的数据平台团队有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Snowflake","Amazon SageMaker","AWS Glue"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据接入","数据发现与搜索"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-09-16T23:19:51+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://aws.amazon.com/blogs/big-data/discover-and-govern-snowflake-data-using-sagemaker-unified-studio/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"3b18acac037a","zh_title":"LinkedIn 基于MCP构建组织级上下文层赋能AI Agent","zh_summary":"LinkedIn 软件工程师 Ajay Prakash 分享了该公司如何通过上下文工程解决 AI 编码 Agent 在大代码库中的能力局限。其构建的 Contextual Agent Playbooks and Tools 基于 Model Context Protocol（MCP），向编码 Agent 直接提供流程性记忆、代码搜索和运行手册。演讲以线上延迟故障排查为例，展示 Agent 能自动获取日志、指标、变更与部署记录，定位到有缺陷的下游 PR 并生成缓解方案与事故报告。","reason":"该实践展示了如何用 MCP 与上下文层为 AI Agent 注入组织知识与流程性记忆，对构建企业级数据/分析 Agent 的上下文工程与工具接口设计有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["LinkedIn","GitHub Copilot"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["准确性与语义一致性"]},"heat":34,"quality_score":76,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":76,"shelf":"evergreen","pinned":false,"published":"2026-09-19T19:00:00+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.infoq.com/presentations/linkedin-context-engineering/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"979fa6b46cc5","zh_title":"DoorDash用多智能体LLM清理6万特性开关","zh_summary":"DoorDash构建多智能体LLM系统，自动清理其代码库中超过6万个特性开关、覆盖约623个仓库。系统结合MCP实时实验数据、工程师审批、隔离的Git工作树、并行智能体与自动校验。在50个失效开关的评测中，系统为45个生成了可用PR，平均每次13.8分钟、成本4.79美元，而人工清理估计需1至2小时。","reason":"这是一个AI Agent进入工程数据治理场景的完整落地案例，包含评测数字、成本与人工对比、MCP工具接口等可复用细节，对做Data Agent与平台AI化的从业者有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":[],"topics":["Data Agent","平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":40,"quality_score":88,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":88,"shelf":"evergreen","pinned":false,"published":"2026-09-18T21:50:00+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.infoq.com/news/2026/09/doordash-feature-flag-cleanup/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"677217a95906","zh_title":"高并发人脸核验系统的四层架构设计","zh_summary":"文章以三千名员工同时打卡导致系统崩溃的实战教训切入，提出高吞吐人脸核验的四层架构：客户端侧做输入质量过滤（旋转、光照、模糊归一化），将云端成本降低约30%；把无状态的检测与有状态的核验解耦，使检测吞吐达到核验的十倍；用基于风险的动态阈值替代厂商静态阈值；并以短期令牌替代原始PII、静态加密和激进的数据留存策略实现零信任合规。核心观点是人脸核验应按分布式系统问题而非简单API集成来设计，需依赖异步队列、熔断与负载均衡应对并发峰值。","reason":"内容属人脸识别与身份核验系统架构，不涉及本站覆盖的Data Agent、AI数据平台、BI可视化、数据产品或业务AI分析领域。","category":"platform","category_label":"AI 数据平台","vendors":["Azure","AWS"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":30,"quality_score":66,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":66,"shelf":"evergreen","pinned":false,"published":"2026-09-18T17:00:00+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.infoq.com/articles/secure-scalable-facial-verification/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"ec9943e319c5","zh_title":"Dropbox 将 Riviera 升级为通用内容处理平台，支撑 AI 负载","zh_summary":"Dropbox 把内部文件预览服务 Riviera 演进为通用内容处理平台，支持 300 多种文件格式和 100 多项转换能力，每秒处理数十万次转换。平台采用可组合转换管线，将编排与执行分离，通过插件模型扩展新能力。Riviera 现已服务 Search、Replay、Sign、Dash 等产品，AI 负载可直接复用此前为预览构建的处理基础设施。该平台此前日均处理约 25 亿次请求、接近 1EB 数据，并利用缓存中间结果供多个 AI 操作复用。","reason":"这是数据基础设施与 AI 负载结合的典型第一方工程实践，展示了内容处理管线、转换复用与缓存设计如何支撑 AI 搜索与问答，对数据平台与 AI 应用架构从业者有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Dropbox"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","知识与上下文"],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-09-16T22:42:00+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.infoq.com/news/2026/09/dropbox-riviera-ai-platform/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"8ac6899a569e","zh_title":"Snowflake DCP 私有数据接入指南","zh_summary":"本文介绍 Snowflake 为 Openflow 推出的 Data Connectivity Proxy（DCP）部署方式。DCP 是部署在客户自有网络内的轻量容器化代理，通过单一出站 443 端口与 Snowflake 代理端点建立 HTTPS 隧道，使 Openflow 连接器可接入防火墙后、私有子网乃至本地部署的数据库、API 和 Kafka。该方案无需入站防火墙规则、公网 IP 或 PrivateLink 基础设施，且 Enterprise 版客户无需升级到 Business Critical 即可实现私有连接。","reason":"对需要把本地或私有 VPC 数据接入云数仓的数据团队而言，本文给出了免入站端口、十几分钟即可完成部署的私有连通方案，直接影响数据集成架构与合规设计。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["权限与安全"]},"heat":29,"quality_score":64,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":64,"shelf":"evergreen","pinned":false,"published":"2026-09-19T03:01:01+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://medium.com/snowflake/private-data-public-cloud-no-compromises-8ed951131703?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"fa10b9bbe065","zh_title":"DCP：Snowflake 通往本地私有数据的桥接实践","zh_summary":"Snowflake 的数据连接代理 DCP（Data Connectivity Proxy）可让 Snowflake 访问位于企业防火墙之后的数据库，无需开放入站端口、VPN 或公网 IP。文章以自建环境为例完整走通链路：在家用网络中搭建 Linux 主机、运行 Docker 版 Postgres、在同一主机部署 DCP agent，并在 Snowflake 侧配置 DCP 对象、网络规则与外部访问集成，最后验证隧道并用 Openflow connector 指向该私有库。文中提示 DCP 目前仅支持配合 Snowflake Openflow 使用，而非虚拟仓库发出的任意 SQL。","reason":"对需要把本地或私有云数据库接入 Snowflake 的数据团队来说，这是一份端到端可复现的连接方案，清楚说明了无需入站端口、VPN 的实现路径及当前功能边界。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["可靠性与评估"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-09-18T22:01:05+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://medium.com/snowflake/dcp-snowflakes-bridge-to-on-prem-data-21f9680a1d5c?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"7ac392ea710c","zh_title":"Snowflake AI 服务成本解析与治理指南","zh_summary":"本文系统梳理 Snowflake 上 Cortex AI 服务的成本构成与治理方式，涵盖 Cortex AI Functions、Cortex Agents、Cortex Search、CoCo 等组件的定价、计量与监控。Snowflake 引入独立于 Platform Credits 的 AI Credits 计费单位，所有版本客户按同一费率付费，跨区域路由方式可影响约 9% 的成本。文章说明 AI_COMPLETE() 这类调用会同时产生 AI Credits（大模型 token 处理）与 Platform Credits（仓库计算）两项费用，并给出用量视图、监控查询与支出护栏的实践方法。","reason":"直接面向在 Snowflake 上落地 AI 能力的数据团队，讲清了 AI Credits 计费口径、token 成本驱动因素与成本可观测性方案，是把 AI 负载纳入数据平台成本治理的实用参考。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["平台AI化"],"product_ids":["snowflake-cortex"],"focus":{"id":"ai-platform","label":"AI 数据平台","priority":1,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":37,"quality_score":83,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":83,"shelf":"evergreen","pinned":false,"published":"2026-09-18T01:35:49+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://medium.com/snowflake/understanding-and-managing-ai-service-costs-on-snowflake-a18db691909d?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"39972c74aa29","zh_title":"智能网络运营：从网络数据到代理式运营与更明智投资","zh_summary":"该白皮书讨论电信网络在软件化、分布式和數據密集型趋势下，运营商面临提升服务质量、降低运营支出并优化资本投向的压力。Snowflake 提出企业智能层，将网络、OSS、服务、客户与规划数据统一在受治理环境中，支持流式数据产品、分析与 AI 异常检测、语义上下文和代理，使智能可通过自然语言获取，并将建议连接到运营或规划行动。文章给出功能、诊断、自主和战略分析框架，面向工程师、NOC 团队以及网络运营总监和 CTO 等管理角色。","reason":"内容涉及将网络与运营数据转化为受治理的智能系统，并落地到代理式运营与投资决策，对关注数据平台、语义层与 Data Agent 在行业场景落地的数据从业者有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","知识与上下文"],"use_cases":["看板与报告","生产评估与运营"],"decision_concerns":["用户采用与业务价值","可靠性与评估"]},"heat":30,"quality_score":67,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":67,"shelf":"evergreen","pinned":false,"published":"2026-09-17T03:01:01+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://medium.com/snowflake/intelligent-network-operations-d84056379aba?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"610ddc3d94ab","zh_title":"Snowflake实时分析：可复现的亚秒级延迟基准测试","zh_summary":"本文针对Snowflake Interactive Warehouse在亚秒级实时查询场景下进行可复现基准测试，并公开完整GitHub代码。作者对比了ClickHouse、Iceberg、Databricks Lakehouse RT（Reyden引擎）等方案，指出实时引擎往往需要独立安全模型与数据副本，而Snowflake试图复用既有治理模型。文中质疑Databricks公布的258毫秒查询10亿行、620毫秒742行等数据缺乏可复现性，强调实时分析性能数据应当可验证。","reason":"面向数据平台与实时分析从业者，提供可复现的基准方法而非厂商营销数字，有助评估湖仓实时查询方案的延迟与治理权衡。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake","Databricks","ClickHouse"],"topics":["湖仓","实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":32,"quality_score":71,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":71,"shelf":"evergreen","pinned":false,"published":"2026-09-17T00:36:24+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://medium.com/snowflake/real-time-analytics-on-snowflake-a-repeatable-benchmark-for-sub-second-latency-at-scale-49b666f2deb2?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"eb90995c71f5","zh_title":"DuckDB-Wasm 结合 OPFS 实现浏览器持久化数据库","zh_summary":"DuckDB-Wasm 自 2021 年发布以来无法持久化数据库，数据只存在于 Wasm 堆内存中，关闭标签页即丢失，此前只能把表序列化为 Parquet 存入 IndexedDB 再重新注册。现代浏览器自 2023 年 3 月起支持 Origin Private File System（OPFS），提供按源隔离的沙箱文件系统与随机读写能力，DuckDB-Wasm 可将其作为存储后端。文章演示了以 opfs:// 路径打开数据库（如 opfs://analytics.duckdb，读写模式），生成带预写日志和检查点的标准 .duckdb 文件，可在页面重载与浏览器重启后存活。作者提醒 npm 上 latest 版本 1.33.1-dev57.0 会创建 OPFS 文件却不写入、路径被规范化为单斜杠导致不匹配，建议锁定 1.32.0 或使用 1.33.1-dev64.0 及以后的 next 标签。","reason":"浏览器端持久化是 DuckDB-Wasm 长期缺失的关键能力，OPFS 方案让纯前端分析应用无需自建应用层序列化即可保留数据，对做嵌入式分析与轻量数据产品的从业者有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["DuckDB"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["可靠性与评估"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-09-18T08:00:00+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://duckdb.org/2026/09/18/opfs-wasm.html","items":[{"source":"DuckDB Engineering Blog"}],"source_badge":"RSS"},{"event_id":"a6d68993f8e6","zh_title":"为什么你的AI Agent其实什么都记不住","zh_summary":"本文探讨AI Agent的记忆问题，指出持久化只是最简单的部分，真正的难点在于记忆的选择、压缩、衰减与污染防控。作者以客服Agent为例：用户周一咨询账单问题，周三回来继续对话时Agent却完全失忆，不知道用户是谁、之前的问题是什么、已尝试过什么、承诺过什么。文章区分了记忆与幂等性、工作流状态、事务一致性三者的不同，并指出记忆逻辑应存在于查询中，包括读取时的衰减、置信度加权与污染过滤。","reason":"Agent记忆是构建可生产Data Agent/分析Agent的核心工程难题，本文明确了记忆与幂等、状态机的边界，并给出读取时记忆逻辑的实现思路，对做Agent的从业者有直接借鉴价值。","category":"agent","category_label":"Data Agent","vendors":["PingCAP","TiDB"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":["Agent构建"],"decision_concerns":["可靠性与评估","可维护性与复用"]},"heat":30,"quality_score":67,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":67,"shelf":"evergreen","pinned":false,"published":"2026-09-18T00:14:23+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.pingcap.com/blog/long-term-memory-ai-agents/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"c98d04acd1bf","zh_title":"AI编程Agent的文件层:持久化工作区如何挺过重置","zh_summary":"文章指出AI编程Agent的文件不只是最终diff,还包括克隆的仓库、依赖清单、构建与测试输出、日志、补丁和草稿笔记。临时沙箱把文件层与计算绑定,超时或崩溃会无提示地抹掉数小时工作。持久化文件系统把存储与沙箱生命周期解耦,让新的运行时重开同一工作区。但任何持久化模型都无法恢复运行中的进程、打开的socket或内存状态,只有落盘内容存活;持久元数据、权限与工作流状态仍需数据库承载。","reason":"对构建Data Agent与Agent基础设施的团队有直接参考价值:它讲清了Agent工作区持久化的机制边界——文件能解决连续性,但状态与权限仍需数据库,是落地时的关键设计取舍。","category":"agent","category_label":"Data Agent","vendors":["PingCAP","TiDB"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","Agent接口与工具"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","可维护性与复用"]},"heat":33,"quality_score":73,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":73,"shelf":"evergreen","pinned":false,"published":"2026-09-14T22:57:17+08:00","first_seen":"2026-09-19T23:55:00.092165+08:00","original_url":"https://www.pingcap.com/blog/ai-coding-agent-files/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"0afd2b5824d2","zh_title":"Databricks营销团队如何用Genie让数据使用量提升3倍","zh_summary":"Databricks营销团队曾面临数据分散、看板陈旧或不一致、可信答案获取慢等问题。团队在受治理的湖仓上统一营销数据，并基于Genie Agents构建内部助手Marge，让营销人员用自然语言获取受治理答案。结果显示，营销数据使用频率提升3倍，85%以上营销组织使用Marge，季度使用量增长50%，每月处理800+问题、累计回答5000+。标记错误响应下降25%，并在不增加分析人力的前提下扩大洞察访问；其做法是把对话式分析作为持续产品和运营模式。","reason":"该案例给出对话式分析在营销组织中的落地指标、采纳路径和治理要点，可帮助数据从业者设计ChatBI/Data Agent的产品与运营模式。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["Data Agent","ChatBI"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","知识与上下文"],"use_cases":["指标问答","自助分析"],"decision_concerns":["准确性与语义一致性","用户采用与业务价值"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-09-15T08:36:33+08:00","first_seen":"2026-09-16T05:24:28.960602+08:00","original_url":"https://www.databricks.com/blog/databricks-marketers-use-data-3x-genie-ai-analytics-assistant","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"0e858c1b5028","zh_title":"美联航用Redshift联邦查询Databricks数据","zh_summary":"AWS与美联航工程师介绍，美联航每天处理数十亿事件，数据平台横跨Amazon Redshift和Databricks Unity Catalog。为在不复制数据的情况下打通平台，团队使用AWS Glue Data Catalog联邦，让Redshift Serverless可直接对S3中的Iceberg表运行实时SQL查询。方案避免了将数据复制到Redshift Managed Storage并维护同步管道。文中还提到Redshift Serverless所用Graviton查询引擎对比前代可带来最高2倍数据湖查询性能。","reason":"该实践展示了跨Redshift与Databricks的湖仓目录联邦和零拷贝查询架构，对多平台数据集成、避免冗余同步、提升分析时效有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Databricks"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-09-15T23:59:48+08:00","first_seen":"2026-09-16T05:24:28.960602+08:00","original_url":"https://aws.amazon.com/blogs/big-data/how-united-airlines-uses-amazon-redshift-and-aws-glue-data-catalog-federation-to-query-databricks-managed-data/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"eee1c02052f9","zh_title":"Snowflake DCM 多环境数据库变更管理指南","zh_summary":"文章介绍在 Snowflake 中跨 DEV、QA、PROD 三套环境管理数据库变更的实践。作者最初使用 SchemaChange，但随着环境、对象和贡献者增多，出现命名规范、变更遗漏和反复 rebase 等运维负担。随后他们转向 Snowflake DCM Projects，希望通过声明式定义和 plan-then-deploy 工作流，实现版本控制、可重复的多环境部署。DCM 允许在定义文件中声明数据库、schema、表等对象的目标状态，由 Snowflake 计算并应用变更。","reason":"对负责 Snowflake 多环境发布的数据平台工程师有直接参考价值，解释了从命令式 SQL 变更管理转向声明式 DCM 的动因与机制。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":[],"decision_concerns":["可靠性与评估","可维护性与复用"]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"evergreen","pinned":false,"published":"2026-09-16T03:01:02+08:00","first_seen":"2026-09-16T05:24:28.960602+08:00","original_url":"https://medium.com/snowflake/snowflake-dcm-projects-setup-guide-database-change-management-c82f5e33bd34?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"537b81bfdf56","zh_title":"Data Agent 上线了，为什么还不能上岗","zh_summary":"文章指出，Data Agent 进入业务试用阶段后，客户关注点正从准确率“面试”转向真实岗位“试用”。当前 Data Agent 往往需要 IT、数据团队和厂商先花三五个月配置权限、元数据、指标口径、语义和知识，上线后仍比新分析师更慢开始工作。作者提出“30 分钟上岗”，主张让 Agent 在部门和岗位确定、数据和报表权限配置后，自主完成数据资产筛选、字段/取值/新鲜度探查、历史报表与 SQL 学习，并通过执行结果校准。文章还建议企业用真实试岗而非几十道题评估 Data Agent，并预告 10 月 23 日 DaCon 北京站演讲。","reason":"文章从交付与试用视角讨论 Data Agent 的上岗冷启动和评估方法，指出实施周期与真实业务价值之间的落差，对数据团队设计 Agent 落地路径有参考价值。","category":"agent","category_label":"Data Agent","vendors":["Aloudata"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","知识与上下文"],"use_cases":["生产评估与运营"],"decision_concerns":["用户采用与业务价值","可靠性与评估"]},"heat":36,"quality_score":70,"trend_score":7,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-09-15T14:47:26+08:00","first_seen":"2026-09-15T19:47:13.175587+08:00","original_url":"https://aloudata.com/news/data-agent-deployed-but-not-ready-for-work","items":[{"source":"Aloudata 动态"},{"source":"Aloudata 博客"}],"source_badge":"官网"},{"event_id":"510e7cc5672e","zh_title":"托管 Postgres：Lakebase 实际替你分担了什么","zh_summary":"文章讨论 Lakebase 所代表的托管 Postgres 在 AI 应用中的价值，核心是 Postgres 能否在同一系统中承载事务状态与向量检索。它介绍了 pgvector、向量/语义搜索、LLM 记忆和 Agent 工作负载，说明嵌入可与业务数据同库存储，减少同步与运维问题。文章也指出，超大规模专用向量检索仍可能需要独立向量数据库，索引策略需按数据规模和查询模式评估。","reason":"数据从业者可关注托管 Postgres 如何把向量检索、LLM 记忆和 Agent 状态统一到数据库层，以及何时仍应选择专用向量库。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":["Agent构建"],"decision_concerns":["可维护性与复用","成本与性能"]},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-09-15T07:36:59+08:00","first_seen":"2026-09-15T19:47:13.175587+08:00","original_url":"https://www.databricks.com/blog/managed-postgres","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"9f8f09e080f9","zh_title":"什么是劳动力上下文？AI与员工数据之间缺失的一层","zh_summary":"文章用 Google Maps 从经纬度到路线指引的类比，说明原始员工数据虽准确却不足以让 AI 给出可行动答案。S&P Global 451 Research 的调查显示，生产级生成式 AI 的四大限制是数据隐私与安全、准确性与回答质量、部署成本、与现有系统集成。员工数据动态变化，向 LLM 询问“当前 headcount”会立刻涉及计算口径、统计时点、是否含承包商以及查看权限。文章据此提出 workforce context（劳动力上下文），强调 AI 需要理解含义、时效和权限，才能可信回答人员数据问题。","reason":"对数据从业者，文章把语义、时效和权限上下文作为 AI 可信回答人员数据的前提，这一思路可迁移到企业指标问答、语义层与 AI 数据治理建设。","category":"platform","category_label":"AI 数据平台","vendors":["Visier"],"topics":["语义层","组织人才"],"product_ids":[],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["指标问答"],"decision_concerns":["准确性与语义一致性","权限与安全"]},"heat":25,"quality_score":56,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":56,"shelf":"evergreen","pinned":false,"published":"2026-09-15T05:53:14.713318+08:00","first_seen":"2026-09-15T05:53:14.713318+08:00","original_url":"https://www.visier.com/blog/what-is-workforce-context/","items":[{"source":"Visier Blog"}],"source_badge":"RSS"},{"event_id":"d7b6cc4a3303","zh_title":"一致性星型模型：多事实表如何在语义视图中共享维度而不产生歧义","zh_summary":"这是一组13篇系列文章的第1篇，主题是语义视图中的一致性星型模型。文中举例说明：两个团队为同一季度复盘拉取“按地区统计的收入”，数字对不上却都没写错查询，原因是各自查询了记录交易发生的系统与记录回款的系统，两者都叫 REVENUE、连接同样的客户与日历表，但衡量的是根本不同的业务流程。作者认为问题在于模式本身对指标含义保持沉默，语义视图通过为每个事实表注册各自的命名指标（如 total_principal、total_repaid、total_balance）并限定其关系范围来解决，避免直接写 SQL 或 AI 生成 SQL 时护栏失效。","reason":"多事实表共享一致性维度导致的指标歧义，是语义层与 Text-to-SQL 落地中最常见的准确性问题，本文给出了结构化的建模思路，对做指标语义和数据 Agent 的从业者有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["语义层","ChatBI"],"product_ids":[],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义"],"use_cases":["指标问答"],"decision_concerns":["准确性与语义一致性"]},"heat":32,"quality_score":71,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":71,"shelf":"evergreen","pinned":false,"published":"2026-09-14T22:01:07+08:00","first_seen":"2026-09-15T05:53:14.713318+08:00","original_url":"https://medium.com/snowflake/conformed-star-schema-in-semantic-views-how-multi-fact-models-share-dimensions-without-ambiguity-cd2f99e81bfb?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"a112e98a96f3","zh_title":"无需外部编排器：在 Postgres 上实现持久工作流","zh_summary":"文章介绍如何用 Postgres 充当持久状态存储与协调层，从而避免引入 Temporal 或 AWS Step Functions 等外部编排器。它用 SELECT ... FOR UPDATE SKIP LOCKED 构建并发工作队列，用主键检查点强制幂等，并通过租约与清理器实现崩溃恢复。工作流休眠和人工审批也可持久化为数据库状态，在重启后继续执行。作者来自 Kestrel Workflows，示例场景包括事故响应、云资源供给、CI/CD 和开发者请求。","reason":"为需要在数据平台或自动化系统中实现可靠工作流的从业者提供数据库原生方案，减少外部依赖，并覆盖幂等、并发与崩溃恢复等关键机制。","category":"platform","category_label":"AI 数据平台","vendors":["Postgres","Temporal","AWS Step Functions"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","可维护性与复用"]},"heat":35,"quality_score":77,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":77,"shelf":"evergreen","pinned":false,"published":"2026-09-14T19:00:00+08:00","first_seen":"2026-09-14T20:49:06.725377+08:00","original_url":"https://www.infoq.com/articles/durable-workflows-postgres/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"80c7dbc69c9c","zh_title":"在Databricks上实现端到端Solvency II报告的实际方法","zh_summary":"Solvency II报告不仅是监管提交，更是连接数据、模型、控制、审批和披露的业务流程。Databricks保险解决方案架构师演示了从数据接入、精算准备金、资本计算到QRT、ORSA、治理审批和披露的端到端实现。该演示针对报告流程分散在多系统、缺乏统一视图的痛点，展示了如何用Databricks形成可治理的完整报告闭环。","reason":"数据从业者可借鉴保险监管报告场景下的端到端数据治理与流程编排方法，对复杂合规报表体系建设有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["风险管理"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["看板与报告"],"decision_concerns":["可维护性与复用"]},"heat":26,"quality_score":57,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":57,"shelf":"evergreen","pinned":false,"published":"2026-09-10T00:20:00+08:00","first_seen":"2026-09-14T12:58:12.012623+08:00","original_url":"https://www.databricks.com/blog/practical-approach-end-end-solvency-ii-reporting-databricks","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"2a38d7e7886d","zh_title":"从检索到推理：用知识图谱构建生产级 Agentic AI","zh_summary":"Cassie Shum 分享如何以知识图谱作为 agentic 系统的关键基础，超越基础 RAG，并提出四种实用架构模式：上下文打包、决策溯源、代码即事实、Agent 可见性。她展示了一个基于知识图谱构建的工程化 harness，用于简化反馈闭环、优化 token 使用并维持系统可靠性。内容来自她在 RelationalAI 的实践经验，但目前可见文本主要停留在开场与框架介绍。","reason":"数据从业者若关注 Data Agent 的生产化落地，可了解知识图谱如何支撑上下文、决策溯源与系统可靠性，并涉及 token 成本和反馈闭环。","category":"agent","category_label":"Data Agent","vendors":["RelationalAI"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-09-12T19:00:00+08:00","first_seen":"2026-09-13T12:49:26.432347+08:00","original_url":"https://www.infoq.com/presentations/knowledge-graphs-agentic-systems-patterns/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"e19bdeb4b036","zh_title":"Anthropic经济指数：Claude使用节奏与经济影响","zh_summary":"Anthropic 发布经济指数报告，指出随着 Claude Code 和 Cowork 增长，Claude 会话越来越多由长时 agentic 任务构成，传统聊天记录已不足以反映使用方式。报告调整数据管道：提高采样率以观察小时级模式，引入输出分类器，并拆分 chat/Cowork 与 1P API 的月度数据。报告还分享 2026 年 4 月启动的 Anthropic Economic Index Survey 初步发现，包括周末工作查询减少、高薪职业降幅较小、新闻查询集中在早晨、睡眠建议约凌晨 5 点、税务请求在截止日前激增。第二章讨论不同产品的输出差异，例如 Chat/Cowork 比 Claude Code 提供更多解释，网站构建比文档翻译更依赖 Claude 判断。","reason":"该报告提供第一方 Claude 使用数据与分类方法，可帮助数据从业者理解 agentic 工作负载的节奏、产品形态差异及 AI 采用情况，对设计 Data Agent 和分析产品有参考价值。","category":"product","category_label":"数据产品","vendors":["Anthropic","Claude"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["用户采用与业务价值"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-09-11T19:57:10+08:00","first_seen":"2026-09-12T23:34:51.151734+08:00","original_url":"https://www.anthropic.com/research/economic-index-june-2026-report","items":[{"source":"Anthropic Economic Index"}],"source_badge":"官网"},{"event_id":"825556db5df8","zh_title":"一年25万VS每月1500美元：大厂AI预算分裂","zh_summary":"文章对比英伟达按人均25万美元年度Token预算与Uber给工程师设每月1500美元上限，借Leonis Capital分析指出企业买AI正跑两套经济学。扩张型市场里智能直接换增长，效率型市场里智能越过约束线后只剩替代劳动力价格。文中引用Uber约70%已提交代码由AI生成、98%从业者管理AI支出、73%企业超出AI成本预期等数据。结论认为多数财富500强是效率型买家，下一阶段重点是Token分配、每任务成本考核与开源模型机会。","reason":"数据从业者若负责AI工具或数据平台预算，可借此理解企业AI支出从“代币最大化”转向按任务成本、开源路由和ROI考核的逻辑，对平台选型与成本治理有参考。","category":"insight","category_label":"AI分析","vendors":[],"topics":["财务经营"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["成本与性能"]},"heat":27,"quality_score":61,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":61,"shelf":"evergreen","pinned":false,"published":"2026-09-12T14:26:28+08:00","first_seen":"2026-09-12T23:34:51.151734+08:00","original_url":"https://www.woshipm.com/ai/6463038.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"9033e4dee9cb","zh_title":"蚂蚁AI Agent大规模企业级执行边界实践","zh_summary":"蚂蚁集团在QCon上海分享其ARCA执行边界体系，围绕Sandboxed Agent、Agentic RL、Agent Harness+Tool Use三类场景，解决Agent执行中的隔离难、启动慢、状态重、规模大、治理散问题。ARCA Sandbox提供安全隔离、缓存池、持久化存储、内存快照、镜像预热、网络隔离与成本治理；Piston负责Agent托管、生命周期管理、灰度发布；Tool Gateway将高危动作路由到受控沙箱执行。该系统支撑蚂蚁多个重点Agent场景，达到数万级每日沙箱创建、千万级日请求和万核级资源峰值。","reason":"它直接讨论企业级AI Agent从Demo走向规模化落地时的执行底座、安全隔离、状态管理和成本治理，对构建Data Agent/分析Agent的工程团队有重要参考价值。","category":"agent","category_label":"Data Agent","vendors":["蚂蚁集团"],"topics":["Data Agent","平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","权限与治理"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-09-12T18:00:00+08:00","first_seen":"2026-09-12T23:34:51.151734+08:00","original_url":"https://www.infoq.cn/article/hk3WB50fAOMDg55YVaaW?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"4d75839a2208","zh_title":"用业务问题集把 Genie Space 从能演示做到可验收","zh_summary":"以营销分析为例，逐步修正元数据、关联关系、CTR 等指标定义和业务规则，用 benchmark 检查每次修改。","reason":"最适合先读：可以直接借鉴“业务问题—参考答案—失败归因—回归验证”的上线流程。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["Data Agent"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"source_date_label":"原文 2026-02-06","heat":40,"quality_score":80,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"X","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-02-06T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://www.databricks.com/blog/how-build-production-ready-genie-spaces-and-build-trust-along-way","items":[{"source":"Databricks"},{"source":"X 线索"}],"source_badge":"RSS"},{"event_id":"64843a2454f2","zh_title":"Cortex Agent 评测：既检查答案，也检查工具执行过程","zh_summary":"把问题、参考答案与执行轨迹结合，检查答案正确性和逻辑一致性，并比较不同配置的成本与延迟。","reason":"适合建立数据 Agent 的质量门槛，区分选错工具、执行出错和最终回答错误。","category":"agent","category_label":"Data Agent","vendors":["Snowflake"],"topics":["Data Agent"],"product_ids":["snowflake-cortex"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"source_date_label":"原文 2026-03-13","heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-03-13T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://www.snowflake.com/en/blog/engineering/cortex-agent-evaluations/","items":[{"source":"Snowflake"}],"source_badge":"RSS"},{"event_id":"82d023cf6dcc","zh_title":"从 API 搭建 BigQuery 对话式数据 Agent","zh_summary":"教程给出数据源与上下文配置、会话管理、流式回复，以及 SQL、结果表和 Vega-Lite 图表的处理方式。","reason":"能回答“怎么把数据 Agent 接进自己的产品”，适合作为实现参考。","category":"agent","category_label":"Data Agent","vendors":["Google Cloud"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"source_date_label":"原文 2026-02-19","heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-02-19T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://cloud.google.com/blog/products/data-analytics/build-data-agents-with-conversational-analytics-api","items":[{"source":"Google Cloud"}],"source_badge":"RSS"},{"event_id":"818d9d4e44f6","zh_title":"Genie Agent Mode：围绕假设反复查询，解释业务变化","zh_summary":"对复杂问题先规划，再执行多次查询、检验假设并调整方向；答案附 SQL 和图表，并按问题复杂度分配推理。","reason":"有助于设计从“查一个数”升级到“解释为什么”的分析流程及证据展示。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["Data Agent"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"source_date_label":"原文 2026-04-17","heat":40,"quality_score":80,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"X","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-04-17T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://www.databricks.com/blog/introducing-genie-agent-mode","items":[{"source":"Databricks"},{"source":"X 线索"}],"source_badge":"RSS"},{"event_id":"598be2f438cd","zh_title":"把周报和流失分析沉淀成可版本管理的 Agent Skills","zh_summary":"将重复分析步骤写成项目内 Markdown skill，与数据模型一起评审、测试和部署，可通过按钮、命令或意图匹配调用。","reason":"适合把固定业务分析做成可复用产品能力，减少每次重新组织长提示词。","category":"agent","category_label":"Data Agent","vendors":["Cube"],"topics":["Data Agent"],"product_ids":["cube"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"source_date_label":"原文 2026-06-02","heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-06-02T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://cube.dev/blog/introducing-cube-agent-skills","items":[{"source":"Cube"}],"source_badge":"RSS"},{"event_id":"e12a2952d00e","zh_title":"多数据源 Agent 如何把问题路由到正确的数据集","zh_summary":"官方更新列出数据源路由 GA：结合 schema、数据源描述、示例查询和路由规则，选择 lakehouse、warehouse、语义模型或 KQL 数据库。","reason":"适合解决企业接入很多数据源后，Agent 选错表、选错引擎的问题。","category":"agent","category_label":"Data Agent","vendors":["Microsoft Fabric"],"topics":["Data Agent"],"product_ids":["fabric-data-agent"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"source_date_label":"2026-08（官方 GA 月份）","heat":40,"quality_score":80,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://learn.microsoft.com/en-us/fabric/fundamentals/whats-new#data-science","items":[{"source":"Microsoft Fabric"},{"source":"Microsoft Fabric"}],"source_badge":"RSS"},{"event_id":"ab71223dcc04","zh_title":"dbt MCP 的生产模式与大表查询成本陷阱","zh_summary":"总结受治理指标问答、文档初稿、CI 测试和跨工具编排；明确指出大表全扫描容易引发超时和仓库费用，应预物化或设置查询限制。","reason":"对“控制成本”尤其有用：MCP 接通后，还要限制扫描量、执行时间和可调用工具。","category":"agent","category_label":"Data Agent","vendors":["dbt Labs"],"topics":["Data Agent"],"product_ids":["dbt"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"source_date_label":"原文 2026-05-01（6 月 16 日更新）","heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-05-01T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://www.getdbt.com/blog/5-dbt-mcp-server-patterns-that-work-in-production","items":[{"source":"dbt Labs"}],"source_badge":"RSS"},{"event_id":"bd750fad1df5","zh_title":"Cortex Agents 平台：版本、租户隔离、预算与工具治理","zh_summary":"将 MCP 连接、可复用 skills、Python 沙箱与 Agent 版本管理、租户隔离、预算和评测放在同一运行平台。","reason":"适合梳理 AI 数据平台的必要底座，尤其是多租户、执行环境和费用归属。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["平台AI化","Data Agent"],"product_ids":["snowflake-cortex"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"source_date_label":"原文 2026-04-21","heat":40,"quality_score":80,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"X","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-04-21T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://www.snowflake.com/en/blog/enterprise-ai-agent-platform/","items":[{"source":"Snowflake"},{"source":"X 线索"}],"source_badge":"RSS"},{"event_id":"7e46d654139f","zh_title":"Genie Code：把长任务、数据资产与 ML 工程放进同一工作区","zh_summary":"全页工作区支持多任务状态和结果审阅；Agent 可使用 MLflow 实验与血缘、服务端点信息，以及团队指令、skills 和连接器。","reason":"产品价值在任务执行与审阅闭环，适合参考数据开发平台如何承载持续工作。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化","Data Agent"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"source_date_label":"原文 2026-06-17","heat":40,"quality_score":80,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"X","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-06-17T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://www.databricks.com/blog/whats-new-genie-code-data-ai-summit-2026","items":[{"source":"Databricks"},{"source":"X 线索"}],"source_badge":"RSS"},{"event_id":"014ecba7e596","zh_title":"Knowledge Catalog：为 Agent 聚合、补全和检索业务上下文","zh_summary":"围绕上下文聚合、语义补全和检索组织目录，关联技术元数据、语义定义、验证查询和数据产品，并考虑源系统访问权限。","reason":"适合定义 AI 数据平台的上下文基础设施，而不是再造一个表清单。","category":"platform","category_label":"AI 数据平台","vendors":["Google Cloud"],"topics":["平台AI化","Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"source_date_label":"原文 2026-04-22","heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-04-22T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://cloud.google.com/blog/products/data-analytics/introducing-the-google-cloud-knowledge-catalog","items":[{"source":"Google Cloud"}],"source_badge":"RSS"},{"event_id":"f38e097a8967","zh_title":"Context Studio：观察真实问答，再测试并发布上下文修正","zh_summary":"提供问题观察、Thread 检查、上下文认证与语义模型管理，以及部署前预览和版本控制。","reason":"把数据团队从逐个补提示词，带到可观察、可修正、可发布的管理流程。","category":"platform","category_label":"AI 数据平台","vendors":["Hex"],"topics":["平台AI化","Data Agent"],"product_ids":["hex"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"source_date_label":"原文 2026-01-28","heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-01-28T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://learn.hex.tech/changelog/2026-01-28","items":[{"source":"Hex"}],"source_badge":"RSS"},{"event_id":"9574a86569ae","zh_title":"Snowflake 内部实践：语义定义、物化加速与问题路由一起做","zh_summary":"用语义视图统一指标，通过代码评审与测试维护；用热门看板问题构造评测集，以物化减少慢查询，并持续整理路由规则。","reason":"既讲指标口径，也讲响应速度和维护方式，适合长期保留。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["语义层"],"product_ids":["snowflake-cortex"],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":true},"source_date_label":"原文 2026-08-17","heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-08-17T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://www.snowflake.com/en/blog/snowflake-internal-context-layer-for-ai-agents/","items":[{"source":"Snowflake"}],"source_badge":"RSS"},{"event_id":"7175222a4aa1","zh_title":"语义上下文是否有效：同题、同模型的配对评测","zh_summary":"比较仅给 schema 与额外提供一份 4 KB 业务语义文档的结果，公开问题、参考 SQL、方法和代码，报告约 17–23 个百分点的提升。","reason":"值得借鉴评测设计：先固定业务题与执行条件，再验证语义投入是否改善结果。","category":"platform","category_label":"AI 数据平台","vendors":["Cube"],"topics":["语义层"],"product_ids":["cube"],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":true},"source_date_label":"原文 2026-04-28","heat":44,"quality_score":80,"trend_score":15,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-04-28T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://cube.dev/blog/why-semantic-layers-make-llm-analytics-reliable-a-paired-benchmark-across-three-frontier-models","items":[{"source":"Cube"},{"source":"Cube"},{"source":"Cube"}],"source_badge":"RSS"},{"event_id":"c81741c8eae1","zh_title":"AI 可以重写语义模型，业务问答契约应该保留在哪里","zh_summary":"团队用 Agent 生成并验证 Malloy 模型；在其测试中，Markdown + SQL 更省 token。文章主张用问题与答案对保留业务意图和验收条件。","reason":"提供一个有价值的设计视角：把业务意图与生成代码分开维护，并为重新生成建立验收依据。","category":"platform","category_label":"AI 数据平台","vendors":["MotherDuck"],"topics":["语义层"],"product_ids":["motherduck"],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":true},"source_date_label":"原文 2026-08-20","heat":40,"quality_score":80,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"X","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-08-20T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://motherduck.com/blog/AI-writes-the-semantic-layer/","items":[{"source":"MotherDuck"},{"source":"X 线索"}],"source_badge":"RSS"},{"event_id":"1040324d5b86","zh_title":"Snowflake语义视图与Spotter语义：指标口径分裂难题","zh_summary":"文章从企业常见场景切入：同一季度营收，一份报表显示4200万美元，另一份显示4400万美元，两者都基于已批准数据，差异源于口径——一个按下单日期统计、另一个按发货日期，一个含退款、另一个不含，客户关联字段也不同。作者指出这不是数据质量问题，而是「意义」问题，并认为组织规模扩张、自助式分析普及以及AI代理写SQL三件事让该问题恶化，尤其AI代理会自信地选错关联路径且不自我怀疑，因此语义治理是规模化智能的前提。","reason":"文章用具体数字场景讲清指标口径不一致的成因，并直指AI代理自动生成SQL时语义层缺失带来的规模化风险，对做ChatBI、语义层与AI数据平台的从业者是核心议题。","category":"platform","category_label":"AI 数据平台","vendors":["ThoughtSpot","Snowflake"],"topics":["语义层","Data Agent"],"product_ids":["thoughtspot"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"source_date_label":"2026-05-13（X 分享日；原文日期未注明）","work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义"],"use_cases":["指标问答","自助分析"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":35,"quality_score":61,"trend_score":15,"star":false,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"X","importance":61,"shelf":"evergreen","pinned":false,"published":"2026-09-14T22:01:06+08:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://www.thoughtspot.com/blog/snowflake-semantic-views-thoughtspot-one-ai-context-layer","items":[{"source":"ThoughtSpot"},{"source":"X 线索"},{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"c218bd27e661","zh_title":"Looker Embedded：在业务应用里继续多轮分析并解释 SQL","zh_summary":"将基于 Looker 语义模型的对话分析通过 iframe、SDK 或 API 嵌入应用；支持多轮问题、多个 Explore、代码解释器与 SQL 解释。","reason":"可以参考如何让分析进入业务现场，同时复用身份管理、指标定义和可解释的查询。","category":"insight","category_label":"AI分析","vendors":["Google Cloud"],"topics":["ChatBI"],"product_ids":["looker"],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":false},"source_date_label":"原文 2026-04-06","heat":40,"quality_score":80,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"X","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-04-06T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://cloud.google.com/blog/products/business-intelligence/looker-embedded-adds-conversational-analytics","items":[{"source":"Google Cloud"},{"source":"X 线索"}],"source_badge":"RSS"},{"event_id":"60f9a9e4ae1a","zh_title":"IAS：从看板异常追到 dbt SQL，再用只读查询验证","zh_summary":"结合 Looker 入口、dbt 模型与血缘、Databricks 只读 SQL；Agent 调查指标逻辑，按业务用户或分析师输出不同细节。","reason":"最贴近可落地的数据诊断产品：还给出了工具拆分、模型分档和多 Agent 路由的取舍。","category":"insight","category_label":"AI分析","vendors":["dbt Labs / IAS"],"topics":["ChatBI"],"product_ids":["dbt","looker"],"focus":{"id":"ai-analysis","label":"AI 数据分析","priority":3,"practical":false},"source_date_label":"原文 2026-07-07","heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-07-07T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://courses.getdbt.com/blog/mcp-dbt-databricks","items":[{"source":"dbt Labs / IAS"}],"source_badge":"RSS"},{"event_id":"8381a579fe49","zh_title":"Chat with App：利用当前看板的逻辑和筛选状态继续追问","zh_summary":"对已发布应用提问，理解底层逻辑、定位单元格并调整筛选器和输入；同时引入只使用经数据团队认证上下文的模式。","reason":"适合设计看板内分析助手：用户已有的上下文可以减少重复解释和错误选数。","category":"insight","category_label":"AI分析","vendors":["Hex"],"topics":["ChatBI"],"product_ids":["hex"],"focus":{"id":"ai-analysis","label":"AI 数据分析","priority":3,"practical":true},"source_date_label":"原文 2026-01-21","heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-01-21T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://learn.hex.tech/changelog/2026-01-21","items":[{"source":"Hex"}],"source_badge":"RSS"},{"event_id":"3c77505eef20","zh_title":"Generative Data Apps：可生成的界面建立在可检查的分析计算之上","zh_summary":"Agent 生成 JavaScript 界面与图表，数据查询和变换仍由 Hex 项目承载，并沿用上下文、发布和数据刷新机制。","reason":"适合搭建 AI 数据产品：生成界面、分析计算和发布权限需要各有明确责任。","category":"product","category_label":"数据产品","vendors":["Hex"],"topics":["BI变局","ChatBI"],"product_ids":["hex"],"focus":{"id":"ai-platform","label":"AI 数据平台","priority":1,"practical":true},"source_date_label":"原文 2026-05-12","heat":40,"quality_score":80,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-05-12T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://learn.hex.tech/changelog/2026-05-12","items":[{"source":"Hex"},{"source":"Hex"}],"source_badge":"RSS"},{"event_id":"06473dc33f26","zh_title":"Dashboards as code：AI 生成看板后进入 Git 审阅流程","zh_summary":"AI 工具读取 Metabase 元数据、编写查询并生成 dashboard YAML，提交 Git 待审阅；版本同时加入 AI 权限、token 限额与使用量分析。","reason":"适合希望可回滚、可评审并控制 AI 费用的数据产品团队。","category":"product","category_label":"数据产品","vendors":["Metabase"],"topics":["BI变局","ChatBI"],"product_ids":["metabase"],"focus":{"id":"ai-dashboard","label":"AI 看板","priority":4,"practical":true},"source_date_label":"原文 2026-05-20","heat":40,"quality_score":80,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-09-12T13:30:00+08:00","discovery_source":"X","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-05-20T00:00:00+00:00","first_seen":"2026-09-12T13:30:00+08:00","original_url":"https://www.metabase.com/releases/metabase-61","items":[{"source":"Metabase"},{"source":"X 线索"}],"source_badge":"RSS"},{"event_id":"4e1f47dc01ac","zh_title":"健康计划：BI显示MLR变动，AI能解释原因吗？","zh_summary":"文章以健康计划CFO月度结算为例：BI仪表盘能快速发现医疗赔付率（MLR）高于预算，但无法解释是哪个业务线/市场、利用率、单位成本还是服务结构导致。Databricks与Abacus结合受治理的企业数据和payer特定数据基础、业务上下文与运营知识，让财务人员用AI在分钟级追问原因，并同时查看理赔、收入、会员、临床、质量和风险评分等信息。文章认为AI在payer finance的机会不只是发现差异，而是解释差异并支持纠正行动。","reason":"对做医疗payer财务分析、BI与分析Agent的数据从业者，本文展示了从看板报警到AI归因与行动的产品方向；但整体偏厂商方案阐述，缺少量化案例与实施细节。","category":"agent","category_label":"Data Agent","vendors":["Databricks","Abacus"],"topics":["Data Agent","财务经营"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["指标问答","自助分析"],"decision_concerns":["准确性与语义一致性","用户采用与业务价值"]},"heat":18,"quality_score":41,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":41,"shelf":"evergreen","pinned":false,"published":"2026-09-12T02:26:59+08:00","first_seen":"2026-09-12T05:00:12.168398+08:00","original_url":"https://www.databricks.com/blog/health-plans-your-bi-tells-you-mlr-moved-can-your-ai-tell-you-why","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"ac7b53978f0b","zh_title":"用 ClickHouse 将 Parquet 数据加载到 MySQL","zh_summary":"本文介绍如何用 ClickHouse 将 Parquet 文件数据加载到 MySQL，因为 MySQL 没有原生方式完成这一任务。作者用 Docker 启动 MySQL 8.4，下载 ClickHouse 二进制，并通过 named collection 配置 MySQL 连接信息。随后使用 url 表函数探索 S3 上的 StackOverflow votes 数据集，并用 ClickHouse 表函数和远程查询能力完成加载。该实践适合需要临时在 Parquet 与 MySQL 之间搬运数据的数据工程师参考。","reason":"这是一篇可复现的技术实践，展示了 ClickHouse 作为轻量数据搬运与联邦查询工具的用法，对处理 Parquet 到 MySQL 数据接入的工程师有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse","MySQL","AWS RDS"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":[]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-09-10T08:00:00+08:00","first_seen":"2026-09-12T05:00:12.168398+08:00","original_url":"https://clickhouse.com/blog/parquet-to-mysql-with-clickhouse","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"779a5a2e9b2e","zh_title":"目标变了：劳动力供给受限新时代的就业市场解读","zh_summary":"美国劳动力在2026年迄今减少约70万人，若第四季度无意外，将是1948年以来第五个劳动力萎缩的日历年，也是非衰退期第二次。2026年每月新增就业平均8万，失业率从1月4.3%降至8月4.1%。外国出生劳动力参与率下降、人口老龄化和女性劳动参与率上升解释了这一变化。文章指出失业率以劳动力为分母，退休或退出劳动力市场会直接降低失业率，因此需重新理解就业报告信号。","reason":"用数据分析解释劳动力供给收缩下的就业信号，帮助数据从业者理解宏观人才供给变化及其对组织与决策分析的影响。","category":"insight","category_label":"AI分析","vendors":["Indeed"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-09-10T18:00:00+08:00","first_seen":"2026-09-11T19:23:52.879136+08:00","original_url":"https://hiringlab.indeed.com/2026/09/10/interpreting-the-labor-market-in-a-new-era-of-constrained-labor-supply/","items":[{"source":"Indeed Hiring Lab"}],"source_badge":"RSS"},{"event_id":"9a7cfad4c8e4","zh_title":"“数据比模型重要”成共识，接下来拼什么？","zh_summary":"在上海一场约45分钟的闭门圆桌上，Snowflake全球产品总裁Christian Kleinerman、白鲸开源创始人郭炜等四位专家形成共识：模型能力趋同，企业AI瓶颈在数据层和语义表达。数据质量与语义一致性被指为跨层级共性瓶颈，模型层竞争让位于数据基础设施成熟度。郭炜以自建销售Agent失败为例，称数据散落在Salesforce、Confluence、微信、Slack等系统中；作者服务一百多家大型企业的体感是总部与区域数据口径难统一。作者判断，共识形成意味着早期认知红利结束，接下来要拼行业纵深与落地深度。","reason":"圆桌直接聚焦语义层、数据集成治理和企业AI落地瓶颈，并给出从认知红利转向行业纵深的判断，对数据平台与AI应用架构从业者有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake","白鲸开源"],"topics":["语义层","平台AI化"],"product_ids":[],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义"],"use_cases":["Agent构建","数据接入"],"decision_concerns":["准确性与语义一致性"]},"heat":29,"quality_score":64,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":64,"shelf":"evergreen","pinned":false,"published":"2026-09-11T19:23:52.879136+08:00","first_seen":"2026-09-11T19:23:52.879136+08:00","original_url":"https://www.infoq.cn/article/sT7izVmjw1YVxh3FQyK8?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"1ee284ef0f32","zh_title":"AI有了“工号”，数据平台长出“手”：Snowflake World Tour观察","zh_summary":"作者参加 Snowflake World Tour Shanghai，并结合与 Snowflake 全球产品总裁 Christian Kleinerman 的交流，总结出三个变化。其一，AI 实体开始获得 Agent Identity/Policy，支持细粒度权限、审计、预算与成本控制，像有了企业“工号”。其二，数据平台从记录世界走向执行行动，连接 Email、Slack、Documents、Repository、Salesforce 等系统。其三，Snowflake 加大开源投入，兼容 LangChain 等主流框架，推动企业级 AI 从概念走向生产化。","reason":"文章把 Agent 落地拆到身份、权限、审计、成本与行动执行等制度性能力，能帮助数据平台与 Agent 从业者判断企业级 AI 的生产化门槛。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["Data Agent","平台AI化"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理","Agent接口与工具"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["权限与安全","成本与性能"]},"heat":27,"quality_score":61,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":61,"shelf":"evergreen","pinned":false,"published":"2026-09-11T19:23:52.879136+08:00","first_seen":"2026-09-11T19:23:52.879136+08:00","original_url":"https://www.infoq.cn/article/RLdCKyW7YNb8ybDKlQ5d?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"90bb704f4579","zh_title":"2026腾讯云大数据年度精选技术实践指南","zh_summary":"标题为《2026腾讯云大数据年度精选技术实践指南》，呈现腾讯云面向大数据领域的年度技术实践内容。原文摘要仅显示“点击查看原文>”，未提供具体产品、案例、数字或技术主题。当前可见信息不足以提取更细的技术内容。","reason":"该指南直接涉及腾讯云大数据技术实践，属于数据平台与数据基础设施范畴，数据从业者可打开原文确认是否包含数仓、湖仓、实时分析或治理实践。","category":"platform","category_label":"AI 数据平台","vendors":["腾讯云"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":5,"quality_score":10,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":10,"shelf":"evergreen","pinned":false,"published":"2026-09-11T04:26:52+08:00","first_seen":"2026-09-11T19:23:52.879136+08:00","original_url":"https://www.infoq.cn/minibook/W2lxNULd8rJGsXWjEgMX?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"7f6d22a0733c","zh_title":"Hex：不必迁移300个仪表盘，应重估迁移策略","zh_summary":"Hex 在官方博客中讲述与一位数据负责人的对话：对方坚信必须把 300 个仪表盘从旧 BI 平台迁移到 Hex。作者认为真正有价值的是仪表盘里沉淀的指标定义与组织共识，筛选和下钻只是入口，用户真正想要的是提问后拿到可信答案。文章主张与其搬运全部仪表盘，不如投入精力整理上下文与数据，让 AI Agent 承担分析任务，并把仪表盘降级为只适用于特定场景的工具。","reason":"对正在做 BI 平台迁移或评估 AI 分析平台的数据团队，本文提供了一个关于“到底该迁移什么”的决策框架：迁移指标语义而非看板外壳。","category":"bi","category_label":"BI 与可视化","vendors":["Hex"],"topics":["BI变局","语义层"],"product_ids":["hex"],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","报表与可视化"],"use_cases":["指标问答","自助分析"],"decision_concerns":["准确性与语义一致性","用户采用与业务价值"]},"heat":18,"quality_score":41,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":41,"shelf":"evergreen","pinned":false,"published":"2026-09-10T08:00:00+08:00","first_seen":"2026-09-11T12:42:55.237907+08:00","original_url":"https://hex.tech/blog/dont-migrate-300-dashboards/","items":[{"source":"Hex Blog"}],"source_badge":"官网"},{"event_id":"d71cb00b889d","zh_title":"开放湖仓中跨引擎与目录的统一治理","zh_summary":"Databricks 这篇技术博客讨论开放湖仓愿景下，如何让治理策略在不同引擎和目录之间保持一致。文章聚焦 Apache Iceberg REST Catalog 近期推进的 read restrictions 与 catalog labels 两项能力，前者用于标准化委托给外部引擎的权限执行，后者用于让治理上下文跨目录可移植。文中还解释了集中式与委托式执行的区别，并提到 Unity Catalog 的 Cross-engine ABAC 如何通过 Iceberg REST catalog scan/plan API 对外部引擎访问进行过滤。最后讨论了这些能力的适用场景与未来创新机会。","reason":"数据平台和湖仓从业者可借此理解跨引擎治理、Iceberg REST Catalog 新规范以及 Unity Catalog 的开放治理实践，对设计权限与互操作架构有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","DuckDB"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["数据接入"],"decision_concerns":["权限与安全","可维护性与复用"]},"heat":40,"quality_score":80,"trend_score":7,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-09-10T23:05:10+08:00","first_seen":"2026-09-11T04:55:09.697299+08:00","original_url":"https://www.databricks.com/blog/unifying-governance-across-engines-and-catalogs-open-lakehouse","items":[{"source":"Databricks Blog"},{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"22e61cb37a9c","zh_title":"2026年AI与数据最佳书籍：数据与AI领导者书单","zh_summary":"ThoughtSpot 分析与 AI 卓越中心团队按书名首字母排序，发布 2026 年度十大 AI 与数据必读书单，并附轻松的推荐读物。书单首本《The Agentic AI Bible》由 Cindi Howson 点评，称其不含厂商立场，覆盖 MCP 协议、提示注入处理与沙箱等治理话题，兼顾领导者和工程师。文章还提到可收听 The Data & AI Chief 播客中三位作者的访谈，并回顾 2025 年书单。","reason":"对数据与 AI 从业者而言，这是一份由数据领域从业者筛选、带点评的年度阅读索引，可快速定位 agentic AI、AI 治理等方向的系统性读物。","category":"product","category_label":"数据产品","vendors":["ThoughtSpot"],"topics":["数据人"],"product_ids":["thoughtspot"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":19,"quality_score":42,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":42,"shelf":"evergreen","pinned":false,"published":"2026-09-10T18:35:49+08:00","first_seen":"2026-09-11T04:55:09.697299+08:00","original_url":"https://www.thoughtspot.com/blog/10-best-books-on-AI-and-data-2026","items":[{"source":"ThoughtSpot Blog"}],"source_badge":"RSS"},{"event_id":"2857d7b10179","zh_title":"CloudSearch 迁移至 OpenSearch Serverless 指南","zh_summary":"这篇 AWS 官方博客介绍如何把 Amazon CloudSearch 域迁移到 Amazon OpenSearch Serverless。文中先评估 CloudSearch 配置，再创建带显式索引映射的 OpenSearch Serverless collection，转换文档和查询、配置安全策略，并用 Amazon OpenSearch Ingestion 载入数据，最后在切换前验证迁移。文章强调 OpenSearch Serverless 的索引与搜索计算可独立扩展，collection 空闲时计算可缩容至零而存储仍需计费，并采用分层安全模型。适用前提包括 AWS 账户、已有 CloudSearch 域、S3 或 DynamoDB 中的源数据、IAM 权限和摄取管道。","reason":"对使用 AWS 搜索服务的数据团队，这是一份可直接照做的迁移实践，涵盖索引映射、数据摄取、安全策略与切换验证。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon CloudSearch","Amazon OpenSearch Serverless","Amazon S3","Amazon DynamoDB"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["权限与安全","成本与性能"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-09-11T00:06:42+08:00","first_seen":"2026-09-11T04:55:09.697299+08:00","original_url":"https://aws.amazon.com/blogs/big-data/how-to-migrate-from-amazon-cloudsearch-to-amazon-opensearch-serverless/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"2e9f871c967c","zh_title":"用 Iceberg 物化视图加速 Spark 查询","zh_summary":"AWS 官方博客介绍如何借助 Apache Iceberg 物化视图降低 Apache Spark 查询执行时间，且无需修改任何 SQL。自 Amazon EMR 7.12.0 和 AWS Glue 5.1 起，系统会自动分析查询逻辑计划，并与物化视图元数据缓存匹配；命中后改写计划读取 MV，未命中则保持原查询不变。该能力面向 BI 仪表盘、ISV 应用和遗留报表等难以手工重写 SQL 的分析负载。文章还对比了标准视图、自定义 ETL、手工重写等方案，并讨论不同 MV 形状的权衡。","reason":"数据湖仓与 Spark 查询优化从业者可关注：它说明了如何在不改 SQL 的情况下通过物化视图自动重写降低延迟与成本，并提示命中条件、正确性和 MV 设计取舍。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon EMR","AWS Glue","Apache Iceberg","Apache Spark"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["看板与报告"],"decision_concerns":["成本与性能","准确性与语义一致性"]},"heat":38,"quality_score":84,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":84,"shelf":"evergreen","pinned":false,"published":"2026-09-11T00:05:45+08:00","first_seen":"2026-09-11T04:55:09.697299+08:00","original_url":"https://aws.amazon.com/blogs/big-data/accelerating-spark-queries-with-iceberg-materialized-views/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"1acb63d9b8cf","zh_title":"Snowflake数据平台上的财务：现金应用自动化","zh_summary":"Snowflake官方博客首次展示其CFO办公室如何将现金应用从多日手工流程变为当日自动化且可审计的流程，每月回收250+小时。文章主张财务各团队（FP&A、会计、资金、催收、对账等）运行在单一受治理数据平台上，消除系统间数据搬运和副本，使报告与自动化使用同一份数据。文中以银行流水、未结发票匹配、ERP入账等环节为例，说明现金应用如何从滞后指标变为实时运营信号。","reason":"该案例把数据平台直接落到财务运营，包含具体流程改造和量化收益，能帮助数据从业者理解受治理平台如何支撑自动化与实时决策。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["财务经营","实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["生产评估与运营"],"decision_concerns":["准确性与语义一致性","用户采用与业务价值"]},"heat":30,"quality_score":66,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":66,"shelf":"evergreen","pinned":false,"published":"2026-09-10T22:01:05+08:00","first_seen":"2026-09-11T04:55:09.697299+08:00","original_url":"https://medium.com/snowflake/what-does-finance-look-like-when-it-runs-on-snowflakes-data-platform-2529ef2c3b2a?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"29786a87453c","zh_title":"企业级AI最大误判：把部署Agent当成组织智能","zh_summary":"爱分析对话爱化身科技CTO郭林，讨论企业级AI为何不能把部署个人Agent等同于组织智能。郭林认为，当前多数Agent仍依附员工身份、权限和指令，主要解决个人提效；企业需要本体定义业务对象、关系、规则和语义，并用世界行为模型推演业务状态变化。再通过Agent集群把推演和决策转化为任务与行动，在身份、权限和治理边界下协同，并涉及FDE交付模式与未来竞争格局。企业长期积累的数据、业务知识和组织经验将决定企业智能竞争基础。","reason":"文章把企业级AI落地拆到语义本体、世界行为模型、Agent集群与治理调度，提醒数据从业者：组织级AI的关键在数据与语义基础设施，而非单纯堆模型或Agent。","category":"platform","category_label":"AI 数据平台","vendors":[],"topics":["平台AI化","语义层"],"product_ids":[],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","权限与治理"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["准确性与语义一致性","权限与安全"]},"heat":27,"quality_score":61,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":61,"shelf":"evergreen","pinned":false,"published":null,"first_seen":"2026-09-10T19:20:49.426641+08:00","original_url":"https://www.ifenxi.com/research/content/6936","items":[{"source":"爱分析"}],"source_badge":"RSS"},{"event_id":"03d840633827","zh_title":"企业AI热词“本体”：是什么、为何火、怎么落地","zh_summary":"文章解释企业AI中的“本体”是一套描述业务概念、关系、属性和规则的方法，正成为Agent理解业务的关键基础设施。它对比了本体与知识图谱、ER图的差异，指出本体负责定义业务对象及其关系，而知识图谱组织实体关系、ER图描述数据存储。文章认为，当AI从问答走向任务执行时，需要本体提供业务全貌，避免AI只读到碎片化信息而产生偏差。","reason":"数据从业者可将本体视为语义层与知识上下文的基础设施，理解其与知识图谱、ER图的分工，有助于设计更可靠的Data Agent和企业AI数据平台。","category":"platform","category_label":"AI 数据平台","vendors":[],"topics":["语义层","平台AI化"],"product_ids":[],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","指标与语义"],"use_cases":["Agent构建"],"decision_concerns":["准确性与语义一致性"]},"heat":18,"quality_score":41,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":41,"shelf":"evergreen","pinned":false,"published":"2026-09-10T10:53:27+08:00","first_seen":"2026-09-10T12:44:57.688858+08:00","original_url":"https://www.woshipm.com/ai/6462587.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"1473b9be1e21","zh_title":"面向 Agent 开发的数据库新范式 | 腾讯云数据库 DBTalk","zh_summary":"腾讯云数据库 DBTalk 发布主题为“面向 Agent 开发的数据库新范式”的内容。当前摘要仅显示“点击查看原文>”，未披露具体产品、架构、数据或案例细节。若该内容讨论数据库如何支撑 Agent 开发，可能属于 AI 数据平台与 Agent 基础设施方向。由于原文信息有限，暂无法提炼具体发现或行动建议。","reason":"数据库如何适配 Agent 开发是数据平台与 Data Agent 基础设施的重要方向，数据从业者可关注腾讯云数据库的架构与实践思路。","category":"platform","category_label":"AI 数据平台","vendors":["腾讯云数据库"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"ai-platform","label":"AI 数据平台","priority":1,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["Agent构建"],"decision_concerns":[]},"heat":7,"quality_score":15,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":15,"shelf":"evergreen","pinned":false,"published":"2026-09-10T02:17:24+08:00","first_seen":"2026-09-10T12:44:57.688858+08:00","original_url":"https://www.infoq.cn/video/xXRz8UJAdS3S51AqOchf?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"880cf15dc545","zh_title":"Snowflake App Runtime 上的 Node.js AI 文档智能","zh_summary":"该实践在 Snowflake App Runtime 上原生托管 Node.js/Next.js 应用，无需外部基础设施，并用 Snowflake Marketplace 的零拷贝公共数据（BLS 就业与价格、Census 房地产、FHFA 房价等）构建 AI 文档智能。数据层通过 ontology 把原始时间序列整理为含 Geography 维度（166K 行）和五张事实表的 AI-ready 数据基础，关键表 FACT_ESCALATION_SIGNALS 用 LAG() 计算各州工资-CPI 同比缺口。Cortex AI Suite 提供 AI_PARSE_DOCUMENT、Cortex Complete、Cortex Search、Cortex Analyst 与 Cortex Agent，覆盖文档解析、LLM 推理、向量搜索、自然语言转 SQL 和基于事实的问答。开发按数据发现、数据基础验证、叠加 AI 服务、在 App Runtime 部署空白 Node.js 应用并逐项加功能的阶段推进。","reason":"展示了如何把 Snowflake App Runtime、Marketplace 零拷贝数据、ontology 语义层和 Cortex AI 串成可复用的文档智能/问答架构，对在数仓内构建 AI 应用和数据基础有直接参考。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["平台AI化","语义层"],"product_ids":["snowflake-cortex"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","知识与上下文"],"use_cases":["数据接入","Agent构建"],"decision_concerns":["可维护性与复用","准确性与语义一致性"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-09-10T09:11:39+08:00","first_seen":"2026-09-10T12:44:57.688858+08:00","original_url":"https://medium.com/snowflake/ai-document-intelligence-using-node-js-on-snowflake-app-runtime-4f151b11056b?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"c8aeffe2b296","zh_title":"金融服务领导者正在问的五大AI信任与治理问题","zh_summary":"文章指出，金融业对AI的焦点已从“AI是否有效”转向“AI能否赢得信任”。Grant Thornton调查显示，50%的银行高管认为治理与合规正在限制AI表现，仅18%有信心通过独立AI控制审计；Economist Enterprise研究也发现，不足一半的组织对自治系统正式要求治理框架。Databricks将在Sibos Miami上展示可审计对账、释放监管资本等实践，并给出CFO、合规官最应追问的五个问题。","reason":"数据从业者可借此了解金融机构AI落地中的治理、信任与可审计需求，以及如何将数据平台能力对准这些业务场景。","category":"insight","category_label":"AI分析","vendors":["Databricks"],"topics":["财务经营","风险管理"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":[],"decision_concerns":["可靠性与评估"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-09-10T02:09:29+08:00","first_seen":"2026-09-10T04:59:07.620001+08:00","original_url":"https://www.databricks.com/blog/five-ai-questions-were-hearing-financial-services-leaders","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"ab586bc5d470","zh_title":"Databricks 参考模式：嵌入式 AI/BI 仪表盘的逐行安全授权","zh_summary":"Databricks 发布技术参考，介绍在客户面向应用中嵌入 AI/BI Dashboard 后如何实现细粒度行级授权。它结合 __aibi_external_value、Unity Catalog 行过滤与列掩码，以及从 IdP（如 Okta/Entra ID）同步的用户组，用一张统一的 entitlements 权限表管住访问规则。示例中，同一张 Open AR Tasks 仪表盘覆盖 West/East/Central 三个区域：外部合作伙伴 Acme Ops 仅能看到 West 区域且邮箱被掩码，Finance 用户组则能看到全部三区域完整数据。该方案同时覆盖嵌入式仪表盘访问和 Databricks 用户直接执行 SQL 两条路径。","reason":"嵌入式 BI 的核心难题是让不同查看方看到各自数据行；文章给出了基于 Unity Catalog 的统一授权参考模式，可作为多租户嵌入场景的落地依据。","category":"bi","category_label":"BI 与可视化","vendors":["Databricks"],"topics":[],"product_ids":[],"focus":{"id":"ai-dashboard","label":"AI 看板","priority":4,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化","权限与治理"],"use_cases":["方案封装与分发"],"decision_concerns":["权限与安全"]},"heat":38,"quality_score":85,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-09-09T22:04:44+08:00","first_seen":"2026-09-10T04:59:07.620001+08:00","original_url":"https://www.databricks.com/blog/beyond-embedding-how-secure-aibi-dashboards-every-viewer","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"89845bea3750","zh_title":"Consort：分支数据库上的测试驱动开发","zh_summary":"本文作者回顾25年软件开发实践，探讨如何用 Lakebase Postgres 的分支数据库实现测试驱动开发。通过写时复制分支，开发者可在内循环中用真实数据库运行测试，免去 mock 和共享环境的负担。schema 随版本化迁移与代码一起作为一个单元演进，破坏性测试也能安全进行。文章介绍了从传统数据库工作流向数据库分支开发模式转变的方法。","reason":"数据库分支能让开发测试基于真实数据而非 mock，对数据平台工程和研发流程改进有直接借鉴价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","Lakebase"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":[],"decision_concerns":["可靠性与评估"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-09-09T21:41:25+08:00","first_seen":"2026-09-10T04:59:07.620001+08:00","original_url":"https://www.databricks.com/blog/introducing-consort-test-driven-development-branching-database","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"26d202fd3489","zh_title":"3.7星掩盖的安全危机：四步将98条评论变成安全情报应用","zh_summary":"Snowflake与Hex作者使用Snowflake Cortex AI Functions和Hex，将GE Profile Opal 2.0制冰机的98条亚马逊评论构建为发布版安全情报应用。分析发现，虽然该产品总评3.7星且不乏热情好评，但评论中同时存在黑霉滋生、BBB投诉等严重安全问题。文章指出平均星值无法反映这类两极分化产品，真正需要关注的是具体失败模式、出现频率与是否恶化。整个过程通过四个提示词在一次笔记本会话中完成，用时不到20分钟。","reason":"该案例展示了如何用AI从非结构化评论中提取平均分掩盖的安全风险信号，对产品安全监控与客户反馈分析场景有直接借鉴价值。","category":"insight","category_label":"AI分析","vendors":["Snowflake","Hex"],"topics":["风险管理"],"product_ids":["hex"],"focus":{"id":"ai-platform","label":"AI 数据平台","priority":1,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案"],"use_cases":["Agent构建","方案封装与分发"],"decision_concerns":[]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-09-09T22:01:05+08:00","first_seen":"2026-09-10T04:59:07.620001+08:00","original_url":"https://medium.com/snowflake/what-3-7-stars-wont-tell-you-fcaa1c7058b2?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"89da9115d842","zh_title":"Hex：AI 数据蔓延——谁为无数无法追踪的分析代码负责？","zh_summary":"Hex 发文指出，AI 让大量非技术人员能用自然语言生成查询、报表乃至应用，但这些代码基于随机上下文、权限松散，散落在聊天记录、HTML 和本地文件中，无人审查、无法追踪、无法复现。文章认为，答案是否正确无从验证，传统 BI 工具靠加一个聊天框无法解决，数据平台团队正面临放弃治理或锁死能力的艰难选择。该文提出“AI 数据蔓延”这一现象，并指向数据治理与可观测性漏洞。","reason":"对数据平台和 BI 选型是个重要提醒：AI 生成分析代码的治理与可观测性尚未被解决，数据团队需要为此设计新的管控机制。","category":"platform","category_label":"AI 数据平台","vendors":["Hex"],"topics":["平台AI化"],"product_ids":["hex"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["自助分析"],"decision_concerns":["准确性与语义一致性","权限与安全"]},"heat":24,"quality_score":53,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":53,"shelf":"evergreen","pinned":false,"published":"2026-09-09T08:00:00+08:00","first_seen":"2026-09-10T04:59:07.620001+08:00","original_url":"https://hex.tech/blog/ai-data-sprawl/","items":[{"source":"Hex Blog"}],"source_badge":"官网"},{"event_id":"025d7e1e4c9f","zh_title":"Zepto在Databricks和MLflow上以评估优先构建客服AI Agent","zh_summary":"Zepto是印度覆盖60多个城市的快商务平台，其多Agent客服系统每天处理超过10万张工单。为应对规模增长与品类扩张带来的可靠性挑战，Zepto与Databricks合作，将评估作为Agent开发、测试和运营的核心环节。文章介绍了系统架构、基于MLflow的评估框架，以及在生产环境中发现隐性错误、平衡成本与性能的实践。","reason":"数据从业者可借鉴其在大规模生产环境中用评估机制驱动Agent可靠性的方法，对Agent落地和运营有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-09-09T11:00:00+08:00","first_seen":"2026-09-09T12:43:31.256989+08:00","original_url":"https://www.databricks.com/blog/evaluation-first-ai-agents-how-zepto-scales-customer-support-databricks-and-mlflow","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"d94c3328a3f2","zh_title":"SQL数据类型参考与最佳实践","zh_summary":"SQL数据类型是定义表中列可存值及其存储空间的基础规范，直接影响数据完整性、存储效率与查询性能。文章将SQL数据类型划分为数值、字符、日期时间和二进制等类别，并介绍MySQL、PostgreSQL、SQL Server和Oracle等主流数据库在命名与精度上的差异。同时提供了为不同用例选择合适数据类型的实践建议，帮助数据从业者规避慢查询和存储浪费问题。","reason":"数据从业者在设计表结构和数据管道时都需面对数据类型选择，理解跨数据库差异和最佳实践有助于提升存储效率与查询性能。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","MySQL","PostgreSQL","SQL Server","Oracle"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":16,"quality_score":36,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":36,"shelf":"evergreen","pinned":false,"published":"2026-09-09T01:16:06+08:00","first_seen":"2026-09-09T05:12:13.228415+08:00","original_url":"https://www.databricks.com/blog/sql-data-types","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"e54258012cf5","zh_title":"用Temporal和Lakebase构建持久化数据Agent的参考实现","zh_summary":"Databricks 展示了如何用 Temporal 与 Lakebase 构建持久化数据 Agent，并以个人贷款承销为例。该 Agent 可跨工作进程和容器存活，处理重试、长时间等待和故障恢复。Temporal 负责持久化控制流状态，Lakebase Postgres 存储证据与决策，并通过 Change Data Feed 与 Unity Catalog 同步。整个方案满足了恢复、重试、长等待、运维可见、运行时治理和审计六项要求。","reason":"对构建可恢复、可治理的生产级 Data Agent 给出了具体架构与实现思路，值得做 Agent 工程化的团队参考。","category":"agent","category_label":"Data Agent","vendors":["Databricks","Temporal"],"topics":["Data Agent","风险管理"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案","权限与治理"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","权限与安全"]},"heat":34,"quality_score":76,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":76,"shelf":"evergreen","pinned":false,"published":"2026-09-08T23:46:40+08:00","first_seen":"2026-09-09T05:12:13.228415+08:00","original_url":"https://www.databricks.com/blog/build-durable-agents-temporal-and-lakebase","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"0ae0d3b4c0b0","zh_title":"40年数据库规则被Agent打破：LTAP统一OLTP与OLAP负载","zh_summary":"Jonathan Katz认为，AI Agent基于延迟几分钟或几小时的批处理副本做判断，会让欺诈检测失效——信用卡交易往往在数百毫秒内完成，等旧副本追上时交易已通过。若Agent直接查询运营系统，扫描客户完整购买历史这类分析负载又可能拖慢在线交易；多个Agent并发且没有负载治理时，系统会被压垮。Databricks的LTAP思路是在湖仓上利用统一Catalog把权限与一致策略延伸到运营数据，避免运营系统重新变成数据孤岛。","reason":"当Data Agent要参与实时决策，“先同步到数仓再分析”的旧链路会产生延迟错误，而直连OLTP又带来性能风险。本文用LTAP和湖仓统一目录给出兼顾实时读取、负载治理与权限控制的路径，值得数据平台与Agent建设者参考。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["湖仓","Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":[],"decision_concerns":["准确性与语义一致性","成本与性能"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-09-07T20:48:05+08:00","first_seen":"2026-09-09T05:12:13.228415+08:00","original_url":"https://www.databricks.com/blog/40-year-old-database-rule-agents-just-broke-how-ltap-unifies-oltp-and-olap-workloads","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"25f0fe575038","zh_title":"AWS助力Sony LIV构建实时视频流分析","zh_summary":"Sony LIV在AWS上构建了实时流媒体分析解决方案，使用Amazon Kinesis Data Streams进行亚秒级事件接入，Amazon Data Firehose可靠投递数据，Amazon EMR配合Apache Spark进行批处理和微批处理，并以Apache Iceberg在S3上构建ACID合规的湖表。该方案在亚洲杯等直播场景中成功处理了数百万并发会话，并支撑从实时互动指标到历史趋势分析的可扩展洞察。","reason":"该文展示了利用Kinesis、EMR、Iceberg等组件搭建实时数据管道的完整方法，对面向高并发业务的数据平台架构设计有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":["实时分析","湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-09-09T00:43:05+08:00","first_seen":"2026-09-09T05:12:13.228415+08:00","original_url":"https://aws.amazon.com/blogs/big-data/how-sony-liv-built-real-time-video-streaming-analytics-with-aws/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"425da12da7dc","zh_title":"超越集中化：亚太零售与CPG团队为何需要dbt","zh_summary":"Fivetran博客指出，集中化数据只是基础，零售和CPG团队需通过dbt测试、治理和血缘追踪来获得可信数据。亚太市场数据来源混杂，自动化补货、促销和库存决策依赖底层数据质量。dbt通过自动运行的not_null、unique等测试，在数据驱动关键决策前暴露坏数据，避免错误补货和缺货损失。","reason":"数据从业者可从中理解dbt如何作为数据信任层，在复杂业务场景下保障AI代理和自动化决策的数据质量。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran","dbt"],"topics":[],"product_ids":["dbt"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["生产评估与运营"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":23,"quality_score":51,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":51,"shelf":"evergreen","pinned":false,"published":"2026-09-09T02:55:26+08:00","first_seen":"2026-09-09T05:12:13.228415+08:00","original_url":"https://www.fivetran.com/blog/beyond-centralization-why-apac-retail-and-cpg-teams-need-dbt","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"f3046d6c1fb6","zh_title":"自动化集成+云数仓+BI：电商分析如何摆脱手工报表","zh_summary":"文章指出，成长型电商分析真正的瓶颈不是缺少数据，而是数据分散在Shopify、Google Analytics、广告平台、财务系统、订阅工具和运营数据库中，导致渠道价值、真实获客成本、复购概率等问题难以回答。作者认为，不需要组建庞大的数据工程团队；通过自动化数据集成、云数据仓库和BI工具，就能以可扩展方式取代电子表格和脆弱定制管道为主的手工分析。","reason":"电商是典型的跨数据源分析场景，数据团队可将这套“集成+数仓+BI”的轻量化架构思路复用到其他业务线，也可据此判断厂商方案是否真正覆盖口径一致性问题。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran"],"topics":["客户运营","销售增长"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":11,"quality_score":24,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":24,"shelf":"evergreen","pinned":false,"published":"2026-09-09T02:45:05+08:00","first_seen":"2026-09-09T05:12:13.228415+08:00","original_url":"https://www.fivetran.com/blog/how-to-solve-ecommerce-analytics-without-manual-reporting","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"7c8800d1b37a","zh_title":"一年前在Snowflake上配OpenAI做聊天机器人，如今我会改用原生AI栈","zh_summary":"作者回顾约一年前发布的一篇教程：在 Snowflake 上用 Streamlit 界面、Snowpark 访问仓库数据，并通过公网调用 OpenAI GPT-3.5 来实现聊天机器人。当时该方案需要 Snowflake 账户、OpenAI API Key 和企业出站网络允许三项前提，严格出口管控下仅网络审查就可能拖到数周；作者也一直担心数据或摘要跨出 Snowflake 边界再返回带来的安全和合规问题。现在他给出的对比结论是：聊天机器人本身没变聪明，但在 Snowflake 原生 AI 栈上，模型与数据之间的物理距离大幅缩短，同类用例不再需要把数据带到外部模型。文章用一个经典场景解释了为何外部 API 方案逐渐让位于数据平台内 AI 能力。","reason":"数据从业者可从中看到聊天机器人架构如何从外挂AI转向数据平台原生AI，尤其是企业敏感数据场景下数据出域与安全审查的真实约束。","category":"agent","category_label":"Data Agent","vendors":["Snowflake","OpenAI"],"topics":[],"product_ids":[],"focus":{"id":"ai-platform","label":"AI 数据平台","priority":1,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["权限与安全"]},"heat":33,"quality_score":74,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"evergreen","pinned":false,"published":"2026-09-09T03:01:01+08:00","first_seen":"2026-09-09T05:12:13.228415+08:00","original_url":"https://medium.com/snowflake/the-chatbot-i-built-with-openai-in-2025-and-why-i-wouldnt-build-it-that-way-today-801e90899fcf?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"c5db01d12b78","zh_title":"专家经验批量变AI数据：专访本原智数李逆勇","zh_summary":"爱分析与本原智数创始人李逆勇对话，围绕数据定义权、专家经验规模化、企业AI落地分工和具身数据路线展开。文中指出，数据公司的毛利率可低于20%或超过80%，差距在于定位为按规则加工的施工队还是能诊断模型短板的数据顾问。本原智数已推出原测、原识、原智、原物四个平台，覆盖模型评测、专家数据生产、智能体落地和具身数据服务；李逆勇认为，未来最值钱的交付物不是一批数据，而是对数据的判断。","reason":"数据资产的价值正从“按规则交付”转向“判断模型缺什么数据”，这篇文章用一线公司的业务拆分给出了数据服务分层与AI数据工程判断框架，值得数据从业者参考。","category":"product","category_label":"数据产品","vendors":["本原智数"],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","知识与上下文"],"use_cases":["生产评估与运营","Agent构建"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":null,"first_seen":"2026-09-09T00:40:17.419505+08:00","original_url":"https://www.ifenxi.com/research/content/6932","items":[{"source":"爱分析"}],"source_badge":"RSS"},{"event_id":"2dc4de112d3d","zh_title":"MCP Toolbox：如何将Agent文本转为ClickHouse向量","zh_summary":"Google 开源 MCP Toolbox for Databases 将 Agent 文本与数据库向量检索之间的转换内置到工具中，你只需在 YAML 中声明 Gemini embedding 模型，插入和搜索时嵌入与 ClickHouse 排序即可透明完成，无需自建嵌入服务。文章以 Toolbox 1.9.0 和 ClickHouse Cloud 26.4.1 为例，演示了从安装配置到自定义 ingestion/search 工具、再到加载语料验证结果的完整链路。","reason":"该实操展示了一种可复用的 Agent 语义检索构建方式，减少手写文本转 SQL/向量的胶水代码，对 Data Agent 工程落地有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["ClickHouse","Google"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["可维护性与复用"]},"heat":45,"quality_score":99,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":99,"shelf":"evergreen","pinned":false,"published":"2026-09-07T17:00:00+08:00","first_seen":"2026-09-08T05:33:50.027187+08:00","original_url":"https://clickhouse.com/blog/mcp-toolbox-clickhouse-vectors","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"c3d67ea96518","zh_title":"“薄 Agent Loop，厚 Control Plane”：TiDB 用数据库思维重做 Harness","zh_summary":"TiDB 团队启动了一项名为 TiDB Cloud Filesystem 的 Agent 基础设施尝试，将 Workspace 从 Session 和 Sandbox 的生命周期中独立出来，提供数据库级持久化、版本、分支、回滚与权限控制，目前已承载超过数百万个 Agent Workspace。他们没有从零编写 Agent Loop，而是基于开源项目 Pi 完成最内层核心，重点自研任务编排、权限、Sandbox、持久状态和失败恢复。唐刘将这一设计哲学概括为“薄 Agent Loop，厚 Control Plane”，并强调 Agent Framework 可以变化，但状态、权限和副作用边界必须稳定。此篇专访还提出了“Fail Fast 比 Retry 更重要”“多 Agent 应通过状态共享而非消息广播协作”等观点。","reason":"数据从业者构建可信、可运维的 Data Agent 时，最缺的正是状态、权限、失败恢复等控制面设计；TiDB 从数据库可靠性哲学出发的经验极具参考价值。","category":"agent","category_label":"Data Agent","vendors":["TiDB"],"topics":["Data Agent","平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理","Agent接口与工具"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","权限与安全"]},"heat":38,"quality_score":85,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-09-08T00:10:35+08:00","first_seen":"2026-09-08T05:33:50.027187+08:00","original_url":"https://www.infoq.cn/article/38uc758e24YV4LUpAs77?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"72abdeca2f43","zh_title":"Ossie会成为“开源Palantir”的起点吗？","zh_summary":"文章围绕 Apache Ossie（前身 OSI）的最新变化：其本体规范已加入业务概念、关系和业务规则，路线图计划在逻辑/物理模型之上建立 Customer、Order、Product 等业务概念。作者认为 Ossie 正从语义交换走向“企业世界模型”，未来 3～5 年可能与开源项目组成 Open Palantir Stack；但 Palantir 真正的壁垒是把本体运行起来，涉及权限一致、数据同步和审计工作流等企业级能力。","reason":"数据从业者可借此理解语义层与本体论的边界：Ossie 作为中立标准正在扩展业务概念，很可能影响未来语义层/数据平台架构和 Agent 对数据的理解方式。","category":"platform","category_label":"AI 数据平台","vendors":["Aloudata","Palantir","RelationalAI"],"topics":["语义层"],"product_ids":[],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义"],"use_cases":[],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-09-07T16:37:31+08:00","first_seen":"2026-09-07T20:34:46.525416+08:00","original_url":"https://aloudata.com/blogs/ossie-open-source-palantir-start","items":[{"source":"Aloudata 博客"}],"source_badge":"官网"},{"event_id":"373235bebbaa","zh_title":"用ClickHouse和Massive构建实时市场数据应用","zh_summary":"本文介绍如何使用ClickHouse与Massive（原Polygon.io）构建可扩展至每秒数千事件的实时金融行情应用。文中解释了tick、quote、trade等概念，并演示了如何接入行情流、写入ClickHouse、利用物化视图预聚合，以及用Node.js和React实现实时可视化。","reason":"实时行情是典型的高频流分析场景，本文给出了从数据接入、存储到可视化的完整技术路径，对数据从业者构建低延迟分析应用有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse","Massive"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["数据接入","看板与报告"],"decision_concerns":["成本与性能"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-09-04T08:00:00+08:00","first_seen":"2026-09-07T20:34:46.525416+08:00","original_url":"https://clickhouse.com/blog/build-a-real-time-market-data-app-with-clickhouse-and-polygonio","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"01bf8edae61d","zh_title":"用实验简报设计更好的实验","zh_summary":"本文提出在开展实验前先撰写实验简报，以提升实验设计质量。简报需记录引发实验的定量、定性或竞争性观察，明确实验类型是假设检验还是无害测试，并结构化描述假设：观察到什么、引入或修改哪个变量、预期行为变化及对结果指标的影响。该方法适用于数据驱动型产品团队和增长实验。","reason":"实验是数据驱动决策的核心环节，原文提供了一套可复用的实验设计模板，帮助数据从业者减少随意实验、提升评估严谨性。","category":"product","category_label":"数据产品","vendors":[],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["可靠性与评估"]},"heat":26,"quality_score":58,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":58,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:08+08:00","first_seen":"2026-09-07T04:26:22.459764+08:00","original_url":"https://amplitude.com/blog/experiment-brief","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"d08baffbd722","zh_title":"事件驱动架构是产品分析的必要非充分条件","zh_summary":"数字分析行业正围绕事件驱动数据架构收敛：Amplitude等产品分析厂商率先采用，Google和Adobe分别通过GA4和CJA/AEP向事件模型迁移。作者认为统一架构让组织更易比较不同分析工具的结果并迁移供应商，但指出只有事件架构不等于能做产品分析。事件驱动是产品分析的底层基础，是否具备产品分析能力仍要看对业务问题的解析和差异化的分析设计。","reason":"帮助数据从业者在架构选型和工具迁移阶段避免“买了事件架构就算产品分析”的误区，也点明了分析工具底层架构收敛带来的机会与边界。","category":"bi","category_label":"BI 与可视化","vendors":["Google","Adobe","Amplitude"],"topics":["BI变局"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":[],"decision_concerns":["可维护性与复用"]},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:08+08:00","first_seen":"2026-09-06T12:40:35.990865+08:00","original_url":"https://amplitude.com/blog/event-based-prodanalytics","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"121742439778","zh_title":"默认提示词正在拖累你的Agent留存率","zh_summary":"针对 Global Agent 的留存分析发现，首周发送过两条及以上消息的用户，留存率是仅发送一条消息用户的 2.5 倍。文章认为，对 Agent 而言真正的激活行为不是首次发送，而是用户是否愿意继续发送第二条消息；第二条消息率低往往意味着首次回复没有命中。造成这一问题的主要元凶是默认提示词：超过半数新用户从同一个默认提示词开始，而它没能有效引导第二次消息。作者建议构建 Agent 的团队审计默认提示词和首次体验，并给出了对应的数据与优化思路。","reason":"对数据/AI Agent 产品团队有直接借鉴意义：激活指标应从首次消息转向第二次消息，并用数据说明默认提示词是影响留存的关键抓手。","category":"insight","category_label":"AI分析","vendors":[],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["用户采用与业务价值"]},"heat":36,"quality_score":79,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":79,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:08+08:00","first_seen":"2026-09-05T23:16:14.673098+08:00","original_url":"https://amplitude.com/blog/default-prompts-agent-retention","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"883e8310f9a4","zh_title":"AI Agent的联邦数据访问：打破企业数据孤岛","zh_summary":"企业数据分散在Amazon S3批量存储、Amazon Kinesis实时流和CRM等SaaS应用中，各有独立访问方式与认证模型，导致只有数据工程师能操作，业务人员只能通过工单获取滞后报表。文章以流媒体公司为例，展示跨系统回答订阅增长、营销相关性等问题时的双重挑战：数据孤岛和访问鸿沟。作者提出联邦数据访问模式，让AI Agent直接在原系统上访问数据，避免集中式数据湖或数据网格的高昂工程投入。","reason":"为构建跨系统数据访问的Agent提供了一种可参考的架构思路，直接关系到Data Agent落地的连接与治理问题。","category":"agent","category_label":"Data Agent","vendors":["AWS"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["数据接入"],"decision_concerns":["权限与安全"]},"heat":32,"quality_score":71,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":71,"shelf":"evergreen","pinned":false,"published":"2026-09-05T05:35:21+08:00","first_seen":"2026-09-05T08:50:04.483271+08:00","original_url":"https://aws.amazon.com/blogs/big-data/from-silos-to-insights-federated-data-access-patterns-for-ai-agents/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"b61e19f27b42","zh_title":"在Snowflake上实现真正的数据层治理","zh_summary":"本文介绍应用通过服务账号查询Snowflake时，容易形成与应用层并行的第二套权限模型。作者提出使用继承的调用者授权（inherited caller grants），在Streamlit和React/Next.js应用（基于SPCS）中启用调用者权限，让用户现有的Snowflake行级访问策略和脱敏策略自动生效。数据团队只需在数据层定义一次治理模型，即可覆盖所有外部应用，避免额外创建角色和重复授权。","reason":"展示了如何将应用层权限收敛回数据层统一治理，对使用Snowflake构建数据应用或BI前端的团队有直接借鉴价值。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":[],"decision_concerns":["权限与安全","可维护性与复用"]},"heat":38,"quality_score":84,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":84,"shelf":"evergreen","pinned":false,"published":"2026-09-05T03:01:01+08:00","first_seen":"2026-09-05T08:50:04.483271+08:00","original_url":"https://medium.com/snowflake/implementing-true-data-layer-governance-on-snowflake-3473b84d3f48?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"39da2eb43096","zh_title":"当你无法信任自己的数据时会发生什么？","zh_summary":"许多公司投入数十万美元购买自助分析工具，但流入工具的数据却未必可信。文章指出，数据使用者每次遇到数据质量问题都会削弱对数据的信任，最终可能放弃数据、依赖直觉决策。作者建议在源头清洗数据，避免脏数据进入数仓，并指出根因在于团队激励重发布、轻度量，分析和采集团队彼此割裂。文末强调高效组织应专注结果而非交付量。","reason":"数据信任直接决定BI与数据平台能否产生价值，文章点出数据治理失效的典型循环与根因，能帮助企业避免工具投入打水漂。","category":"product","category_label":"数据产品","vendors":[],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["自助分析"],"decision_concerns":["准确性与语义一致性"]},"heat":24,"quality_score":53,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":53,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:08+08:00","first_seen":"2026-09-05T08:50:04.483271+08:00","original_url":"https://amplitude.com/blog/data-trust","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"4a741d5c9e08","zh_title":"Yahoo用Flexible VMs与Auto-Zone保障Spark集群持续运行","zh_summary":"Yahoo运行着支撑数亿用户的大型数据分析基础设施，其Spark工作负载必须持续高速运行。在Managed Service for Apache Spark（原Dataproc）中，Yahoo通过配置可接受VM规格的排名列表并结合Auto-Zone，让集群自动应对区域容量不足，避免关键数据管道阻塞。该实践基于Yahoo将本地Hadoop和大数据平台迁移到Google Cloud的现代化改造，为大规模批处理和流式分析提供了动态资源灵活性。","reason":"该案例展示了用灵活VM配置应对云区域容量瓶颈的工程思路，对需要保障关键Spark管线稳定运行的团队有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Google","Google Cloud"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估"]},"heat":33,"quality_score":74,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"evergreen","pinned":false,"published":"2026-09-04T08:00:00+08:00","first_seen":"2026-09-05T08:50:04.483271+08:00","original_url":"https://cloud.google.com/blog/products/data-analytics/how-yahoo-optimizes-apache-spark-with-flexible-vms","items":[{"source":"Google Cloud Data Analytics Blog"}],"source_badge":"RSS"},{"event_id":"2735f617dc71","zh_title":"MySQL AI三义辨析：Serverless MySQL作为AI Agent统一后端","zh_summary":"文章区分了“MySQL AI”的三种含义：AI辅助SQL、MySQL产品内置AI功能、以及MySQL作为AI Agent后端；其中第三种才是决定架构的选择。Agent需要持久化六类数据，其中五类仍依赖事务和精确过滤，新增的是embedding向量；社区版和商业版MySQL可存储向量但不能比较向量，DISTANCE()仅由HeatWave/MySQL AI提供。作者认为对应用团队而言，MySQL AI意味着用MySQL兼容后端统一存放Agent记忆、工具输出、embedding与持久化状态，并能同一查询内同时做向量检索和SQL，从而消除分离式架构的同步问题；Serverless形态可避免手动分片与运维。","reason":"数据从业者为Agent做存储和记忆层选型时，常混淆SQL辅助、数据库AI功能和应用后端这三种“MySQL AI”；本文清晰讲清事务、向量与服务化取舍，值得直接参考。","category":"platform","category_label":"AI 数据平台","vendors":["PingCAP","TiDB","Oracle"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["可维护性与复用","成本与性能"]},"heat":38,"quality_score":85,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-09-04T05:05:13+08:00","first_seen":"2026-09-05T08:50:04.483271+08:00","original_url":"https://www.pingcap.com/blog/mysql-ai/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"7bcb449b109d","zh_title":"什么是Serverless数据库？为何对现代AI应用重要","zh_summary":"Serverless数据库将计算与存储解耦，自动伸缩容量并按实际用量计费，团队无需预置实例或做容量规划。托管服务通常仍需选择实例规格，而Serverless自己决定容量。突发推理流量和空闲开发周期使AI工作负载非常适合Serverless。但需注意冷启动、无成本上限、始终高负载等不适合场景。","reason":"文章厘清Serverless数据库的定义与架构，并给出适用/不适用场景，帮助数据从业者评估AI应用的数据基础设施选型。","category":"platform","category_label":"AI 数据平台","vendors":["PingCAP","TiDB"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["成本与性能"]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-09-02T04:10:00+08:00","first_seen":"2026-09-05T08:50:04.483271+08:00","original_url":"https://www.pingcap.com/blog/serverless-database-2/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"e5047a94013f","zh_title":"ClickHouse 26.8：构建流式 HTTP 查询 API","zh_summary":"ClickHouse 官方博客展示了如何在 26.8 中直接用命名 HTTP handlers、类型化参数、分页、framing formats 和访问控制构建流式 HTTP API。文章以英国房产成交价数据集为例，给出建表、导入转换和查询封装的过程；同时指出，如果只需要受控的 ClickHouse 查询，可以省掉中间应用 API 层，从而简化架构。包含实际代码，机制说明清晰。","reason":"数据从业者可了解如何在数据库侧直接提供受控查询 API，减少中间服务层、降低维护成本，并评估这种能力在自身架构中的适用边界。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["方案封装与分发"],"decision_concerns":["权限与安全","可维护性与复用"]},"heat":40,"quality_score":89,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":89,"shelf":"evergreen","pinned":false,"published":"2026-09-05T01:20:25.051642+08:00","first_seen":"2026-09-05T01:20:25.051642+08:00","original_url":"https://clickhouse.com/blog/clickhouse-streaming-http-api","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"b77d23be249c","zh_title":"OpenViking实战：用虚拟文件系统统一Agent知识库、记忆与技能","zh_summary":"火山引擎开源OpenViking，以虚拟文件系统统一知识库、记忆与技能，并通过L0/L1/L2三层上下文加载优化Agent检索。文章详解其设计思路、部署流程及接入Claude Code等工具的实际体验，展示如何减少无关内容进入上下文，同时保留可观察的检索轨迹。","reason":"面向AI Agent的上下文管理是数据Agent落地的关键基建，文章给出分层检索与统一上下文的具体实践，值得数据从业者参考。","category":"agent","category_label":"Data Agent","vendors":["火山引擎"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":["Agent构建"],"decision_concerns":["准确性与语义一致性","成本与性能"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-09-04T17:17:06+08:00","first_seen":"2026-09-05T00:43:06.690820+08:00","original_url":"https://www.woshipm.com/ai/6459718.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"6a15bb49ecb1","zh_title":"OpenAI 内部 Data Agent 的六层上下文","zh_summary":"OpenAI 公开了内部 Data Agent 的构建方法。系统连接数仓和模型，也把表使用记录、人工注释、代码补全、组织知识、记忆与运行时上下文分层组合，并在 Slack、网页、IDE 与 Codex CLI 中复用。权限透传和持续评测被放在与生成能力同等重要的位置。","reason":"这是一份少见的生产级 Data Agent 拆解，能直接帮助判断上下文、权限、入口和评测应如何组成完整产品，而不是只做一个会写 SQL 的聊天框。","category":"agent","category_label":"Data Agent","vendors":["OpenAI"],"topics":["Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"heat":47,"quality_score":96,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-09-05T00:32:30+08:00","discovery_source":"X·@alexxubyte","importance":96,"shelf":"evergreen","pinned":false,"published":"2026-01-29T00:00:00+00:00","first_seen":"2026-09-05T00:32:30+08:00","original_url":"https://openai.com/index/inside-our-in-house-data-agent/","items":[{"source":"OpenAI"},{"source":"X 线索·@alexxubyte"}],"source_badge":"RSS"},{"event_id":"3c7ef4914e12","zh_title":"Pinterest 用意图向量解决十万张表的 Text-to-SQL 检索","zh_summary":"Pinterest 面对十万级分析表和数千名用户，没有把 Text-to-SQL 的希望只压在大模型上，而是从历史查询中抽取连接、过滤、聚合等结构化意图，构建意图向量，再结合文档、热度、新鲜度和治理等级进行资产排序。核心变化是先找到可信的数据资产，再生成 SQL。","reason":"它抓住了企业 Text-to-SQL 最容易被低估的一环，也就是表检索。对数据目录、语义检索和 Data Agent 的工程落地都有很强的参考价值。","category":"agent","category_label":"Data Agent","vendors":["Pinterest","DataHub","OpenSearch"],"topics":["Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"heat":46,"quality_score":94,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-09-05T00:32:30+08:00","discovery_source":"X·@PinterestEng","importance":94,"shelf":"evergreen","pinned":false,"published":"2026-03-06T00:00:00+00:00","first_seen":"2026-09-05T00:32:30+08:00","original_url":"https://medium.com/pinterest-engineering/unified-context-intent-embeddings-for-scalable-text-to-sql-793635e60aac","items":[{"source":"Pinterest Engineering"},{"source":"X 线索·@PinterestEng"}],"source_badge":"RSS"},{"event_id":"b37fd3d1c6d4","zh_title":"Google Cloud 把数据技能带进 IDE 和 CLI","zh_summary":"Google Cloud 发布 Google Data Cloud 一批更新。Data Agent Kit 正式可用，提供免费 MCP 工具和 Google 编写的 agent skills，可把 15+ 个 Google Data Cloud 服务接入 VS Code、Cursor、Claude Code、Codex 等编码代理，支持查看 schema、编写查询和用自然语言构建端到端数据管道。Spanner Omni 正式可用，支持本地、其他公有云和 Kubernetes/VM 部署，并统一多模型 API；AlloyDB 推出面向 agent 的 PostgreSQL，Cloud SQL/AlloyDB 的 BM25 混合检索进入预览。Lakehouse runtime catalog 的区域端点覆盖 22 个 Google Cloud 区域，并为灵活列名提供 GA 支持。","reason":"数据从业者应关注 Google 将 MCP/Agent 能力接入数据云，以及 Spanner Omni、AlloyDB、湖仓 catalog 在混合云和多模型场景的 GA/预览，这些会影响平台选型与 Agent 数据接入方式。","category":"agent","category_label":"Data Agent","vendors":["Google Cloud","BigQuery","AlloyDB","Google","dbt"],"topics":["Data Agent","平台AI化","湖仓"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","Agent接口与工具"],"use_cases":["Agent构建","自助分析"],"decision_concerns":["可维护性与复用","可靠性与评估"]},"heat":50,"quality_score":90,"trend_score":18,"star":true,"editorial_pick":true,"curated_at":"2026-09-05T00:32:30+08:00","discovery_source":"X·@googlecloud","importance":90,"shelf":"evergreen","pinned":false,"published":"2026-05-20T08:00:00+08:00","first_seen":"2026-09-05T00:32:30+08:00","original_url":"https://cloud.google.com/blog/products/data-analytics/data-agent-kit-brings-data-skills-and-tools-to-your-ide-or-cli","items":[{"source":"Google Cloud"},{"source":"X 线索·@googlecloud"},{"source":"Google Cloud Data Analytics Blog"},{"source":"Google Cloud Data Analytics Blog"},{"source":"Google Cloud Data Analytics Blog"},{"source":"Google Cloud Data Analytics Blog"}],"source_badge":"RSS"},{"event_id":"214ed5550146","zh_title":"LinkedIn SQL Bot 如何支撑企业取数","zh_summary":"LinkedIn 在内部分析平台 DARWIN 中建设 SQL Bot，用表检索、知识图谱、LLM 重排和查询自纠错组成多 Agent 流程，并加入数据集访问控制和验证机制。文章还公开了真实使用数据。集成 SQL Bot 后采用率提升 5 至 10 倍，约八成会话使用过 Fix with AI。","reason":"这篇文章同时提供了架构、权限、评测和采用率证据，是观察企业 Text-to-SQL 如何从功能走向工作流的优质案例。","category":"agent","category_label":"Data Agent","vendors":["LinkedIn","LangChain","LangGraph"],"topics":["Data Agent","ChatBI"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"heat":45,"quality_score":92,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-09-05T00:32:30+08:00","discovery_source":"X·@LangChainAI","importance":92,"shelf":"evergreen","pinned":false,"published":"2024-12-09T00:00:00+00:00","first_seen":"2026-09-05T00:32:30+08:00","original_url":"https://www.linkedin.com/blog/engineering/ai/practical-text-to-sql-for-data-analytics","items":[{"source":"LinkedIn Engineering"},{"source":"X 线索·@LangChainAI"}],"source_badge":"RSS"},{"event_id":"d2194130512d","zh_title":"Harrison Chase 谈领域子 Agent 的编排方式","zh_summary":"Harrison Chase 分享了一种面向数据工作的 Deep Agents 形态。上层编排 Agent 理解任务，再把不同环节交给拥有专属上下文和工具的领域子 Agent。设计重点是把数据发现、查询、分析等职责和上下文明确分开，并控制 Agent 数量。","reason":"这条帖子提供了一个简洁但有用的产品视角。复杂 Data Agent 无需把所有知识和工具塞进单一提示词，可以按领域拆分责任与上下文。","category":"agent","category_label":"Data Agent","vendors":["LangChain","Deep Agents"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":38,"quality_score":84,"trend_score":0,"star":true,"editorial_pick":true,"curated_at":"2026-09-05T00:32:30+08:00","discovery_source":"X·@hwchase17","importance":84,"shelf":"evergreen","pinned":false,"published":"2026-04-08T05:09:38+08:00","first_seen":"2026-09-05T00:32:30+08:00","original_url":"https://x.com/hwchase17/status/2041624465625510145","items":[{"source":"Harrison Chase"}],"source_badge":"RSS"},{"event_id":"e7ef7e2d8090","zh_title":"Codatum AI Agent 保留了代码审阅和回滚","zh_summary":"Codatum 的 AI Agent 可以从自然语言出发检索表、生成 SQL、制作图表并编辑 Notebook；产品同时区分只回答问题的 Ask 模式和可执行操作的 Agent 模式。每次 AI 编辑都会先创建版本，用户可以审阅和恢复，模型能访问的资产也受现有权限与 AI Profile 控制。","reason":"它把 Agent 的执行能力与人类审阅、版本回滚和权限范围放在同一个产品流程里，关注点超出了功能数量。","category":"agent","category_label":"Data Agent","vendors":["Codatum"],"topics":["Data Agent","ChatBI"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"heat":43,"quality_score":86,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-09-05T00:32:30+08:00","discovery_source":"X·@codatum_jp","importance":86,"shelf":"evergreen","pinned":false,"published":"2026-03-24T08:04:15+08:00","first_seen":"2026-09-05T00:32:30+08:00","original_url":"https://docs.codatum.com/features/ai-agent/overview","items":[{"source":"Codatum"},{"source":"X 线索·@codatum_jp"}],"source_badge":"RSS"},{"event_id":"d17829a807e2","zh_title":"Jay Zoo 谈可靠 Data Agent 的四类证据","zh_summary":"Jay Zoo 的系列帖子把 Data Agent 的可靠性拆成四部分。数据定义、SQL 与公式、验证过程、最终呈现都要能追溯。语义层负责限制模型猜测，独立验证器在结果发出前检查数字、口径和异常，最终答案则应把依据展示给用户。","reason":"这组帖子没有停在“提高准确率”的口号，而是把可靠性落实为可观察、可审计的产品机制，适合用来检查 Data Agent 是否真的能进入业务决策。","category":"agent","category_label":"Data Agent","vendors":[],"topics":["Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"heat":40,"quality_score":88,"trend_score":0,"star":true,"editorial_pick":true,"curated_at":"2026-09-05T00:32:30+08:00","discovery_source":"X·@jayzoojayzoo","importance":88,"shelf":"evergreen","pinned":false,"published":"2026-08-27T11:10:28+08:00","first_seen":"2026-09-05T00:32:30+08:00","original_url":"https://x.com/jayzoojayzoo/status/2092811959230152768","items":[{"source":"Jay Zoo"}],"source_badge":"RSS"},{"event_id":"ea4f1d97db33","zh_title":"一张图看懂 Data Agent 如何像分析师一样工作","zh_summary":"该内容以图解方式拆解 Data Agent 的分析工作流，说明其如何模拟分析师完成数据理解、指标计算与结论呈现。文章源自数据领域厂商官方博客，作为入门科普有助于理解 Data Agent 的能力边界与交互方式。具体实现细节和案例需以原文为准。","reason":"以直观图示解释 Data Agent 的工作机制，适合想快速了解其分析逻辑与产品定位的数据从业者。","category":"agent","category_label":"Data Agent","vendors":["Aloudata"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["准确性与语义一致性"]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-09-04T16:04:03+08:00","first_seen":"2026-09-04T19:19:40.171721+08:00","original_url":"https://aloudata.com/blogs/how-data-agent-works-like-analyst-infographic","items":[{"source":"Aloudata 博客"}],"source_badge":"官网"},{"event_id":"08421439e662","zh_title":"S3到GPU一次拷贝：Vortex重新定义ML训练数据加载","zh_summary":"SpiralDB的Onur Satici在演讲中介绍Linux基金会下的开源列式文件格式Vortex如何加速ML训练数据加载。它通过级联轻量编码、基于布局的分段剪枝和零拷贝内存管道，消除CPU/NVMe瓶颈，使数据可从S3直通GPU，速度最高达60 Gbps，且无需预先重新处理数据。演讲还用4K视频扫描演示了列投影剪枝时仅传输所选列字节的效果。","reason":"Vortex展示了面向GPU/AI场景的列式格式与数据加载优化方向，对湖仓和AI数据平台架构设计有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["SpiralDB"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入"],"decision_concerns":["成本与性能"]},"heat":38,"quality_score":85,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-09-04T19:00:00+08:00","first_seen":"2026-09-04T19:19:40.171721+08:00","original_url":"https://www.infoq.com/presentations/vortex-columnar-file-format-gpu-streaming/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"cbf67eab8b01","zh_title":"高质量数据如何驱动AI时代的成功","zh_summary":"Amplitude在博客中提出，AI时代的数据领导者需要在短期与长期ROI之间取得平衡，将AI投入视为持续复利的循环。文章认为AI正在把数据民主化从自助报表推向自然语言问答，业务用户无需懂SQL或处理数据，即可直接通过聊天界面获取转化、漏斗、新用户等指标答案。未来这类交互还将进入Slack等协作工具，成为普遍工作流。","reason":"文章点明了ChatBI/数据Agent落地所需的先决条件，即高质量数据和语义一致的指标层，对数据从业者规划AI数据产品有参考价值。","category":"agent","category_label":"Data Agent","vendors":["Amplitude"],"topics":["ChatBI","数据人"],"product_ids":[],"focus":{"id":"ai-analysis","label":"AI 数据分析","priority":3,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","指标与语义"],"use_cases":["指标问答","自助分析"],"decision_concerns":["准确性与语义一致性","用户采用与业务价值"]},"heat":28,"quality_score":63,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":63,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:08+08:00","first_seen":"2026-09-04T19:19:40.171721+08:00","original_url":"https://amplitude.com/blog/data-fuels-ai-success","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"159bcbb463f0","zh_title":"治理不止安全：湖仓上的知识、上下文与本体","zh_summary":"文章从医疗场景谈起，指出面向AI的数据治理不能只回答“谁能访问数据”，还要解释数据的含义、可信度以及是否适合被AI学习。文中提出DEP（Data Empowerment Program）视角：分类标签、去标识化策略、模型卡、数据契约等治理工件都是企业语义的原材料，治理应是知识、上下文和本体，而不只是安全控制。文章认为在湖仓（lakehouse）环境中，应从数据、AI、人员、产品与共享上下文五个维度统一设计治理体系，让治理成为AI运行的基础。","reason":"这篇文章把数据目录、质量、血缘等治理资产重新定义为语义基础而非合规成本，有助于数据从业者理解如何在湖仓上为AI建立可信上下文，是数据平台与语义层建设者值得关注的视角。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["语义层","平台AI化"],"product_ids":[],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":[],"decision_concerns":["准确性与语义一致性","权限与安全"]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-09-04T04:20:00+08:00","first_seen":"2026-09-04T10:02:21.710394+08:00","original_url":"https://www.databricks.com/blog/governance-beyond-security-knowledge-context-ontology-lakehouse","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"110ce74fa9e5","zh_title":"用Databricks构建高质量可信数据产品","zh_summary":"Databricks官方博客介绍如何将产品思维应用于数据，构建企业级高质量、可信的数据产品。文中提及通过数据网格范式实现数据资产所有权与管理民主化，并指出无论是否采用数据网格，数据质量和可用性对数据驱动决策都至关重要。博客还给出基于Databricks平台落地数据产品架构的具体建议。","reason":"数据从业者可从中了解在湖仓平台上落地数据产品与数据网格原则的实践路径，对数据资产治理与平台建设有直接参考价值。","category":"product","category_label":"数据产品","vendors":["Databricks"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":[],"decision_concerns":["可靠性与评估"]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-09-04T03:55:00+08:00","first_seen":"2026-09-04T10:02:21.710394+08:00","original_url":"https://www.databricks.com/blog/building-high-quality-and-trusted-data-products-databricks","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"eebe3840dcae","zh_title":"什么是数据转换？","zh_summary":"数据转换是处理原始数据的过程，通过分箱、聚合、清洗、去重、派生、增强、过滤、集成、连接、拆分、汇总、验证、格式修订、键重构等多种技术，将数据转化为可用于分析的结构。文章列举了各类转换方法，适合数据平台建设者参考。","reason":"系统梳理数据转换的常见类型，是数据平台/数据集成治理领域的基础方法论，有助于从业者理解ETL/ELT各环节。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":[],"decision_concerns":[]},"heat":25,"quality_score":55,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":55,"shelf":"evergreen","pinned":false,"published":"2026-09-04T03:54:00+08:00","first_seen":"2026-09-04T10:02:21.710394+08:00","original_url":"https://www.databricks.com/blog/what-is-data-transformation","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"29e0b8236c7e","zh_title":"Snowflake Notebooks新增强可观测性与运行控制","zh_summary":"Snowflake Notebooks发布了面向交互开发和生产定时运行的可观测性与控制改进。开发时可在笔记本内实时查看CPU和内存使用情况，并通过颜色预警及时识别资源风险。点击仪表可查看各文件对内存的占用分解，以及后台进程消耗。遇到高负载时，界面会推荐操作，如让CoCo分析瓶颈、扩展到更大计算池或重启内核，方便用户快速排查问题。","reason":"数据开发与生产调度中的Notebook可观测性是平台运维的重要环节，Snowflake将资源监控直接嵌入Notebook，能帮助数据团队减少运行失败并优化成本。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"news","pinned":false,"published":"2026-09-04T03:45:17+08:00","first_seen":"2026-09-04T10:02:21.710394+08:00","original_url":"https://medium.com/snowflake/new-in-snowflake-notebooks-more-visibility-less-guesswork-289d3b7c68c1?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"b4ab99888c0d","zh_title":"AI时代管好业务词汇：治理术语表是Agent理解业务的基础","zh_summary":"本文来自Snowflake官方博客，指出业务术语表是AI Agent准确理解业务问题的关键。文中举例医药研究员询问“API optimal dosage”，若Agent把API理解为应用程序接口而非活性药物成分，将给出看似自信实则无效的答案。文章提出用Cortex AI清洗现有业务术语表并持续维护的模式，强调术语表应在查询时被Agent读取，而非仅作为无人查阅的参考文档。","reason":"数据从业者应关注业务术语/语义层在Data Agent准确性中的基础作用，文中提供了可借鉴的Cortex AI治理模式。","category":"agent","category_label":"Data Agent","vendors":["Snowflake"],"topics":["Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","知识与上下文"],"use_cases":["Agent构建"],"decision_concerns":["准确性与语义一致性"]},"heat":33,"quality_score":73,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":73,"shelf":"evergreen","pinned":false,"published":"2026-09-04T03:01:01+08:00","first_seen":"2026-09-04T10:02:21.710394+08:00","original_url":"https://medium.com/snowflake/minding-your-language-in-the-ai-era-21cd9d1c87e4?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"8f1d134628cf","zh_title":"数据 Agent 真正缺的不是更强模型，而是上下文层","zh_summary":"a16z 认为，数据 Agent 的主要瓶颈已经不只是 Text-to-SQL，而是缺少持续更新的业务上下文。现代上下文层应成为传统语义层的超集，同时覆盖指标定义、规范实体、身份解析、隐性业务规则和治理要求。文章给出从数据接入、自动构建、人工补充、API/MCP 连接到反馈回流的五步架构，并梳理了数据平台、AI 数据分析产品和独立上下文层公司的竞争位置。","reason":"这篇文章把数据 Agent 的产品问题从“模型会不会写 SQL”推进到“系统如何持续获得可信业务语义”，对设计数据平台、Data Agent 和语义治理模块都有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["Databricks","Snowflake","OpenAI","Palantir"],"topics":["Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","指标与语义"],"use_cases":["Agent构建","指标问答"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":50,"quality_score":94,"trend_score":15,"star":true,"editorial_pick":true,"curated_at":"2026-09-04T09:55:00+08:00","discovery_source":"X·@JasonSCui","importance":94,"shelf":"evergreen","pinned":true,"published":"2026-03-10T22:00:21+08:00","first_seen":"2026-09-04T09:55:00+08:00","original_url":"https://a16z.com/your-data-agents-need-context/","items":[{"source":"a16z"},{"source":"X 线索·@JasonSCui"},{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"ba19ed95fa31","zh_title":"从Neon Postgres迁移到ClickHouse Managed Postgres","zh_summary":"ClickHouse官方博客分享了三支团队将生产Postgres工作负载从Neon迁移到ClickHouse Managed Postgres的案例。迁移原因包括负载下的可靠性问题、性能不稳定、基础设施成本和网络传输费用上升。迁移后，团队报告了更稳定的查询性能、更少运维问题和更低成本；Infinitas Learning在相同schema下p99查询延迟从秒级降至个位数毫秒，且通过ClickPipes在数小时内完成数据迁移。","reason":"真实迁移案例展示了托管Postgres在扩展阶段的性能与成本权衡，以及ClickPipes支持快速数据迁移的实践价值，对维护数据基础设施的从业者有参考意义。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse","Neon"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":30,"quality_score":66,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":66,"shelf":"evergreen","pinned":false,"published":"2026-09-02T08:00:00+08:00","first_seen":"2026-09-04T01:47:50.355474+08:00","original_url":"https://clickhouse.com/blog/neon-to-clickhouse-managed-postgres","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"5ab337977aa6","zh_title":"Amazon OpenSearch Serverless 下一代私网连接模式","zh_summary":"AWS 官方介绍了 OpenSearch Serverless 下一代私网访问连接方式：不再需要在每个消费 VPC 中创建 VPC 端点并配置 Route 53 Profiles、自定义私有 hosted zone 或 resolver inbound endpoints，而是改用标准 AWS PrivateLink 接口端点，并原生支持私有 DNS。集合端点基于 on.aws 域，分为单集合端点与账户级区域端点，后者通过 x-amz-aoss-collection-name 请求头指定目标集合。文章还按区域和账户边界给出了 9 种架构模式的 DNS 解析与数据流量路径。","reason":"数据平台工程师在规划 OpenSearch Serverless 私网访问、跨账户或多区域连接时，可直接对照这些模式，减少此前复杂的 DNS 编排与维护负担。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["权限与安全"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-09-04T00:26:58+08:00","first_seen":"2026-09-04T01:47:50.355474+08:00","original_url":"https://aws.amazon.com/blogs/big-data/network-connectivity-patterns-for-the-next-generation-of-amazon-opensearch-serverless/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"2eee875ea4c4","zh_title":"Moovit通过架构现代化实现33%成本优化","zh_summary":"Moovit是Mobileye旗下MaaS出行解决方案提供商，其数据平台处理大量出行、应用和运营数据。随着业务增长，单一Amazon Redshift集群成本不断上升。Moovit通过构建多引擎Lakehouse架构，将工作负载分配到Provisioned Redshift、Redshift Serverless与Amazon EMR Serverless等合适引擎，使Redshift集群规模缩减50%，并实现33%的成本优化。文中还介绍了洞察工作负载模式、清理非必要负载、筛选卸载候选并成功完成POC的实践方法。","reason":"展示了一套从单体仓库走向多引擎湖仓的完整迁移与评估方法，对数据平台团队在控制成本的同时提升架构灵活性有直接借鉴价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":41,"quality_score":92,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":92,"shelf":"evergreen","pinned":false,"published":"2026-09-04T00:23:46+08:00","first_seen":"2026-09-04T01:47:50.355474+08:00","original_url":"https://aws.amazon.com/blogs/big-data/how-moovit-achieved-33-cost-optimization-through-architectural-modernization/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"80834225a78b","zh_title":"用Snowflake数据构建车队预测性维护分析仪表盘","zh_summary":"本文演示了使用Snowflake中的车辆遥测数据构建预测性维护仪表盘的方法。通过SQL查询完成原始记录到分析数据集的转化，并利用Dashtera实现交互式可视化。仪表盘涵盖车队健康KPI、风险分布、使用量风险分层、相关性分析、时间序列监测和车队健康评分。该方案将存储、分析逻辑与可视化分离，以SQL作为核心，适合设备运维监控场景。","reason":"数据从业者可借鉴一套结合数仓SQL分析与BI可视化的可复用范式，用于设备预测性维护场景的仪表盘建设。","category":"bi","category_label":"BI 与可视化","vendors":["Snowflake","Dashtera"],"topics":["风险管理"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["看板与报告"],"decision_concerns":["可维护性与复用"]},"heat":20,"quality_score":45,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":45,"shelf":"evergreen","pinned":false,"published":"2026-09-03T22:01:05+08:00","first_seen":"2026-09-04T01:47:50.355474+08:00","original_url":"https://medium.com/snowflake/snowflake-powered-fleet-predictive-maintenance-analytics-dashboard-484e7d2188c1?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"4d66f00eb39c","zh_title":"漏斗分析是什么？定义、示例与工具","zh_summary":"漏斗分析是一种分析用户从起点到转化点之间事件序列的方法，帮助产品与市场经理理解用户在数字触点上的行为与障碍。文章以免费试用转付费为例，展示了从打开邮件、点击CTA、创建账户到转为付费用户的四步漏斗，并介绍了多种漏斗分析用途与可用工具。核心思路是通过定位每一步的流失摩擦，改善用户体验并提升转化率。","reason":"漏斗分析是用户行为分析与转化优化的基础方法，文中对概念、场景和工具有系统梳理，适合数据从业者搭建转化指标体系或做客户旅程分析时参考。","category":"product","category_label":"数据产品","vendors":[],"topics":["客户运营"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["用户采用与业务价值"]},"heat":20,"quality_score":44,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":44,"shelf":"evergreen","pinned":false,"published":"2026-09-03T18:34:48+08:00","first_seen":"2026-09-04T01:47:50.355474+08:00","original_url":"https://amplitude.com/blog/funnel-analysis","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"9ee1caee2efa","zh_title":"2026年14款最佳产品管理工具盘点（附资深PM建议）","zh_summary":"原文盘点2026年14款最佳产品管理工具，覆盖项目管理、产品分析与洞察、协作、产品设计与市场情报等类别，并提到Aha!、Jira、monday.com、Productboard、Amplitude、Tableau等代表产品。文中引用BetterCloud数据称，2024年企业平均使用106个SaaS应用，低于2023年的112个，因此重点不是堆工具，而是围绕团队工作方式选择合适组合。文章认为好的工具栈能帮助产品团队从洞察转向行动，用数据而非猜测做决策。","reason":"来自数据领域厂商官方博客的工具栈盘点，能帮助数据从业者理解产品经理眼中数据分析与BI工具所处位置，以及产品侧选型时关注的价值。","category":"bi","category_label":"BI 与可视化","vendors":["Amplitude","Tableau"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["用户采用与业务价值"]},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-09-03T18:23:41+08:00","first_seen":"2026-09-04T01:47:50.355474+08:00","original_url":"https://amplitude.com/blog/product-management-tools","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"3a9bd9cef38b","zh_title":"美国2035劳动力：仅增3.5%，GDP增长22%，AI加速转型","zh_summary":"据美国劳工统计局2025-2035就业预测，美国劳动力十年仅增3.5%，GDP预计增长22%，意味着生产率年均需提升近2%，将迫使企业加速AI转型。约61%岗位依赖体力或人际工作，AI目前可完全自动化的岗位约13%，AI更多创造“超级员工”机会而非大规模取代就业。劳动力放缓源于移民政策、低出生率与老龄化，65岁以上劳动力将增长21%。企业应构建“动态组织”，应对人才短缺和技能转型。","reason":"基于权威就业预测揭示AI与劳动力结构的真实关系，为企业制定数据/AI产品与人才布局提供宏观参考。","category":"insight","category_label":"AI分析","vendors":[],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":33,"quality_score":74,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"evergreen","pinned":false,"published":"2026-09-02T22:35:11+08:00","first_seen":"2026-09-04T00:27:09.861536+08:00","original_url":"https://joshbersin.com/2026/09/us-workforce-in-2035-a-few-more-workers-a-lot-more-output/","items":[{"source":"Josh Bersin"}],"source_badge":"RSS"},{"event_id":"2cb23ff14d5d","zh_title":"未来转型中重新设计工作的五个思路","zh_summary":"Visier首席研究员参加HR Leaders圆桌，与施耐德电气、北欧航空、壳牌等企业人员分析负责人探讨“人机时代”的工作再设计。核心观点是HR不应单独重构流程，而应让受影响部门参与共创，否则只是“政策”；同时伦理护栏应先于推广。文章以福特AI产线裁员后被迫召回300名工程师为例警示风险。","reason":"数据与分析领导者需要参与AI驱动的工作再设计，明确人机分工与评估指标，本文提供了来自多家企业实践的一线经验，对数据团队推进AI落地有借鉴意义。","category":"product","category_label":"数据产品","vendors":["Visier"],"topics":["组织人才","数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":23,"quality_score":52,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":52,"shelf":"evergreen","pinned":false,"published":"2026-09-02T08:00:00+08:00","first_seen":"2026-09-04T00:27:09.861536+08:00","original_url":"https://www.visier.com/blog/redesign-work-for-future-transformation/","items":[{"source":"Visier Blog"}],"source_badge":"RSS"},{"event_id":"f65a1c3ef6c3","zh_title":"Omdia报告：OceanBase位居亚太分布式数据库市场第一","zh_summary":"Omdia最新报告显示，按2025年收入计算，OceanBase位列亚太及大洋洲分布式数据库市场第一。该区域市场2025年规模达9亿美元，预计2029年增至18亿美元，复合增长率19.3%。OceanBase已服务全球超4000家客户，其中超400家金融机构，60%以上将核心系统部署于其平台。报告还指出，分布式数据库正与AI能力集成，以支撑AI Agent实时推理等负载。","reason":"报告提供了亚太分布式数据库市场的权威份额、增长预测及厂商全球化进展，对数据库选型和数据平台战略判断有直接参考价值。","category":"product","category_label":"数据产品","vendors":["OceanBase"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":33,"quality_score":74,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"evergreen","pinned":false,"published":"2026-09-04T00:37:58+08:00","first_seen":"2026-09-04T00:27:09.861536+08:00","original_url":"https://www.infoq.cn/article/dICPOgXYkvE9HcA1KpUv?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"2f84330339e9","zh_title":"亚马逊云科技推出规范驱动组合，简化数据工作流治理","zh_summary":"亚马逊云科技介绍了一种规范驱动组合模式，将工作流意图与处理逻辑分离，以减少数据流水线重复代码并强化验证治理。该方法采用意图层、组合层、处理层三层架构，基于 AWS Lambda、Step Functions、S3 与 OpenSearch Service 实现，通过声明式规范和转换能力注册表动态组装工作流，支持字段映射、数据分类与版本化能力。适合数据集较多、受监管环境中需要可追溯性的场景，但对简单流水线可能过度设计。","reason":"数据平台工程师可借鉴该模式解决多数据集流水线重复开发、难验证和治理薄弱问题，声明式规范与能力注册表设计具有实操参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":[],"decision_concerns":["可维护性与复用","可靠性与评估"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-09-04T00:16:00+08:00","first_seen":"2026-09-04T00:27:09.861536+08:00","original_url":"https://www.infoq.cn/article/cg5y0kCfmWKrIjCraZeH?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"6d4892f9d110","zh_title":"南方公司SCOUT：实时风暴运营应用扩展数据智能","zh_summary":"南方公司在Databricks Data + AI平台上新增SCOUT实时风暴运营应用，与SPEAR和RAMP共同构成端到端风暴智能闭环。SCOUT将停电、客户、地形与抢修计划数据整合到统一实时恢复界面，已获1139名员工采用，其中超250人曾在6月单日峰值风暴期间使用。该应用基于Delta Lake、Unity Catalog和Lakehouse架构，Genie Code加速了自定义数据管道开发。","reason":"数据从业者可通过此案例了解能源企业如何利用湖仓平台统一实时运营数据，形成从灾前预测到灾中感知、灾后分析的完整闭环，具有可借鉴的数据产品落地价值。","category":"insight","category_label":"AI分析","vendors":["Databricks"],"topics":["风险管理"],"product_ids":["databricks-genie"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","场景与方案"],"use_cases":["数据接入","看板与报告"],"decision_concerns":["用户采用与业务价值"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-09-03T07:20:00+08:00","first_seen":"2026-09-03T12:35:15.887433+08:00","original_url":"https://www.databricks.com/blog/southern-companys-scout-completing-storm-intelligence-story","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"c5c8e925af01","zh_title":"Swiggy 用350+特征与多任务MLP预测客户终身价值","zh_summary":"Swiggy 开发了内部pLTV模型，基于350多个首单前特征，用多任务MLP同时预测Food和Instamart的客户终身价值。加入订单数作为辅助任务后，模型参数从36.3万降至13.5万，减少63%，并略微提升预测表现。该信号被用于Google Target ROAS广告竞价，以优化拉新投放。","reason":"展示了在冷启动和稀疏目标下用多任务学习压缩模型并提升LTV预测的落地案例，对数据驱动获客与广告投放优化的从业者有参考价值。","category":"insight","category_label":"AI分析","vendors":[],"topics":["销售增长"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":38,"quality_score":85,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-09-02T21:55:00+08:00","first_seen":"2026-09-03T12:35:15.887433+08:00","original_url":"https://www.infoq.com/news/2026/09/swiggy-pltv-multitask-mlp/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"4761ed6dc8dd","zh_title":"Snowflake自动数据分类：PII检测完整指南","zh_summary":"Snowflake技术架构师撰写的完整指南，介绍如何在数据仓库内原生自动发现、分类和保护敏感数据。方案基于机器学习分析列数据模式与元数据，无需外部工具、无需数据移动。文中涵盖手动分类、自定义分类器、分类配置、自动化启用、合规查询以及基于标签的脱敏策略集成等操作细节。","reason":"数据从业者可了解Snowflake内置治理能力的自动化PII识别流程，以及分类结果如何与脱敏策略联动，是平台化数据治理的落地参考。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据发现与搜索"],"decision_concerns":["权限与安全","准确性与语义一致性"]},"heat":41,"quality_score":90,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":90,"shelf":"evergreen","pinned":false,"published":"2026-09-03T09:01:01+08:00","first_seen":"2026-09-03T12:35:15.887433+08:00","original_url":"https://medium.com/snowflake/snowflake-auto-data-classification-4c749af1b48d?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"9bfa01144959","zh_title":"创建或演进分析追踪计划的实践要点","zh_summary":"本文最初发布于 Iteratively 博客，讲述制定和维护 analytics tracking plan 的方法。它建议先定义目标与指标，再确定需要采集的事件和用户属性，并保证跨 iOS、Android、Web 与后端来源的数据一致。文中以“Q1 获客增长15%”为例，将目标拆解为转化率指标和 User Signed Up 事件，并提出分离开发与生产环境、落实追踪计划、指派负责人、完整文档化等实践。","reason":"没有清晰的追踪计划和指标口径，后续的 BI 报表、用户分析和数据决策都会失去可信基础；此文提供适合数据团队与研发协作的埋点治理和一致性清单。","category":"product","category_label":"数据产品","vendors":["Amplitude"],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","指标与语义"],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":30,"quality_score":67,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":67,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:08+08:00","first_seen":"2026-09-03T12:35:15.887433+08:00","original_url":"https://amplitude.com/blog/analytics-tracking-practices","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"c4e8f5a99035","zh_title":"打造实验文化：Spotify与Einride的实战经验分享","zh_summary":"Spotify的Web分析与实验负责人Ashit Kumar与Einride高级产品经理Philip Knape分享了建立实验文化的经验。Ashit通过A/B测试优化多市场转化漏斗，并用反馈循环向业务方证明实验价值、争取更多资源；Philip则使用Amplitude Notebook向领导层清晰展示关键指标与分析解读。他们还指出，当改动方向明确时应直接实施，等待本身也会产生成本。","reason":"数据团队推广实验驱动决策时，常遇到价值难量化、资源难争取的问题，文中给出了反馈循环和高层沟通的具体做法，有直接参考价值。","category":"product","category_label":"数据产品","vendors":["Amplitude"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["用户采用与业务价值"]},"heat":24,"quality_score":54,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":54,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:08+08:00","first_seen":"2026-09-03T12:35:15.887433+08:00","original_url":"https://amplitude.com/blog/culture-of-experimentation","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"341e5c5d3b89","zh_title":"数据团队与产品团队如何休战：走向数据民主化","zh_summary":"产品团队希望数据又快又整齐，数据团队则认为高质量数据需要时间沉淀，这种冲突会阻碍数据民主化。文章提出，应通过数据集中化、把内部团队当作客户以及共情式文化转变来解决冲突，让数据质量责任分布到整个组织。文中列出部门孤岛、数据混乱、缺乏信任、访问受限等典型症状，并建议领导者从冲突根源入手推动变革。","reason":"文章把数据团队与产品团队的冲突拆成一目了然的组织症状，并给出集中化与内部客户导向的改进方向，对数据平台和数据产品落地者具备参考价值。","category":"product","category_label":"数据产品","vendors":[],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["自助分析"],"decision_concerns":["用户采用与业务价值"]},"heat":23,"quality_score":52,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":52,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:08+08:00","first_seen":"2026-09-03T12:35:15.887433+08:00","original_url":"https://amplitude.com/blog/data-and-product-teams","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"775f063ddfa3","zh_title":"Genie Agents扩展：深度分析与文件推理等新能力","zh_summary":"Databricks在Data and AI Summit上宣布Genie Spaces演进为Genie Agents后，持续扩展其能力。Agent mode现已面向所有Genie Agents开放，可进行多步推理、迭代查询，并生成带引用和可视化的研究报告。同时新增Agent mode API，允许开发者将深度分析集成到自定义应用、Slack机器人和报表中，并通过SSE流式响应。此次更新旨在让Agent覆盖更广泛的问题类型，并更易从现有团队工作流中创建。","reason":"数据从业者应关注，因为对话式数据Agent正从单轮问答走向可编程的多步深度分析，Genie Agents的Agent mode和API展示了ChatBI在企业业务场景中的落地形态。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["ChatBI","Data Agent"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建","自助分析"],"decision_concerns":[]},"heat":37,"quality_score":83,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":83,"shelf":"news","pinned":false,"published":"2026-09-03T03:30:00+08:00","first_seen":"2026-09-03T05:05:05.315316+08:00","original_url":"https://www.databricks.com/blog/expanding-genie-agents-deep-analysis-file-reasoning-and-more","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"b84cc37d6f34","zh_title":"零售AI信任调查：仅13%信任推荐，59%因不准确弃店","zh_summary":"ThoughtSpot联合YouGov调查美英4833名成年人后发现，74%的消费者认为零售商收集了过多个人数据。仅13%信任AI商品推荐，47%明确表示不信任，而家人朋友（43%）和顾客评论（27%）是最受信任的信息来源，AI推荐仅获1%信任。66%的受访者称AI曾误解其需求或推荐错误商品，59%表示若AI反复推荐超出预算的商品就不愿继续在该店购物。报告认为，零售AI的准确性直接影响客户信任与留存。","reason":"通过大规模消费者调研量化零售AI的信任与准确性问题，为数据产品设计、AI应用评估提供用户侧证据。","category":"product","category_label":"数据产品","vendors":["ThoughtSpot","YouGov"],"topics":["客户运营"],"product_ids":["thoughtspot"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["准确性与语义一致性","用户采用与业务价值"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-09-03T04:00:01+08:00","first_seen":"2026-09-03T05:05:05.315316+08:00","original_url":"https://www.thoughtspot.com/blog/retail-ai-trust-report","items":[{"source":"ThoughtSpot Blog"}],"source_badge":"RSS"},{"event_id":"a28e77234d8e","zh_title":"使用Iceberg REST端点从Amazon EMR Trino查询S3 Tables","zh_summary":"Amazon S3 Tables提供原生Apache Iceberg支持和自动表维护，可减轻压缩、快照过期与元数据跟踪的运维负担。通过Iceberg REST端点，EMR上的Trino可查询这些表，形成全托管、开放标准的分析栈。该集成支持跨引擎兼容，并保持对查询执行和数据处理逻辑的控制，可帮助用户在避免厂商锁定的同时获得高吞吐查询性能。","reason":"这是AWS将托管数据湖存储与Trino查询引擎打通的新实践，让使用Iceberg的团队无需自行维护表元数据与表生命周期，值得关注。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":[],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":33,"quality_score":73,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":73,"shelf":"evergreen","pinned":false,"published":"2026-09-03T03:01:30+08:00","first_seen":"2026-09-03T05:05:05.315316+08:00","original_url":"https://aws.amazon.com/blogs/big-data/query-amazon-s3-tables-from-amazon-emr-trino-using-the-iceberg-rest-endpoint/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"52613ad8696c","zh_title":"在Amazon SageMaker用Iceberg物化视图构建Medallion架构","zh_summary":"Amazon Redshift 宣布支持创建和刷新 Apache Iceberg 物化视图，可用 CREATE MATERIALIZED VIEW ... USING ICEBERG 将预计算的连接和聚合结果存为 S3 或 S3 Table Buckets 中的标准 Iceberg 表，并注册到 AWS Glue Data Catalog。该物化视图可被 Athena、EMR 上的 Spark 和 AWS Glue 等 Iceberg 兼容引擎直接查询，Redshift 通过增量刷新保持更新。此前推出的 Redshift RG 基于 AWS Graviton，内置面向数据湖的向量化查询引擎，官方称 Iceberg 查询比 RA3 快 2.4 倍、每 vCPU 成本低 30%，且数据湖查询无按 TB 扫描费用。Redshift 还支持通过 IAM 角色或 Lake Formation 管理外部 schema 的细粒度访问。","reason":"面向湖仓架构和多引擎分析，该更新把 Redshift 的物化视图变成可被 Athena、Spark、Glue 共享的 Iceberg 表，涉及跨引擎数据共享、增量刷新与治理，值得数据平台从业者关注。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Apache Iceberg","Amazon Redshift","AWS Glue","Amazon Athena"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["生产评估与运营","自助分析"],"decision_concerns":["可维护性与复用","可靠性与评估"]},"heat":41,"quality_score":82,"trend_score":7,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-09-03T02:34:32+08:00","first_seen":"2026-09-03T05:05:05.315316+08:00","original_url":"https://aws.amazon.com/blogs/big-data/building-medallion-architecture-with-iceberg-materialized-views-in-amazon-sagemaker/","items":[{"source":"AWS Big Data Blog"},{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"b887687fe920","zh_title":"用Apache Iceberg和Flink构建动态流式数据湖","zh_summary":"本文针对流式管道写入数据湖时上游schema变更带来的运维难题，给出基于Apache Iceberg Dynamic Sink的解决方案。在Amazon Managed Service for Apache Flink上，Flink作业可对记录进行动态路由并自动演进Iceberg表schema，无需重启或手动迁移。文章基于Apache Flink 2.3和Apache Iceberg 1.11.0，展示了DataStream API实现，并附完整GitHub代码。","reason":"数据湖实时写入场景中schema演进是高频痛点，该文提供了可落地的架构和代码实践，值得数据平台与实时链路从业者参考。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":["湖仓","实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-09-03T02:28:38+08:00","first_seen":"2026-09-03T05:05:05.315316+08:00","original_url":"https://aws.amazon.com/blogs/big-data/build-a-dynamic-streaming-data-lake-with-apache-iceberg-and-apache-flink/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"04f292a5b8db","zh_title":"当 AI 开始重写负载，数据库该如何重新设计？","zh_summary":"腾讯云数据库 DBTalk“2026 国际顶会论文权威解读”中，人大张峰、浙大李环、华东师大杨程程分别从数据库内核、云原生基础设施与测试评测角度，讨论 AI 对数据库设计的改写。文章指出，向量/图/多模态对象与 AI Agent 长任务链路正进入内核，优化需沿“数据表示—存储—执行”路径做跨层协同；云上资源虽已解耦，但真正的弹性需要观测-预测-决策-执行-反馈的闭环，并向“快稳省”控制。Agent 还会把任务进度、记忆与上下文写回系统，未来基础设施需管理跨查询的任务状态和访问关系。评测应从单查询/算子转向工作流、多模协同和动态负载，且需覆盖 5 个方向。","reason":"数据库/数据平台的架构选型正被 Agent、向量和异构计算重塑。文章用三个教授视角把内核、云原生弹性和评测体系串成一张决策地图，值得数据平台负责人和架构师参考。","category":"platform","category_label":"AI 数据平台","vendors":["腾讯云"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":30,"quality_score":67,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":67,"shelf":"evergreen","pinned":false,"published":"2026-09-02T19:20:03.821854+08:00","first_seen":"2026-09-02T19:20:03.821854+08:00","original_url":"https://www.infoq.cn/article/rhKVS8RAdp4aVPZD0vZu?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"5cac4004492d","zh_title":"如何让数据库更容易暴露 Bug？","zh_summary":"该文讨论如何通过测试方法让数据库在开发阶段更早暴露潜在缺陷。属于数据库可靠性方向的工程技术内容。对依赖数据平台稳定性的数据从业者具有参考价值。","reason":"数据库是数据平台的数据承载基础，系统化测试并暴露其潜在 Bug 直接关系到上层分析与业务稳定性，值得数据工程师关注。","category":"platform","category_label":"AI 数据平台","vendors":[],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["可靠性与评估"]},"heat":31,"quality_score":69,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":69,"shelf":"evergreen","pinned":false,"published":"2026-09-02T17:30:00+08:00","first_seen":"2026-09-02T19:20:03.821854+08:00","original_url":"https://www.infoq.cn/video/O8p3IB5iTYxpJ4OKgOQ2?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"8472b7757697","zh_title":"蚂蚁VLDB工业最佳论文：OmniTable统一宽表管理35PB语料","zh_summary":"蚂蚁集团统一宽表系统OmniTable获评VLDB 2026工业赛道最佳论文，用于PB级大模型训练数据的解析、清洗、特征加工与探查。系统已在生产环境管理超过35 PB、3050亿条训练数据，覆盖Web、代码、PDF和SFT等数据域。论文披露，在真实SFT数据准备任务中，端到端周期从约14天缩短到2.5天，手工操作步骤从45步降至12步。其核心思路是逻辑统一、物理分离，将数据批次和特征列作为一等对象，降低数据定位、特征回刷与结果追溯成本。","reason":"该工作展现了PB级数据治理与特征工程在工程架构上的突破，对数据平台建设中的数据组织、血缘追溯和效率优化有直接借鉴价值。","category":"platform","category_label":"AI 数据平台","vendors":["蚂蚁集团"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":[],"decision_concerns":["可维护性与复用","成本与性能"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-09-02T14:20:17+08:00","first_seen":"2026-09-02T19:20:03.821854+08:00","original_url":"https://www.qbitai.com/2026/09/483104.html","items":[{"source":"量子位"}],"source_badge":"RSS"},{"event_id":"591af11b5a5c","zh_title":"UX分析入门：如何用数据改善用户体验","zh_summary":"Amplitude 官方博客介绍用户体验（UX）分析的核心理念，即通过数据衡量体验表现、提炼洞察并采取行动。文章强调将 UX 指标与业务目标挂钩可推动营收增长和品牌声誉，并说明了 UX 设计与数据分析的关系、常用工具及分析仪表盘的作用。还提到可通过设计、执行和分析实验来优化体验。","reason":"面向数据从业者梳理了产品体验度量与分析的基本路径，对从事客户行为分析和产品优化的人有参考价值。","category":"product","category_label":"数据产品","vendors":["Amplitude"],"topics":["客户运营"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["看板与报告"],"decision_concerns":["用户采用与业务价值"]},"heat":22,"quality_score":48,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":48,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:56+08:00","first_seen":"2026-09-02T19:20:03.821854+08:00","original_url":"https://amplitude.com/blog/ux-analytics","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"2b3bac906a4b","zh_title":"什么是增强分析？如何上手","zh_summary":"增强分析结合AI、机器学习与自然语言处理，自动化数据准备和分析过程，帮助用户更快发现数据中的模式与洞察，并预测未来趋势。Gartner数据显示，目前已有三分之一的企业在使用增强分析。文中以客户流失风险为例，说明企业可在季节性流失前主动采取折扣等干预措施。这篇文章适合作为理解增强分析概念与应用的入门参考。","reason":"增强分析是BI智能化演进的重要方向，数据从业者可借此了解其定义、技术组成及应用场景，便于评估相关工具与落地策略。","category":"bi","category_label":"BI 与可视化","vendors":[],"topics":["BI变局"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["自助分析"],"decision_concerns":["用户采用与业务价值"]},"heat":20,"quality_score":44,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":44,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:56+08:00","first_seen":"2026-09-02T19:20:03.821854+08:00","original_url":"https://amplitude.com/blog/what-are-augmented-analytics","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"fd2e877cea44","zh_title":"如何识别并使用公司中的可行动指标","zh_summary":"文章对比了可行动指标与虚荣指标的差异，指出虚荣指标（如社交媒体粉丝数、总下载量）无法反映真实业务表现，不应作为KPI。可行动指标直接关联具体业务结果，能准确反映业务健康状况，SaaS企业应重点关注转化率、留存率、流失率、活跃用户数、客户终身价值（CLV）、月经常性收入（MRR）和客户获取成本（CAC）等。文中还引用了Amplitude的产品指标指南，提供更全面的指标清单。","reason":"数据分析和数据产品人员在进行指标体系设计时，需要有一套区分虚荣指标和可行动指标的标准，本文提供了清晰的方法论和SaaS业务指标示例，有助于提升分析落地价值。","category":"product","category_label":"数据产品","vendors":["Amplitude"],"topics":["财务经营"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义"],"use_cases":[],"decision_concerns":[]},"heat":26,"quality_score":57,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":57,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:08+08:00","first_seen":"2026-09-02T19:20:03.821854+08:00","original_url":"https://amplitude.com/blog/actionable-metrics","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"4dad370e7247","zh_title":"AI时代的数据治理","zh_summary":"AI已从试点进入产品阶段，生成式与预测性系统正驱动分析、实验、客户支持等工作负载，带来数据泄露、偏见输出和不透明决策等风险。作者认为AI治理不再是纯数据团队问题，而是融合技术、政策与文化的企业级运营问题。文章指出三大重塑力量：AI原生平台和副驾带来的影子AI、全球监管趋严、以及流批一体/数据网格/多模态等数据架构演进，推动治理必须连续嵌入而非一次性门禁。","reason":"数据从业者应关注AI时代治理责任从集中式数据团队扩展到全组织，并需处理影子AI、合规与跨架构数据治理等关键问题。","category":"platform","category_label":"AI 数据平台","vendors":[],"topics":["平台AI化","风险管理"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":[],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":20,"quality_score":45,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":45,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:08+08:00","first_seen":"2026-09-02T19:20:03.821854+08:00","original_url":"https://amplitude.com/blog/ai-era-data-governance","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"4b50e35ecf47","zh_title":"Databricks发布AgentOps实践指南《Big Book of AgentOps》","zh_summary":"Databricks发布《Big Book of AgentOps》，系统阐述AgentOps——在生产环境中构建、部署和迭代AI代理的运营纪律。该指南将架构、评估、可观测性、治理、安全和成本管理整合为可重复流程，并列出团队在可靠性、可追溯性、权限控制、成本和上线决策等关键问题。文章指出AgentOps是MLOps、LLMOps之后的新阶段，并援引FactSet等客户实践说明其价值。","reason":"数据从业者应关注AgentOps：它从模型能力转向生产级Agent的架构、评估、观测、治理与成本管理，是Data Agent落地的关键方法论。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","权限与治理"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","权限与安全"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-09-02T09:30:00+08:00","first_seen":"2026-09-02T12:35:38.640037+08:00","original_url":"https://www.databricks.com/blog/announcing-databricks-big-book-agentops","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"0d51b4362db6","zh_title":"FDA在Databricks for Government上构建安全AI就绪数据基础","zh_summary":"FDA在Data+AI Summit上分享了如何在Databricks for Government上构建安全、AI就绪的数据基础。该机构每天影响三分之一的美国人，监管美国消费者支出的20%，拥有16000多名员工，覆盖200多个办公室和300多个产品类别。Databricks介绍了面向FedRAMP High和DoD IL5环境的参考架构与Terraform部署模型，通过PrivateLink、客户管理密钥等实现治理、审计和合规。","reason":"政府级数据平台的安全合规架构实践具有代表性，可为受严格监管行业的数据团队落地AI就绪数据基础提供参考。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-09-02T05:45:00+08:00","first_seen":"2026-09-02T12:35:38.640037+08:00","original_url":"https://www.databricks.com/blog/how-fda-building-secure-ai-ready-data-foundation-databricks-government","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"34f821da1d0f","zh_title":"Databricks如何一小时内消除每年120万美元AI Agent浪费","zh_summary":"Databricks工程师广泛使用AI Agent，但工具调用失败时Agent会静默重试、猜测并绕行，持续浪费token和开发时间。通过Unity Gateway的OTel tracing和Genie One，团队定位到7个工具服务器bug，每年约浪费49.9万美元token和1.2万工程小时，合计约120万美元生产力损失。发现、量化并修复全部问题仅用约一小时。该实践展示了借助可观测性追踪Agent工具调用与MCP活动的成本优化方法。","reason":"这是数据平台厂商对AI Agent工具调用成本问题的第一手技术实践，提供了可复现的监控与优化路径，对数据团队运营Agent有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["Data Agent"],"product_ids":["databricks-genie"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":45,"quality_score":100,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":100,"shelf":"evergreen","pinned":false,"published":"2026-09-02T03:43:51+08:00","first_seen":"2026-09-02T05:04:18.773327+08:00","original_url":"https://www.databricks.com/blog/how-we-eliminated-1-million-year-wasted-ai-agent-spend-one-hour","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"57a7b282e14e","zh_title":"在数据栈中落地Genie Ontology：为AI代理构建共享业务上下文","zh_summary":"Databricks 官方博客介绍 Genie Ontology，旨在为通用 AI agent 补充企业上下文，包括业务定义、规则、关系和可信来源。它从 Unity Catalog 中经治理与认证的核心概念出发，结合仪表板、文档、查询、notebook 和已连接应用中的知识，并通过 OntoRank 按认证、使用和作者等信号排序。文章展示 Databricks 产品团队如何用 Genie One 按标准化模板生成每周采用率审查，相关上下文分散在 web、桌面、移动、Slack、Teams、Google Docs 和 Jira 等来源。","reason":"该文展示了 Data Agent 如何通过语义层与企业知识图谱解决业务问答中的上下文缺失和可信来源排序问题，对做 ChatBI、分析 Agent 和数据治理的从业者有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["语义层","平台AI化","Data Agent"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","知识与上下文"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":42,"quality_score":85,"trend_score":7,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-09-01T23:00:00+08:00","first_seen":"2026-09-02T05:04:18.773327+08:00","original_url":"https://www.databricks.com/blog/operationalizing-genie-ontology-your-data-stack","items":[{"source":"Databricks Blog"},{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"71f75d69b18c","zh_title":"Discovery Bank用行为AI与治理数据实现规模化超个性化","zh_summary":"Discovery Bank将银行架构建立在基于行为科学和AI的数据产品之上，通过可复用决策逻辑在营销、数字体验、服务等场景保持一致，并借助治理机制支持从洞察到行动的闭环。该案例展示了在满足金融业速度、安全与合规要求的同时，实现超个性化客户体验的路径。文中强调与Databricks合作建设这一数据基础设施。","reason":"该案例展示了如何通过可复用数据产品与治理机制支撑规模化个性化和实时决策，对数据平台建设者具有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化","客户运营"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["Agent构建","方案封装与分发"],"decision_concerns":["权限与安全","可维护性与复用"]},"heat":25,"quality_score":56,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":56,"shelf":"evergreen","pinned":false,"published":"2026-09-01T21:30:00+08:00","first_seen":"2026-09-02T05:04:18.773327+08:00","original_url":"https://www.databricks.com/blog/how-discovery-bank-delivers-hyper-personalized-banking-scale-behavioral-ai-governed-data-and","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"d59935fed7ef","zh_title":"ClickHouse发布Agentic Analytics基准：28模型对比评测","zh_summary":"ClickHouse基于其内部分析Agent DWAINE的生产流量，构建了包含201个真实分析问题的基准，对28个模型（涵盖专有与开源权重）在正确性、成本和速度上进行评测，并发布了开源测试工具。该基准不同于传统Text-to-SQL，强调Agent自行发现schema、多轮交互以及以结果集为答案。文章还介绍了如何基于自己的数仓流量构建同类评测框架，帮助选择适合自身场景的模型。","reason":"数据从业者可借此了解分析型Agent的评测方法，并基于自身数仓复现基准来选择合适模型，而非依赖单一Text-to-SQL榜单。","category":"agent","category_label":"Data Agent","vendors":["ClickHouse","Hex"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":41,"quality_score":91,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":91,"shelf":"evergreen","pinned":false,"published":"2026-09-02T03:15:00+08:00","first_seen":"2026-09-02T05:04:18.773327+08:00","original_url":"https://clickhouse.com/blog/agentic-analytics-benchmark-data-agent-mnist","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"49b7c1960c22","zh_title":"Uken Games用ClickHouse替代Datadog，可观测性成本降低87%","zh_summary":"Uken Games 用基于 ClickHouse 的开源可观测性栈替代 Datadog，在单节点上存储全部 trace，每年成本降低 87%。该工作室监控 300 个容器、50+ EC2 机器和 100+ 服务部署，此前 Datadog 成本即使一再优化仍持续上涨。迁移后他们保留了产品分析层和技术可观测性层，并用于处理排行榜作弊争议等场景。","reason":"这是开源 OLAP 数据库替代高成本 SaaS 可观测性工具的典型案例，展示 ClickHouse 在日志与追踪场景的实时分析价值，对数据平台选型和成本优化有直接参考意义。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse","Datadog"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-09-01T23:28:24+08:00","first_seen":"2026-09-02T05:04:18.773327+08:00","original_url":"https://clickhouse.com/blog/uken-games-clickhouse-observability-stack","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"2621c2f3f508","zh_title":"用OpenSearch Agent Health观测与评估生产AI Agent","zh_summary":"本文介绍如何结合AWS与OpenSearch Agent Health，对生产环境中的AI Agent进行可观测性与评估。方案基于OpenTelemetry traces捕获Agent行为，并通过与期望行为对比的evals实现质量监控。文章演示了从部署Agent到构建可观测性数据管道的完整流程，并支持将Agent Health作为本地开发工具连接云资源。该实践为开发团队在软件生命周期中引入Agent专用的质量门禁提供了可操作路径。","reason":"生产级AI Agent的可观测性与评估是数据Agent落地中的关键工程问题，该文提供了基于OpenSearch的具体实现方案，值得数据平台与Agent建设者参考。","category":"agent","category_label":"Data Agent","vendors":["AWS","OpenSearch"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估"]},"heat":38,"quality_score":85,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-09-02T00:19:02+08:00","first_seen":"2026-09-02T05:04:18.773327+08:00","original_url":"https://aws.amazon.com/blogs/big-data/observing-and-evaluating-production-agents-using-opensearch-agent-health/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"402c6e3ce47a","zh_title":"用AWS DevOps Agent加速EMR上的Spark调试","zh_summary":"AWS 官方博客介绍如何将托管的 Apache Spark Troubleshooting Agent（MCP 服务器）注册为 AWS DevOps Agent 的自定义能力提供者，并通过 PrivateLink 确保私网连接。从一个聊天提示出发，Agent 可自主调查 EMR 上 Spark 作业失败，生成根因与修复计划，整个过程约两分钟。文章还指出内置 API 工具无法访问 Spark History Server 事件日志、执行器内存等内部工件，需借助 MCP 扩展弥补。它提供了完整的部署前置条件和集成步骤，适合数据团队参考。","reason":"Spark 作业失败排查是数据平台运维的高频痛点，本文展示了用 Agent 自动化根因分析的可行路径，可显著降低人工排查成本。","category":"agent","category_label":"Data Agent","vendors":["AWS","Amazon EMR"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估"]},"heat":41,"quality_score":90,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":90,"shelf":"evergreen","pinned":false,"published":"2026-09-02T00:06:44+08:00","first_seen":"2026-09-02T05:04:18.773327+08:00","original_url":"https://aws.amazon.com/blogs/big-data/accelerate-apache-spark-debugging-on-amazon-emr-with-aws-devops-agent/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"774466de20a5","zh_title":"Fivetran：开放数据基础设施加速工作流的六种方式","zh_summary":"Fivetran博客提出开放数据基础设施（ODI）是开放、基于标准的架构，可提升控制力、互操作性和AI就绪性。文章指出Salesforce、SAP等软件厂商的封闭数据策略加剧了数据迁移摩擦，而ODI将开放数据访问作为架构要求。开放表格式能帮助企业在扩展基础设施的同时控制成本，并支持AI代理等新工作负载。全文从数据访问、成本控制、可靠性等六个方面给出实践思路。","reason":"开放数据基础设施是数据平台演进的重要方向，Fivetran从数据集成厂商视角总结的实践方法，对构建AI-ready数据架构有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran"],"topics":["湖仓","平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-09-02T02:53:05+08:00","first_seen":"2026-09-02T05:04:18.773327+08:00","original_url":"https://www.fivetran.com/blog/6-ways-open-data-infrastructure-accelerates-your-workflows","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"d05ec7db74fa","zh_title":"应对数据驻留与隐私的复杂性","zh_summary":"文章指出企业面临从海量数据中提取洞察与满足数据驻留和隐私要求的双重挑战。数据驻留指数据存储的地理位置，影响合规、性能与成本；数据隐私则关注个人信息的收集、使用和治理。文章概述了企业在跨区域数据流动时需考虑的法律义务与安全策略，但未提供具体案例或数据。","reason":"数据平台与治理从业者需要理解数据驻留和隐私对架构选型及合规设计的基础约束，本文提供了清晰的框架性梳理。","category":"platform","category_label":"AI 数据平台","vendors":[],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":[],"decision_concerns":["权限与安全"]},"heat":18,"quality_score":40,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":40,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:56+08:00","first_seen":"2026-09-02T05:04:18.773327+08:00","original_url":"https://amplitude.com/blog/data-residency-and-privacy","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"b9a25258238e","zh_title":"ForeFlight 通过 Amplitude 清理数据杂乱，年省 15 万美元","zh_summary":"ForeFlight 因事件数据追踪缺乏可见性、重复事件泛滥，陷入数据治理困境，难以进行数据驱动决策并支付了高昂的超额费用。使用 Amplitude 后，他们清除了 67% 的数据杂乱，并建立全公司自助数据访问。该实践每年节省 15 万美元成本，同时让团队能更好地理解和服务用户。","reason":"数据治理和事件数据重复是数据团队常见痛点，本文给出了可量化的清理收益和自助分析落地路径，值得数据平台与治理实践者参考。","category":"platform","category_label":"AI 数据平台","vendors":["Amplitude","Twilio Segment","Tableau"],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据发现与搜索","自助分析"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":31,"quality_score":69,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":69,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:56+08:00","first_seen":"2026-09-02T05:04:18.773327+08:00","original_url":"https://amplitude.com/blog/how-foreflight-cleared-data-clutter","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"ec9f60f77f17","zh_title":"动态JSON负载下Apache Doris与ClickHouse等引擎对比","zh_summary":"文章针对AI Agent日志产生的宽表、动态JSON负载，比较Apache Doris、ClickHouse、Elasticsearch和OpenSearch在可预测延迟下的表现。内容聚焦这类新型数据在查询分析中的实际差异，并讨论不同引擎的适用场景。适合需要为Agent日志分析选择存储和查询引擎的数据团队参考。","reason":"AI Agent日志已成为新的数据分析负载，动态JSON处理能力直接影响可观测性和分析基础设施选型，值得数据平台从业者关注。","category":"platform","category_label":"AI 数据平台","vendors":["Apache Doris","ClickHouse","Elasticsearch","OpenSearch"],"topics":["平台AI化","实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-08-27T08:00:00+08:00","first_seen":"2026-09-02T05:04:18.773327+08:00","original_url":"https://doris.apache.org/blog/dynamic-json-in-agent-workloads-apache-doris-clickhouse-elasticsearch-and-opensearch/","items":[{"source":"Apache Doris Blog"}],"source_badge":"RSS"},{"event_id":"0628bd50a80c","zh_title":"PostgreSQL CDC到Apache Doris：一条SQL实现实时同步","zh_summary":"Apache Doris 推出原生 PostgreSQL CDC 能力，通过内置流式任务替代独立的 CDC、Kafka、Flink 或 Spark 组件，用户可用一条 SQL 完成实时数据同步。该方案简化了传统实时同步链路中的多组件部署与维护成本，适用于将 PostgreSQL 数据实时接入 Doris 进行分析的场景。","reason":"数据从业者可了解 Doris 原生 CDC 如何简化实时数据接入链路，对数据集成与实时分析架构选型有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Apache Doris"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入"],"decision_concerns":["可维护性与复用"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-08-21T08:00:00+08:00","first_seen":"2026-09-02T05:04:18.773327+08:00","original_url":"https://doris.apache.org/blog/postgresql-cdc-to-apache-doris-real-time-sync-with-one-sql-statement/","items":[{"source":"Apache Doris Blog"}],"source_badge":"RSS"},{"event_id":"bb6fe0f2d967","zh_title":"AQuA：让量化研究Agent持续进化并验证回测","zh_summary":"普林斯顿、蚂蚁集团和斯坦福团队提出AQuA系统，让量化研究Agent在假设、实验、验证的循环中递归自我改进。AQuA将数据路径和评价规则固定在循环之外，避免Agent把偶然高分或数据泄漏当作有效经验。实验显示，Part I在加密资产数据上取得约0.190的Spearman IC，Part II在美股预测上样本外Sharpe最高达+2.50。论文还记录了一次未被两个Agent发现的前视偏差，说明仅靠语义审查无法替代数据路径约束。","reason":"数据从业者应关注AQuA如何区分新证据与偶然高分，这对构建可靠、可溯源的自主分析Agent具有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["蚂蚁集团"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":["Agent构建"],"decision_concerns":["可靠性与评估","可维护性与复用"]},"heat":39,"quality_score":86,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":86,"shelf":"evergreen","pinned":false,"published":"2026-08-31T11:01:29+08:00","first_seen":"2026-09-01T13:09:18.346258+08:00","original_url":"https://www.qbitai.com/2026/08/481475.html","items":[{"source":"量子位"}],"source_badge":"RSS"},{"event_id":"c9ec1d90d337","zh_title":"构建理解产品分析语言的数据Agent","zh_summary":"Amplitude 官方博客介绍了构建数据 Agent 的冷启动难题：优秀分析师在写 SQL 前已掌握指标定义、实验分流、SDK 变更、过滤口径等上下文，而直接对数仓生成 SQL 的 AI 虽能快速返回精确数字，却可能因缺少业务语境而给出错误答案。为此 Amplitude 将客户日常使用中沉淀的事件、漏斗、群组、实验和分类定义结构化，供 Agent 复用。文章强调，Agent 要真正理解产品分析，不能只加速生成 SQL，而要把业务知识系统化接入。","reason":"数据从业者可从中看到：分析 Agent 的准确率不取决于 SQL 生成能力，而取决于业务上下文与语义层的工程化；本文给出了从现有分析资产构建 Agent 上下文的可行思路。","category":"agent","category_label":"Data Agent","vendors":["Amplitude"],"topics":["Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","知识与上下文"],"use_cases":["指标问答","Agent构建"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:56+08:00","first_seen":"2026-09-01T13:09:18.346258+08:00","original_url":"https://amplitude.com/blog/agents-understand-product-analytics","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"bd501c61d0f5","zh_title":"Amplitude发布AI分析智能体评测框架，四类任务得分76%","zh_summary":"Amplitude 联合其 AI 产品经理发布面向企业分析场景的 AI 智能体评测框架，将能力拆分为描述性、诊断性、预测性和规范性四类分析任务。其 Global Agent 综合得分 76%，相比六个月提升 7 倍以上，其中描述性 80%、诊断性 76%、预测性 63%、规范性 50%。文章还以仓库级 Text-to-SQL 最佳性能 9% 作为基线，展示智能体在多查询生产工作流上的优势。该框架为行业提供了可复用的评估语言，帮助团队区分营销话术与真实能力。","reason":"提供了一套可复用的AI分析智能体任务评测方法，并用具体分数和基线对比展示能力边界，对选型和自建评估有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["Amplitude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估"]},"heat":37,"quality_score":83,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":83,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:56+08:00","first_seen":"2026-09-01T13:09:18.346258+08:00","original_url":"https://amplitude.com/blog/ai-analytics-agents-task-based-evaluation","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"70a81e2b6a37","zh_title":"Amplitude如何用自家无代码工具做网站实验","zh_summary":"Amplitude增长团队分享使用自家Web Experimentation功能进行无代码A/B测试的实践。营销人员无需工程资源即可快速启动实验，并通过与Amplitude数据分析深度结合，更全面地理解访客行为，提升网站转化率与个性化体验。原文还总结了该工具适合快速迭代的小型测试，并介绍了从实施到运行的简便流程。","reason":"数据从业者可借鉴Amplitude将实验工具与行为分析打通的实践，理解无代码实验如何降低增长团队的测试门槛，对数据驱动转化优化有参考价值。","category":"product","category_label":"数据产品","vendors":["Amplitude"],"topics":["销售增长"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案"],"use_cases":["自助分析"],"decision_concerns":["用户采用与业务价值"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-09-01T07:50:56+08:00","first_seen":"2026-09-01T13:09:18.346258+08:00","original_url":"https://amplitude.com/blog/amplitude-team-web-experimentation","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"0980eee65ba0","zh_title":"什么是AI Copilot？企业团队的效率与局限","zh_summary":"文章介绍AI Copilot在企业应用中的核心价值：通过生成草稿、自然语言转SQL和仪表盘，显著提升例行任务速度；GitHub 2024年研究显示，使用Copilot的开发者完成受控编码任务快55%。同时，它降低了数据访问门槛，业务用户可分钟级获得答案，并借助模板和元数据提升输出一致性。文章也提醒，Copilot存在幻觉和准确性风险，过度依赖可能导致技能退化，需人工审查。","reason":"AI Copilot正在改变数据访问与分析工作流，理解其能力边界和风险，有助于数据团队评估引入策略并设计人工审查机制。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["ChatBI","Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","知识与上下文"],"use_cases":["指标问答","自助分析"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":19,"quality_score":43,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":43,"shelf":"evergreen","pinned":false,"published":"2026-08-29T06:22:15+08:00","first_seen":"2026-09-01T06:52:29.940791+08:00","original_url":"https://www.databricks.com/blog/ai-copilot","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"729c4b318a8b","zh_title":"用UBI与SRW度量改进OpenSearch搜索质量","zh_summary":"本文介绍在Amazon OpenSearch Service上使用User Behavior Insights（UBI）开放标准捕获搜索行为，并用Search Relevance Workbench（SRW）评估搜索质量。查询日志只能记录用户输入，无法反映用户看到、选择或离开的原因；文章给出收集信号、生成相关性判断、上线前验证的闭环框架。这是系列文章的第一部分，后续将讨论端到端自动化。","reason":"搜索质量评估是数据产品中的常见难题，UBI+SRW提供了可复制的信号采集与度量框架，对做搜索、推荐或数据产品评估的从业者有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon OpenSearch Service"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-09-01T05:13:36+08:00","first_seen":"2026-09-01T06:52:29.940791+08:00","original_url":"https://aws.amazon.com/blogs/big-data/measuring-and-improving-search-quality-with-amazon-opensearch-service/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"0d7185877bfa","zh_title":"Snowflake Postgres：从OLTP到分析的无ETL实战指南","zh_summary":"Snowflake Postgres 是运行在 Snowflake 账户内的全托管 PostgreSQL 18 服务，支持 Data Mirroring 实现亚分钟级 CDC 持续复制，并可通过 pg_lake 将数据导出为 Apache Iceberg 表到客户自有 S3。文章用电商场景的端到端 POC，演示了创建实例、配置网络策略、构建 schema、启用连续复制、查询 $CHANGES/$LIVE 对象等完整流程。所有代码均来自真实实现，强调无需管理基础设施、无需外部 CDC 连接器，且数据格式开放、无厂商锁定。","reason":"数据从业者可借此了解 Snowflake 将 OLTP 与分析打通的 Zero-ETL 路径，以及用 Apache Iceberg 保持开放格式的具体做法，对评估托管 PG 与湖仓集成有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["湖仓","实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":39,"quality_score":87,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":87,"shelf":"evergreen","pinned":false,"published":"2026-08-31T22:01:04+08:00","first_seen":"2026-09-01T06:52:29.940791+08:00","original_url":"https://medium.com/snowflake/snowflake-postgres-zero-etl-from-oltp-to-analytics-1d9117c9f8c8?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"cc5c540a68f6","zh_title":"从数据格式到完整引擎：2026数据库系统演进趋势与TDSQL实践","zh_summary":"该内容来自腾讯云数据库 DBTalk，围绕2026年数据库系统演进趋势展开，提出从数据格式到完整引擎的发展方向。文中结合腾讯云 TDSQL 的实践，展示了数据库系统如何为下一代数据应用提供基础能力。对关注数据基础设施选型与数据库技术演进的从业者具有参考价值。","reason":"数据库系统从格式到引擎的演进决定上层数仓与AI数据平台的能力边界，TDSQL实践能帮助从业者评估自身技术路线。","category":"platform","category_label":"AI 数据平台","vendors":["腾讯云"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":33,"quality_score":74,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"evergreen","pinned":false,"published":"2026-08-28T20:07:33+08:00","first_seen":"2026-08-31T09:43:36.689819+08:00","original_url":"https://www.infoq.cn/video/7Idl1NaRyb6MPku1W1Vv?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"797acf2223dd","zh_title":"AI Agent评估信号：首次正面体验带来3倍留存","zh_summary":"Calibre与Amplitude对2万+资深用户分析Amplitude Global Agent使用数据，发现老用户的eval得分与留存基本无关，坏会话不会赶走他们，好会话也不会留住他们。对新用户则相反：首次会话是否正向并保存Agent输出，是预测后续留存的最强信号。首周体验严格正面的用户，长期留存是触发过任一失败标志用户的3倍。","reason":"揭示了AI Agent评估指标与用户留存之间的非线性关系，提醒数据从业者不要只盯会话内eval，而要关注首次体验对长期业务价值的影响。","category":"insight","category_label":"AI分析","vendors":["Amplitude"],"topics":["客户运营"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["生产评估与运营"],"decision_concerns":["用户采用与业务价值","可靠性与评估"]},"heat":43,"quality_score":95,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":95,"shelf":"evergreen","pinned":false,"published":"2026-08-29T01:10:28+08:00","first_seen":"2026-08-31T08:07:12.262881+08:00","original_url":"https://amplitude.com/blog/the-eval-signal-that-predicts-3x-agent-retention","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"324abe85aa2a","zh_title":"把洞察交给产品经理，销售额提升53%","zh_summary":"印度保险科技公司ACKO通过Amplitude分析，把洞察交到产品经理手中，使销售额提升53%。在健康险交叉销售活动中，折扣使交叉销售率提升41%，并证明折扣优化收益而非侵蚀营收。Cricket World Cup广告活动期间，实时仪表盘与多角度数据分析帮助团队将旅程内错误率降低64%。","reason":"展示真实业务场景中自助分析与实时看板如何直接驱动销售与运营改进，对数据产品落地和业务价值衡量有参考意义。","category":"insight","category_label":"AI分析","vendors":["Amplitude"],"topics":["销售增长","客户运营"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["自助分析","看板与报告"],"decision_concerns":["用户采用与业务价值"]},"heat":33,"quality_score":74,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"evergreen","pinned":false,"published":"2026-08-29T01:10:18+08:00","first_seen":"2026-08-31T08:07:12.262881+08:00","original_url":"https://amplitude.com/blog/acko-amplitude-user-insights","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"562907be2c5e","zh_title":"罗氏Agentic Analytics实战：AI试点失败源于领导力未定运营模式","zh_summary":"罗氏工程负责人Yannick Misteli在伦敦Agentic Analytics Playbook活动上表示，多数AI试点停滞并非技术和预算问题，而是领导层没有回答试点之后的归属、治理与风险容忍度。罗氏拥有10万多名员工、在25+个国家受严格监管，若能规模化落地Agentic Analytics，将打破“必须小团队才能做”的借口。罗氏将AI治理、安全与血缘视为不可妥协，但在完整性和延迟上接受取舍，因此报表采用夜间批处理而非实时。其建议是在扎实基础上“小步启动、大胆思考、快速迭代”。","reason":"大型受监管药企的Agentic Analytics规模化经验，直接回应AI试点无法转生产的普遍痛点，为数据团队提供了治理与取舍的落地参考。","category":"agent","category_label":"Data Agent","vendors":["ThoughtSpot"],"topics":["Data Agent","组织人才"],"product_ids":["thoughtspot"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理","报表与可视化"],"use_cases":["生产评估与运营","看板与报告"],"decision_concerns":["权限与安全","成本与性能"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-29T09:55:58+08:00","first_seen":"2026-08-31T05:07:17.626819+08:00","original_url":"https://www.thoughtspot.com/blog/how-roche-operationalized-ai-pilots-agentic-analytics-playbook","items":[{"source":"ThoughtSpot Blog"}],"source_badge":"RSS"},{"event_id":"afa110f519ff","zh_title":"Thinking Machines将任务专长融入RL，Text-to-SQL达SOTA","zh_summary":"Thinking Machines的研究团队将任务专业知识引入强化学习，在Text-to-SQL任务上取得当前最优（SOTA）结果。他们发现现有Text-to-SQL训练数据噪声极大，并从BIRD Train中采样了2.5k实例。该工作对提升Text-to-SQL准确性和构建可靠数据问答Agent具有参考价值。","reason":"Text-to-SQL是ChatBI/Data Agent的核心技术路径，该研究展示了用RL注入任务专长突破SOTA，值得数据Agent开发者关注。","category":"agent","category_label":"Data Agent","vendors":["Thinking Machines"],"topics":["ChatBI","Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["Agent构建"],"decision_concerns":["准确性与语义一致性"]},"heat":40,"quality_score":80,"trend_score":7,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-08-30T00:14:16.367000+08:00","first_seen":"2026-08-31T05:07:17.626819+08:00","original_url":"https://bsky.app/profile/sungkim.bsky.social/post/3muabi5nil22v","items":[{"source":"Bluesky 数据社区"}],"source_badge":"Bluesky"},{"event_id":"8feab1f0fa88","zh_title":"从工单到产品真相：用支持数据驱动产品改进","zh_summary":"客服支持工单中蕴含着产品问题的早期信号，但常被埋没在非结构化对话和分散系统中。文章提出，将支持对话与真实行为数据结合，可以帮助产品团队更早发现客户摩擦、优先处理高影响修复，并建立持续改进闭环。作者认为，CX与产品团队紧密协作能把工单从被动解决转变为战略产品情报，最终减少工单量、改善体验并加速产品迭代。","reason":"数据从业者可借鉴如何将非结构化支持数据转化为可指导产品决策的信号，是一套可复用的数据产品方法论。","category":"product","category_label":"数据产品","vendors":[],"topics":["客户运营"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["用户采用与业务价值"]},"heat":23,"quality_score":52,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":52,"shelf":"evergreen","pinned":false,"published":"2026-08-29T01:10:28+08:00","first_seen":"2026-08-30T20:00:59.261573+08:00","original_url":"https://amplitude.com/blog/support-data-powers-better-products","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"fb6358d08535","zh_title":"Anthropic经济指数：AI采用的地理与企业不均","zh_summary":"Anthropic经济指数报告显示，美国已有40%员工在工作中使用AI，较两年前的20%翻倍，采用速度明显快于电力、PC和互联网等历史技术。报告首次结合Claude.ai对话的地理分布与企业API使用数据，分析AI在不同地区和企业任务中的扩散。早期采用呈地理集中和企业内少数任务集中的特征，但AI扩散的时间线比20世纪技术更短、强度更高。企业可据此评估AI落地节奏与区域差异，为运营重构提供参考。","reason":"数据从业者可从中了解企业AI采用的真实分布和扩散速度，有助于判断数据Agent/分析类产品在市场渗透和客户推进中的时机与重点。","category":"insight","category_label":"AI分析","vendors":["Anthropic","Claude"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["用户采用与业务价值"]},"heat":40,"quality_score":89,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":89,"shelf":"evergreen","pinned":false,"published":"2026-08-26T00:13:14+08:00","first_seen":"2026-08-30T09:28:58.645826+08:00","original_url":"https://www.anthropic.com/research/anthropic-economic-index-september-2025-report","items":[{"source":"Anthropic Economic Index"}],"source_badge":"官网"},{"event_id":"4fa13c7cd30d","zh_title":"如何做好任务管理：从任务入池到验收复盘","zh_summary":"DeepSeek Harness 将 Agent 运行带入“调度”议题；从8月17日起 DeepSeek API 实行峰谷定价，同一任务不同时段执行价格可差一倍。文章提出 AI 任务管理六步法：入池、分级、排队、执行、验收、复盘，强调先建任务台账与执行记录两张关联表，并为每类任务写明截止时间、交付物和责任人。适合产品团队据此构建可落地的调度规则，让 AI 任务真正高效运转。","reason":"当 AI Agent 从原型走向生产，任务调度、成本与验收是数据平台和 Agent 落地必须解决的问题；此文给出了可执行的管理框架，值得数据从业者参考。","category":"product","category_label":"数据产品","vendors":["DeepSeek"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-08-29T13:52:53+08:00","first_seen":"2026-08-30T09:28:58.645826+08:00","original_url":"https://www.woshipm.com/ai/6454995.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"185ee6eef27b","zh_title":"云原生数据库到数据基础设施：架构、弹性与智能化演进","zh_summary":"腾讯云数据库DBTalk分享云原生数据库向数据基础设施的演进，重点讨论架构设计、弹性能力与智能化方向。内容反映数据库在数据平台中的角色变化，涉及技术实践与趋势判断。适合关注数据基础设施演进的从业者参考。","reason":"数据从业者可借此了解云原生数据库如何融入数据基础设施，以及弹性与智能化带来的架构选择，对规划数据平台有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["腾讯云"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":18,"quality_score":40,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":40,"shelf":"evergreen","pinned":false,"published":"2026-08-28T20:31:09+08:00","first_seen":"2026-08-30T09:28:58.645826+08:00","original_url":"https://www.infoq.cn/video/gaAV7GRNCXWITqLRGu0H?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"6597afea514d","zh_title":"TOTVS：为AI代理构建数据层——从事务系统到MCP与语义模型","zh_summary":"TOTVS数据架构负责人Fabiane Nardon分享为企业级AI代理准备数据的实践经验。她指出事务系统和数据湖的数据都未针对代理访问优化，需结合确定性逻辑与LLM非确定性推理，平衡精度、安全与成本。具体方法包括采用数据网格、低延迟数据库架构、语义本体，以及动态MCP工具选择来优化上下文窗口并降低token开销。TOTVS为巴西最大科技公司之一，约四分之一的巴西GDP经由其系统运行。","reason":"面向AI代理的数据架构设计是Data Agent落地的关键工程问题，演讲给出从事务系统到语义层/MCP的完整思路，对构建企业级数据Agent的从业者有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["TOTVS"],"topics":["Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","知识与上下文"],"use_cases":["Agent构建","数据接入"],"decision_concerns":["准确性与语义一致性","成本与性能"]},"heat":36,"quality_score":79,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":79,"shelf":"evergreen","pinned":false,"published":"2026-08-29T19:00:00+08:00","first_seen":"2026-08-30T04:56:58.190412+08:00","original_url":"https://www.infoq.com/presentations/enterprise-data-architecture-ai-agents/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"6dc4e96e1ba7","zh_title":"Strava采用Amplitude自助分析，效率提升3倍","zh_summary":"Strava增长分析团队曾因平台复杂而集中处理所有数据查询，产品经理等待答案最长需两周。转向Amplitude后，团队采用自助分析模型，分析师效率提升3倍，到2025年初累计节省约10万美元成本。该实践展示了降低分析门槛对业务响应速度的显著价值。","reason":"数据从业者可借鉴Strava从集中式查询转向自助分析的实际路径与量化收益，是BI平台落地价值的典型案例。","category":"bi","category_label":"BI 与可视化","vendors":["Amplitude"],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["自助分析","看板与报告"],"decision_concerns":["用户采用与业务价值","成本与性能"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-08-29T01:10:28+08:00","first_seen":"2026-08-30T04:56:58.190412+08:00","original_url":"https://amplitude.com/blog/strava-analytics-efficiency","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"b1206f2af34f","zh_title":"如何平衡AI Agent推理成本与用户体验","zh_summary":"Amplitude 官方博客记录了其 Global Agent 从 Claude Sonnet 4.6 切换到 Gemini 3 Flash 的受控实验：会话成本从 $4.88 降至 $2.33（-52.3%），端到端延迟从 63.8s 升至 119.7s（+87.7%），平均消息数下降 10%，有效行动转化率基本持平（30.4% vs 29.98%）。团队利用 Agent Analytics 和 Feature Experimentation 在三天内完成了成本与体验的权衡决策。文章还讨论了为何厂商基准无法替代生产流量下的实验。对数据从业者而言，这是一套可复用的 Agent 生产评估方法。","reason":"数据从业者应关注：这篇提供了 AI Agent 在生产环境中成本与体验权衡的可复用实验框架，并给出了具体指标和决策流程，比单纯模型选型建议更有可操作性。","category":"insight","category_label":"AI分析","vendors":["Amplitude"],"topics":["财务经营","客户运营"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能","用户采用与业务价值"]},"heat":43,"quality_score":95,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":95,"shelf":"evergreen","pinned":false,"published":"2026-08-29T03:56:08+08:00","first_seen":"2026-08-29T15:05:44.929994+08:00","original_url":"https://amplitude.com/blog/agent-analytics-beta","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"a0a2d1d1e7b2","zh_title":"超越招聘：如何培养一支蓬勃发展的数据团队","zh_summary":"文章来自Amplitude数据产品增长总监的一线实践分享，指出招聘合适的人只是开始，更要为分析师创造持续成长和投入工作的条件。作者建议以行动为导向沟通分析结果，优先清晰可执行而非技术复杂度，并持续给团队新挑战，避免重复分析带来的倦怠。同时强调赋能业务部门自助分析，让分析师专注复杂问题，并给予分析师自主权以建立信任和激发动力。整体是一篇关于数据团队长期发展与价值落地的管理方法论。","reason":"数据团队管理者可借鉴如何避免分析师倦怠、提升分析成果的行动力，也体现数据分析岗位在组织中持续发挥价值的关键条件。","category":"product","category_label":"数据产品","vendors":["Amplitude","HubSpot"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["自助分析"],"decision_concerns":["用户采用与业务价值"]},"heat":25,"quality_score":55,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":55,"shelf":"evergreen","pinned":false,"published":"2026-08-29T01:10:28+08:00","first_seen":"2026-08-29T15:05:44.929994+08:00","original_url":"https://amplitude.com/blog/cultivate-thriving-data-team","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"723c65c45ba9","zh_title":"Prisma ORM与TiDB Serverless设置指南","zh_summary":"TiDB Cloud官方博客介绍如何在AI应用中用Prisma ORM连接TiDB。内容强调TiDB兼容MySQL，现有schema可无缝使用，并推荐通过@tidbcloud/prisma-adapter走HTTPS查询以满足serverless/edge环境，同时说明迁移和introspection仍需TCP连接。还针对AI应用的数据建模给出主键和索引设计建议。","reason":"面向数据从业者提供了Prisma连接TiDB的完整技术路径和serverless环境下的关键限制，对AI应用的数据建模有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["PingCAP","TiDB","Prisma"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案"],"use_cases":["数据接入"],"decision_concerns":["可维护性与复用"]},"heat":33,"quality_score":74,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":74,"shelf":"evergreen","pinned":false,"published":"2026-08-29T00:44:33+08:00","first_seen":"2026-08-29T15:05:44.929994+08:00","original_url":"https://www.pingcap.com/blog/integrating-tidb-cloud-serverless-driver-prisma-orm/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"fb81aeaf8e1a","zh_title":"Anthropic经济指数：Claude 3.7使用数据揭示AI对劳动力市场影响","zh_summary":"Anthropic发布第二期经济指数报告，基于Claude 3.7 Sonnet发布后11天内的100万条匿名Claude.ai对话，分析AI对劳动力市场的影响。结果显示，编程及教育、科学、医疗类用途占比上升；增强式思考模式主要用于技术任务。报告还发布了按任务和职业划分的增强/自动化分解数据，以及涵盖630个细分类别的Claude.ai使用分类法，数据集免费开放下载。","reason":"数据从业者可利用这份大规模真实AI使用行为数据，理解AI在各职业中的增强与自动化边界，为数据产品设计和劳动力规划提供实证依据。","category":"insight","category_label":"AI分析","vendors":["Anthropic","Claude"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":45,"quality_score":91,"trend_score":7,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":91,"shelf":"evergreen","pinned":false,"published":"2026-08-26T00:13:14+08:00","first_seen":"2026-08-29T06:20:40.285450+08:00","original_url":"https://www.anthropic.com/news/anthropic-economic-index-insights-from-claude-sonnet-3-7","items":[{"source":"Anthropic Economic Index"},{"source":"Anthropic Economic Index"}],"source_badge":"官网"},{"event_id":"1590ce86fc2a","zh_title":"Databricks Genie One新增桌面应用与文档协作，推动洞察转化为行动","zh_summary":"Databricks 在 Data + AI Summit 后持续更新 Genie One，新增原生桌面应用，支持全局启动器，并可在桌面端使用文档、技能、定时任务及 Genie Agents 和 Databricks Apps。Genie One 的文档功能也得到增强，用户可直接在对话中起草、修订和评论文档，并通过链接共享，减少上下文切换。这些更新旨在让用户获得 AI 答案后，能更快地完成验证、包装和协作流程，将洞察转化为实际业务行动。","reason":"数据从业者关注 ChatBI 产品演进时，这是领先平台将问答能力延伸至工作流和协作闭环的最新实践，便于评估 Data Agent 的落地形态。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["ChatBI","Data Agent"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","报表与可视化"],"use_cases":["指标问答","Agent构建"],"decision_concerns":["用户采用与业务价值"]},"heat":32,"quality_score":71,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":71,"shelf":"news","pinned":false,"published":"2026-08-29T05:00:00+08:00","first_seen":"2026-08-29T06:20:40.285450+08:00","original_url":"https://www.databricks.com/blog/beyond-answers-new-genie-one-features-turn-insights-action","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"c90518881d01","zh_title":"Trackunit用Databricks构建IrisX，将建筑数据转化为决策","zh_summary":"建筑行业数据分散在设备遥测、维修记录、工地文档和租赁流中，形成数据智能挑战。Trackunit 基于 Databricks 数据与AI平台打造运营数据平台 IrisX，通过 connect、distill、amplify 三种能力，将原始机器数据转化为运营决策与企业智能。其背景包括20年行业经验、5000家客户、覆盖120个国家的600万台互联设备，以及1200个连接器和150个合作伙伴应用。文中由 Trackunit 与 Databricks 专家共同分享该平台的构建经验。","reason":"数据从业者可从中看到垂直行业如何用统一数据平台整合碎片化数据并补齐运营上下文，而非停留在单点AI能力；对建设行业数据平台有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","Trackunit"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"ai-platform","label":"AI 数据平台","priority":1,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","知识与上下文"],"use_cases":["数据接入"],"decision_concerns":["准确性与语义一致性","用户采用与业务价值"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-08-29T01:30:00+08:00","first_seen":"2026-08-29T06:20:40.285450+08:00","original_url":"https://www.databricks.com/blog/how-trackunit-turns-construction-data-decisions-ai","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"f72942ffb967","zh_title":"Indra在Databricks上统一EV充电数据","zh_summary":"英国EV充电公司Indra在数据快速增长后，将原先分散在Cosmos DB、Synapse、Power BI等多项服务中的数据整合到Databricks单一平台。通过并行原型迁移、月度Delta表和Unity Catalog实现统一治理，并借助AI/BI仪表盘与Genie Agent让业务团队自助获取数据答案。该实践减少了工具数量和运维成本，提升了数据标准化与可治理性。","reason":"数据从业者可借鉴多工具数据栈向统一湖仓平台迁移的路径，以及如何通过治理和AI/BI自助分析释放数据价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","Microsoft"],"topics":["湖仓"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据接入","自助分析"],"decision_concerns":["成本与性能","用户采用与业务价值"]},"heat":33,"quality_score":73,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":73,"shelf":"evergreen","pinned":false,"published":"2026-08-29T01:30:00+08:00","first_seen":"2026-08-29T06:20:40.285450+08:00","original_url":"https://www.databricks.com/blog/how-indra-unified-ev-charging-data-databricks","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"1659453556d9","zh_title":"HR Tech中AI失败的三大结构性原因","zh_summary":"HR科技领导者承受着交付AI而非评估AI的压力，但多数项目在进入生产前就停滞，根因不在模型，而在底层人员数据。Gartner报告显示60%的AI项目因缺乏AI就绪数据而被放弃，商业分析中心发现90%的AI项目在分析不成熟的组织中失败。文章指出三大结构性问题：不可信的数据、拖慢上线的复杂性、以及超出规划的成本，并涉及Workday、SAP、Snowflake等数据链路。","reason":"数据从业者能从中看到HR AI项目失败的数据层根因，对数据治理、平台建设和AI落地优先级有参考价值。","category":"product","category_label":"数据产品","vendors":["Visier","Workday","SAP","Snowflake"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["准确性与语义一致性","成本与性能"]},"heat":28,"quality_score":63,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":63,"shelf":"evergreen","pinned":false,"published":"2026-08-10T08:00:00+08:00","first_seen":"2026-08-29T06:20:40.285450+08:00","original_url":"https://www.visier.com/blog/why-ai-in-hr-tech-fails/","items":[{"source":"Visier Blog"}],"source_badge":"RSS"},{"event_id":"4309cc7b0aec","zh_title":"QuintoAndar 用 ClickHouse 统一 9 亿月事件并兼容 Postgres 生态","zh_summary":"QuintoAndar 是拉丁美洲最大住房平台，其 CDP 团队在 ClickHouse Cloud 上统一每月约 9 亿条原始事件。他们使用 ClickHouse Managed Postgres 让 Hightouch 及其他 Postgres 兼容工具直接访问这些数据，替代了原先 Lambda 架构中由 Databricks 处理的冷层和自建 Postgres 热层。","reason":"该实践展示了如何通过托管 Postgres 兼容层打通 ClickHouse 与现有工具生态，对统一数据平台和降低集成成本有直接借鉴价值。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse","Hightouch","Databricks"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["可维护性与复用"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-08-27T08:00:00+08:00","first_seen":"2026-08-29T06:20:40.285450+08:00","original_url":"https://clickhouse.com/blog/quintoandar-managed-postgres","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"58f6eefe19db","zh_title":"Razor Group在AWS上构建现代数据湖仓实践","zh_summary":"Razor Group作为欧洲领先电商聚合商，运营250多个品牌，年收入超4亿美元。其自研平台ROS每月处理超3.7亿次API调用，通过9,300多条数据管道将市场信号转化为自动化行动。本文介绍了该公司从Amazon Redshift迁移至AWS湖仓架构的决策、分阶段迁移路径及业务成果，并重点讨论了工作负载争用、成本优化和多引擎灵活性等问题。","reason":"该文是典型的数据平台架构升级实战，涉及湖仓迁移、工作负载优化和成本控制，对数据平台团队有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon Redshift","Tableau","Apache Airflow"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["成本与性能"]},"heat":39,"quality_score":86,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":86,"shelf":"evergreen","pinned":false,"published":"2026-08-29T00:25:02+08:00","first_seen":"2026-08-29T06:20:40.285450+08:00","original_url":"https://aws.amazon.com/blogs/big-data/razor-groups-journey-to-a-modern-data-lakehouse-on-aws/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"ef728d771871","zh_title":"Fivetran：两年后，AI如何改变性能工程","zh_summary":"Fivetran 团队复盘两年用 AI 做性能工程的实践：过去跑通一个性能优化想法需两三天，现在借助 AI 检索与综合日志、代码上下文只需数小时。评估成本骤降后，即使单个方案只提升 5%，长尾优化也值得投入。团队还强调写代码前先用生产日志估算影响面，再决定是否实施。","reason":"数据从业者可从中看到 AI 如何显著降低工程评估成本，理解性能优化从“挑高价值点子”转向“低成本试错长尾”的工作方式变化。","category":"insight","category_label":"AI分析","vendors":["Fivetran"],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":33,"quality_score":73,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":73,"shelf":"evergreen","pinned":false,"published":"2026-08-29T06:09:05+08:00","first_seen":"2026-08-29T06:20:40.285450+08:00","original_url":"https://www.fivetran.com/blog/how-ai-changed-performance-engineering-2-years-later","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"f62fc670d258","zh_title":"AI时代数据分析学习路线：贴近业务+指挥AI","zh_summary":"文章指出传统Excel/SQL/Python/PowerBI全栈学习路线在AI时代已不适用，主张数据分析师贴近业务流程练分析思维，用标准化指令指挥AI取数，并借助AI学习统计学等复杂理论。具体从指标体系梳理、分析思路练习、取数方式升级、理论强化四方面给出成长路径。全文保留了PowerBI等工具名，适合数据从业者参考。","reason":"为数据从业者提供了AI时代技能升级的实操路线，区别于泛AI讨论，强调业务分析与AI协作，具有方法参考价值。","category":"product","category_label":"数据产品","vendors":["PowerBI"],"topics":["数据人"],"product_ids":[],"focus":{"id":"ai-analysis","label":"AI 数据分析","priority":3,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":33,"quality_score":73,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":73,"shelf":"evergreen","pinned":false,"published":"2026-08-28T14:19:56+08:00","first_seen":"2026-08-29T06:20:40.285450+08:00","original_url":"https://www.woshipm.com/share/6455975.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"94457c5e8a92","zh_title":"圆桌讨论：研究型人才培养与数据库未来发展方向","zh_summary":"这是一场关于研究型人才培养与数据库未来发展的圆桌讨论。内容围绕数据库领域如何培养研究型人才以及未来技术方向展开。具体观点与细节需查看原文。","reason":"数据库是数据基础设施的核心，关于人才培养与未来方向的讨论有助于从业者把握技术趋势与职业路径。","category":"product","category_label":"数据产品","vendors":[],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":5,"quality_score":10,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":10,"shelf":"evergreen","pinned":false,"published":"2026-08-29T00:55:25+08:00","first_seen":"2026-08-29T06:20:40.285450+08:00","original_url":"https://www.infoq.cn/video/kJ0ARKZePg80FpGY1J3Y?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"d199550f2126","zh_title":"数据库测试、测评：进展与展望","zh_summary":"腾讯云数据库 DBTalk 以“数据库测试、测评：进展与展望”为主题，围绕数据库测试领域的最新进展展开。文章面向数据从业者，探讨测试方法论与测评体系的发展方向，具体内容需点击原文查看。","reason":"数据库测试与测评直接影响选型和可靠性判断，腾讯云的一线实践视角对数据从业者有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["腾讯云"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估"]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"evergreen","pinned":false,"published":"2026-08-29T00:35:03+08:00","first_seen":"2026-08-29T06:20:40.285450+08:00","original_url":"https://www.infoq.cn/video/SD7eGfAXrr5K0spls5LO?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"ae59d5e45ca4","zh_title":"统一技能仓库：数据团队如何向AI编码代理传递代码规范","zh_summary":"该文介绍数据团队如何用一个中央技能仓库，向Claude Code、GitLab Duo、OpenCode和Snowflake CoCo五个AI编码代理统一传递团队约定。团队五位工程师各有偏好，但代理默认生成的Python代码因不了解CI规则而失败。团队将原本分散在手册、资深工程师经验和评审评论中的知识，集中到仓库中并像代码一样管理，使各AI工具都能消费同一套规范。","reason":"AI编码代理在数据团队中越来越普及，但如何让不同代理遵守团队特有规范是关键痛点；本文给出了可复用的中央技能仓库方法，值得数据工程团队参考。","category":"product","category_label":"数据产品","vendors":["Snowflake"],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["可维护性与复用","可靠性与评估"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-08-29T05:01:01+08:00","first_seen":"2026-08-29T06:20:40.285450+08:00","original_url":"https://medium.com/snowflake/one-skills-repo-every-ai-agent-how-our-data-team-ships-its-conventions-to-claude-code-gitlab-1fe42bd7c824?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"bb69209c8d0f","zh_title":"用Git管理Openflow流程组：从画布到Dev/Prod的版本控制","zh_summary":"Snowflake Openflow（基于Apache NiFi的托管服务）将流程组（Process Group）接入Git，支持分支、提交、Diff与PR评审。文章针对图形化Pipeline导出再导入的三类问题（运行时状态丢失、无法Diff、手工操作），给出从GitHub裸仓库到Dev/Prod环境提升的完整配置，包含画布生成的JSON、feature-branch工作流及父子Parameter Context设置。","reason":"可视化数据流也需要代码级版本控制与CI/CD时，这套Git-backed流程提供了可复用的工程范式，可改善多环境交付的一致性与可审计性。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案"],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["可维护性与复用","可靠性与评估"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-08-29T05:01:01+08:00","first_seen":"2026-08-29T06:20:40.285450+08:00","original_url":"https://medium.com/snowflake/treating-openflow-like-code-a-git-backed-workflow-for-process-groups-215fd46ad2bd?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"14238297ec97","zh_title":"自动驾驶治理：用血缘自动化数据治理（Google Cloud）","zh_summary":"Google Cloud 介绍了 Governance Agent 项目，基于 Knowledge Catalog、BigQuery 和列级血缘，将上游表已文档化、已标记、可信的元数据自动传播到下游视图，避免每个下游表重复手工治理。文章指出现有治理工具多为事后扫描，治理债务成为数据团队日常成本。该方案将治理从审计转向后台持续更新。","reason":"数据从业者可从治理自动化思路中获得减少元数据维护成本、提升下游数据可信度的可落地方法。","category":"platform","category_label":"AI 数据平台","vendors":["Google","Google Cloud"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理","数据资产"],"use_cases":["数据发现与搜索","生产评估与运营"],"decision_concerns":["可维护性与复用","权限与安全"]},"heat":32,"quality_score":71,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":71,"shelf":"evergreen","pinned":false,"published":"2026-08-18T08:00:00+08:00","first_seen":"2026-08-29T06:20:40.285450+08:00","original_url":"https://cloud.google.com/blog/products/data-analytics/governance-on-autopilot-automate-data-governance-with-lineage","items":[{"source":"Google Cloud Data Analytics Blog"}],"source_badge":"RSS"},{"event_id":"e6e46cfe5599","zh_title":"Malachyte用实时AI重塑零售推荐，破解冷启动难题","zh_summary":"Malachyte是一家AI电商推荐平台，利用Google Cloud的Bigtable和托管Kafka构建实时AI方案，解决零售推荐中冷启动用户的问题。其基于注意力机制的神经网络模型可建模客户交互序列，已帮助部分零售商销售额翻倍甚至三倍增长。","reason":"展示了如何用托管实时数据基础设施支撑AI推荐场景，对关注数据平台与实时分析实践的数据从业者有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Google","Google Cloud","Malachyte"],"topics":["实时分析","销售增长"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案"],"use_cases":["数据接入"],"decision_concerns":["用户采用与业务价值"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-10T08:00:00+08:00","first_seen":"2026-08-29T06:20:40.285450+08:00","original_url":"https://cloud.google.com/blog/products/data-analytics/solving-retails-cold-start-problem-malachytes-recommendation-reinvention","items":[{"source":"Google Cloud Data Analytics Blog"}],"source_badge":"RSS"},{"event_id":"5d62b7c6659d","zh_title":"企业智能体如何转化为组织生产力","zh_summary":"爱分析对话神州数码AI产品部总经理，探讨企业智能体进入核心流程时平台、知识治理与行业经验的作用。文章指出，同样的场景、文档和基础模型，在不同平台上搭建的智能体效果悬殊，平台对业务流程和企业知识的处理能力成为可用性分水岭。企业智能体只有进入需求、执行、审核、交付组成的连续流程，才能从个人工具变为流程中的调度和执行力量。知识治理成熟度决定企业AI拐点，持续进入系统的数据和专家反馈才能让智能体越用越好。","reason":"数据从业者可从中理解企业智能体从单点工具走向组织级流程的关键挑战，以及平台、知识与治理协同的落地思路。","category":"agent","category_label":"Data Agent","vendors":["神州数码"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":["Agent构建"],"decision_concerns":["可维护性与复用","用户采用与业务价值"]},"heat":34,"quality_score":76,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":76,"shelf":"evergreen","pinned":false,"published":null,"first_seen":"2026-08-28T19:13:09.529506+08:00","original_url":"https://www.ifenxi.com/research/content/6908","items":[{"source":"爱分析"}],"source_badge":"RSS"},{"event_id":"b219fb4a4304","zh_title":"你的企业有清晰的B2B产品分析策略吗？","zh_summary":"文章指出，虽然消费级SaaS的“消费化”影响企业软件，但B2B产品在KPI定义上仍缺乏共识：NPS、留存、流失等指标在年度预付合同和大型客户场景下并不直观。作者提出B2B产品分析应围绕5个核心属性展开，其中第一个是区分“用户”和“付费者”体验。文章作为系列开篇，抛出收入指标与用户体验如何关联的问题，并称后续会逐项展开。","reason":"数据从业者在搭建B2B数据产品和指标体系时，常直接套用消费级指标；本文点出企业场景下KPI定义的根本矛盾，有助于重新审视产品分析策略与业务价值的连接。","category":"product","category_label":"数据产品","vendors":[],"topics":["客户运营","销售增长"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义"],"use_cases":[],"decision_concerns":["用户采用与业务价值"]},"heat":23,"quality_score":52,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":52,"shelf":"evergreen","pinned":false,"published":"2026-08-28T04:04:18+08:00","first_seen":"2026-08-28T19:13:09.529506+08:00","original_url":"https://amplitude.com/blog/b2b-product-analytics-strategy","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"886b990fc1eb","zh_title":"通往前沿企业：AI优先组织的三大启示","zh_summary":"该文来自数据厂商官方博客，聚焦为何部分企业能成为AI前沿公司。作者提出领先企业对AI的三点理解，并建议领导者如何着手构建AI优先组织。文章未披露具体数据、样本或案例，主要提供高管视角的方法论。","reason":"数据从业者可借此了解企业级AI转型的顶层关注点，但内容未落到数据产品与平台实践，信息密度较低。","category":"product","category_label":"数据产品","vendors":[],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":14,"quality_score":30,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":30,"shelf":"evergreen","pinned":false,"published":"2026-08-26T07:01:41+08:00","first_seen":"2026-08-28T14:41:16.340601+08:00","original_url":"https://www.microsoft.com/en-us/worklab/frontier-firm-resources","items":[{"source":"Microsoft WorkLab"}],"source_badge":"官网"},{"event_id":"4c08e8e2cd44","zh_title":"AI Runtime上的快速容错PyTorch训练","zh_summary":"本文探讨了在大规模分布式训练中如何通过分布式检查点（DCP）和异步保存来提升有效吞吐（goodput）。作者指出，随着GPU数量增加，故障成为常态，而数据管道和检查点机制是恢复的关键。通过采用DCP并行写入分片和async_save异步保存，可以显著减少检查点时间，例如在32×H100上训练20B参数的FSDP模型时，检查点时间从522秒降至9秒。频繁检查点可缩短恢复时间，如每30分钟检查点一次时，有效吞吐从64%提升至91%。文章还强调了自动恢复的重要性，并提供了配套的性能和弹性指南。","reason":"本文提供了关于分布式训练中检查点优化和有效吞吐提升的深度技术实践，对使用PyTorch和AI Runtime的数据工程师和ML工程师有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":43,"quality_score":95,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":95,"shelf":"evergreen","pinned":false,"published":"2026-08-28T09:15:00+08:00","first_seen":"2026-08-28T14:41:16.340601+08:00","original_url":"https://www.databricks.com/blog/fast-fault-tolerant-pytorch-training-ai-runtime","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"d5e1ac751487","zh_title":"资本市场财务如何保障资产负债表回报","zh_summary":"文章指出卖方机构依赖资产负债表运营，市场波动及FRTB等监管推高资本要求，财务部门需实时理解融资成本、资本消耗与流动性风险。AI代理已嵌入定价、资金、报告和监控流程，使决策同时影响资金、资本、流动性和估值。作者认为这一转变将持续加速，财务成为业务前线。","reason":"该文展示了AI代理在资本市场财务决策中的落地场景，对关注数据Agent在复杂金融业务中应用的人有参考价值。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["财务经营","风险管理"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":19,"quality_score":42,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":42,"shelf":"evergreen","pinned":false,"published":"2026-08-26T04:00:01+08:00","first_seen":"2026-08-28T14:41:16.340601+08:00","original_url":"https://www.databricks.com/blog/how-capital-markets-finance-protects-balance-sheet-returns","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"1f2d67f8a512","zh_title":"用 Knowledge Catalog 跨组织扩展 OKF Bundle 治理与共享","zh_summary":"Google Cloud 介绍如何通过 Knowledge Catalog 将 OKF bundle 扩展为组织级可治理的 Agent 上下文。OKF v0.1 定义基于 Markdown 与 YAML frontmatter 的便携格式，v0.2 加入 provenance、verification、freshness、attestation 等信任信号；但跨团队共享仍面临可搜索性、安全合规和元数据孤岛问题。将 bundle 映射到 Knowledge Catalog 的现有类型后，任何查询该目录的 Agent 都能发现、访问这些上下文，并通过 IAM 控制权限。发布只需一次性设置和一次推送，官方提供 OKF 示例代码。","reason":"数据从业者需要管理 Agent 的上下文与治理边界；本文给出用数据目录统一 OKF bundle 的可行路径，避免知识分散在 Git 仓库。","category":"platform","category_label":"AI 数据平台","vendors":["Google","Google Cloud"],"topics":["Data Agent","平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["数据发现与搜索","方案封装与分发"],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":39,"quality_score":87,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":87,"shelf":"evergreen","pinned":false,"published":"2026-08-26T08:00:00+08:00","first_seen":"2026-08-28T14:41:16.340601+08:00","original_url":"https://cloud.google.com/blog/products/data-analytics/scale-okf-bundles-across-an-organization-with-knowledge-catalog","items":[{"source":"Google Cloud Data Analytics Blog"}],"source_badge":"RSS"},{"event_id":"dd21ab640be2","zh_title":"Google Cloud Serverless Spark架构与AI故障排查","zh_summary":"Google Cloud 官方博客介绍了 Serverless Apache Spark 的两种执行模式：交互式会话适合迭代探索，批处理用于自动化生产，并说明了各自的计费特点。文章还展示了从开发到生产的生命周期切换方式，以及高级性能调优和 DCU 成本优化内容。","reason":"数据平台从业者可借鉴 Serverless Spark 在不同阶段的选型与成本控制方法，并了解 Google Cloud 的 AI 辅助排障实践。","category":"platform","category_label":"AI 数据平台","vendors":["Google","Google Cloud"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-08-19T08:00:00+08:00","first_seen":"2026-08-28T14:41:16.340601+08:00","original_url":"https://cloud.google.com/blog/products/data-analytics/serverless-apache-spark-on-google-cloud-architecture-ai-troubleshooting","items":[{"source":"Google Cloud Data Analytics Blog"}],"source_badge":"RSS"},{"event_id":"b3444cea9cb6","zh_title":"Google Cloud Lakehouse catalog 助力 Hive Metastore 现代化","zh_summary":"Google Cloud 介绍无边界湖仓（borderless Lakehouse）在跨云对话式分析中的生产部署注意事项。使用 federated catalogs 时，--refresh-interval 控制元数据同步，最小间隔为 300 秒；大目录同步超时会跳过下一轮以避免排队。BigQuery 会将跨云缓存块存放在 federated catalog 所在区域（如 us-central1），并默认使用 Google 管理加密密钥；若启用 constraints/gcp.restrictNonCmekServices，则绕过缓存直读远端存储。用户可通过 BigQuery 作业统计的 objectStorageStats 比较 cacheBytesRead 与 objectStorageBytesRead 来评估缓存利用率。","reason":"面向数据平台/湖仓从业者的跨云联邦查询生产实践，涉及缓存、数据驻留、加密和监控，对架构与治理决策有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Google","Google Cloud","BigQuery","Databricks","AWS Glue"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["可维护性与复用","成本与性能"]},"heat":44,"quality_score":76,"trend_score":18,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":76,"shelf":"evergreen","pinned":false,"published":"2026-08-19T08:00:00+08:00","first_seen":"2026-08-28T14:41:16.340601+08:00","original_url":"https://cloud.google.com/blog/products/data-analytics/lakehouse-runtime-catalog-helps-modernize-apache-hive","items":[{"source":"Google Cloud Data Analytics Blog"},{"source":"Google Cloud Data Analytics Blog"},{"source":"Google Cloud Data Analytics Blog"},{"source":"Google Cloud Data Analytics Blog"}],"source_badge":"RSS"},{"event_id":"5a0ad358d586","zh_title":"Google Dataflow 结合 ADK 构建经济高效的生成式 AI 流式管道","zh_summary":"Google Cloud 博客介绍了在 Dataflow 中集成生成式 AI 代理的混合流式管道模式。通过在上游使用轻量级 CPU 机器学习模型过滤事件，仅将复杂案例路由至下游 ADK 代理，实现了流式处理的动态分支，同时显著降低成本与延迟。文中以客户支持场景为例，说明代理可动态查询订单数据库、制定补救措施并记录结果。该模式适用于高吞吐流中大多数事件为常规场景的通用场景。","reason":"数据从业者可借鉴其在流式数据处理中结合轻量预过滤与代理动态决策的架构，兼顾成本、延迟与复杂事件处理能力。","category":"platform","category_label":"AI 数据平台","vendors":["Google","Google Cloud"],"topics":["平台AI化","实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":38,"quality_score":85,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-08-18T08:00:00+08:00","first_seen":"2026-08-28T14:41:16.340601+08:00","original_url":"https://cloud.google.com/blog/products/data-analytics/cost-effective-genai-workflows-in-google-dataflow","items":[{"source":"Google Cloud Data Analytics Blog"}],"source_badge":"RSS"},{"event_id":"70dc45860539","zh_title":"快餐业报告忽略的决策关键","zh_summary":"限时优惠（LTO）常被用来吸引客流和促进销售，但整体结果不佳时，传统数据分析无法揭示真正原因。Lovelytics 开发了 QSR 高管绩效控制塔，连接跨职能数据，展示营销、供应链、运营、财务等不同场景下的差异化应对。文章强调关键不是知道数字变了，而是理解数字背后的“为什么”及其财务影响和下一步行动。","reason":"数据从业者可借鉴如何用连接的数据平台解决业务归因问题，而不是停留在报表层面。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","Lovelytics"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["看板与报告"],"decision_concerns":["用户采用与业务价值"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-27T23:00:00+08:00","first_seen":"2026-08-28T06:17:25.558910+08:00","original_url":"https://www.databricks.com/blog/what-qsr-reports-miss-about-decisions-matter-most","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"a18fcf7ace27","zh_title":"结构化图表提取提升Agent检索与问答准确率","zh_summary":"Databricks 官方博客指出，企业Agent在处理包含图表的文档时经常出错，例如前沿Agent仅凭图片推理50秒仍得出错误答案17，而Databricks Genie通过ai_parse_document的结构化提取给出正确答案18。文章在OfficeQA Pro基准及客户检索系统中观察到图表类问题表现更差，尤其在金融服务领域。通过结构化图表提取，可同时改善检索和基于图表问题的回答质量，并在ViDoRe V3图表子集和自建Chart-RAG数据集上验证了效果。","reason":"数据从业者可了解如何通过结构化图表提取增强Agent对多模态文档的理解，提升ChatBI/Data Agent在真实企业场景中的可靠性。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["ChatBI","Data Agent"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":["Agent构建","指标问答"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-08-27T23:00:00+08:00","first_seen":"2026-08-28T06:17:25.558910+08:00","original_url":"https://www.databricks.com/blog/enhancing-agent-retrieval-structured-chart-extraction","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"e3de08c4636a","zh_title":"对象存储+WAL：面向智能体时代的Lakebase Postgres","zh_summary":"文章介绍 Lakebase Postgres 在分离存储架构下的计算侧缓存改进。数据存放在 S3 等对象存储时，缓存分为分布式存储层和 Postgres 计算层，前者物化页面以支持高写入吞吐和读取，后者用 DRAM 服务高频访问页面。标准 Postgres 的 shared buffers 与 OS page cache 存在双重缓冲：例如 4GB RAM 中 1GB 分配给 shared buffers 时，为缓存 1GB 数据可能占用 2GB 内存。文章还说明已向客户交付的改进，并披露近期计划。","reason":"数据平台与数据库从业者可了解 Lakebase Postgres 在分离存储下的缓存架构、双重缓冲问题及优化方向，涉及性能与成本等关键权衡。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","Neon"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":45,"quality_score":82,"trend_score":15,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-08-27T15:18:59+08:00","first_seen":"2026-08-28T06:17:25.558910+08:00","original_url":"https://www.databricks.com/blog/object-storage-wal-lakebase-postgres-agentic-era","items":[{"source":"Databricks Blog"},{"source":"Databricks Blog"},{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"9ee13d67ebf3","zh_title":"为什么AI试点会卡在上下文鸿沟——dbt的解法","zh_summary":"仅16%的企业已规模化部署agentic AI；近80%的公司称AI项目受数据访问限制，70%的受访者表示无法充分信任和治理agent。dbt认为，AI试点停滞的主因并非模型，而是缺乏可信、受治理的上下文，导致agent可能臆造指标或随意选择口径。dbt平台通过提供受治理的语义上下文，帮助企业构建可规模化、可信任的AI agent。","reason":"数据从业者应关注agentic AI落地中的上下文治理缺口；本文给出了未经治理agent的典型失败模式及dbt平台的解决思路，对自建ChatBI/分析Agent有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["dbt Labs","dbt"],"topics":[],"product_ids":["dbt"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","知识与上下文"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-08-28T00:34:00+08:00","first_seen":"2026-08-28T06:17:25.558910+08:00","original_url":"https://www.getdbt.com/blog/why-your-ai-pilot-stalled-at-the-context-gap","items":[{"source":"dbt Blog"}],"source_badge":"RSS"},{"event_id":"f6162b805044","zh_title":"PAYBACK消除BI瓶颈：从传统报表到自助分析","zh_summary":"PAYBACK（德国领先的忠诚度计划公司）通过ThoughtSpot自助分析平台，取代了原有僵化的BI报表体系。此前任何报表调整都需手动修改数据仓库，导致分析师陷入大量工单，用户则被迫回到Excel和邮件，数据孤岛日益严重。转型后，业务团队可近实时下钻查询，例如追踪某日某门店特定优惠券的表现，大幅缩短从问题到答案的等待时间。该案例展示了以用户为中心的数据素养建设和自助服务文化对企业数据化的价值。","reason":"数据从业者应关注这一传统企业如何通过自助分析打破BI工单瓶颈、实现数据民主化的真实路径，对同类组织具有借鉴意义。","category":"bi","category_label":"BI 与可视化","vendors":["ThoughtSpot"],"topics":["BI变局"],"product_ids":["thoughtspot"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["自助分析"],"decision_concerns":["用户采用与业务价值"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-28T06:17:25.558910+08:00","first_seen":"2026-08-28T06:17:25.558910+08:00","original_url":"https://www.thoughtspot.com/blog/payback-eliminates-the-bi-bottleneck","items":[{"source":"ThoughtSpot Blog"}],"source_badge":"RSS"},{"event_id":"0ef0564c116b","zh_title":"ClickHouse真的赢下可观测性之战了吗？","zh_summary":"本文围绕“ClickHouse是否正在赢得可观测性之战”的讨论展开，分析其列式架构、压缩和向量化执行带来的性能优势，也指出高基数分组仍会带来查询时间和内存成本。作者认为，ClickHouse在存储与查询层表现出色，但赢下数据库层并不等于赢下整个可观测性领域。","reason":"ClickHouse是可观测性场景中常用的数据引擎，本文对其性能优势与局限的剖析，对数据平台选型和成本性能权衡有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-08-28T02:24:53+08:00","first_seen":"2026-08-28T06:17:25.558910+08:00","original_url":"https://clickhouse.com/blog/is-clickhouse-winning-the-observability-wars","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"ac7f62f35ef1","zh_title":"Picnic为Amazon MQ配置多OAuth身份提供商实践","zh_summary":"Picnic是一家阿姆斯特丹科技公司，以RabbitMQ作为通信骨干，峰值每秒处理近100万条消息。为确保高可用，他们选用Amazon MQ托管服务。由于公司同时使用Keycloak和AWS IAM进行认证，本文演示如何在同一个RabbitMQ broker上配置多个OAuth 2.0身份提供商，将各提供商的scopes映射到RabbitMQ权限，并在不中断用户的情况下完成变更。","reason":"多身份提供商认证与权限映射是数据平台安全治理的常见难题，本文给出了在Amazon MQ上的具体配置路径，对使用RabbitMQ做数据集成和实时消息的团队有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":[],"decision_concerns":["权限与安全"]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-08-28T00:07:20+08:00","first_seen":"2026-08-28T06:17:25.558910+08:00","original_url":"https://aws.amazon.com/blogs/big-data/how-picnic-configured-multiple-oauth-providers-for-amazon-mq/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"45280e8ace9a","zh_title":"AWS Glue 6.0支持Iceberg v3地理空间与变体类型","zh_summary":"AWS Glue 6.0 基于 Apache Spark 4.1，引入 Spark Declarative Pipelines，让开发者声明目标数据集而非手写 DAG 编排。演示作业把 S3 中的原始订单 CSV 按 bronze、silver、gold 三层加工为分析就绪表，并自动注册到 Glue Data Catalog，可用 Athena 查询。相比用 MWAA 或 Step Functions 人工协调各阶段，单个声明式作业可自动解析依赖、管理检查点并决定执行顺序，减少生产 ETL 的衔接成本。","reason":"声明式 ETL 把湖仓中常见的 medallion 分层管线的依赖、检查点和重试逻辑交给框架，能显著降低大规模管道维护成本；AWS 生态的数据团队可据此评估从 Airflow/Step Functions 编排向 SDP 迁移的收益。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":["湖仓","实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":44,"quality_score":80,"trend_score":15,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-08-28T00:00:12+08:00","first_seen":"2026-08-28T06:17:25.558910+08:00","original_url":"https://aws.amazon.com/blogs/big-data/build-with-geospatial-and-variant-types-in-iceberg-v3-on-aws-glue-6-0/","items":[{"source":"AWS Big Data Blog"},{"source":"AWS Big Data Blog"},{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"d89b42ab29e1","zh_title":"一文搞懂预测模型：建模思路、分类与应用","zh_summary":"本文以销售数据预测为例，讲解预测模型的两类基本思路：因果关系建模和时间序列建模。在只有一行历史数据的情况下，作者演示了如何用Excel识别趋势与季节性，并通过回归分析构造预测公式，还介绍了模型扩展、R平方与MSE等评估方法。文章强调预测的本质是模拟历史走势，数据越丰富预测越准，若数据缺失则更适合做测试而非预测。","reason":"面向数据分析师的数据建模方法论，覆盖从思路选择到Excel落地和模型评估的完整链路，对日常预测分析有实操参考价值。","category":"product","category_label":"数据产品","vendors":[],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["自助分析"],"decision_concerns":[]},"heat":23,"quality_score":52,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":52,"shelf":"evergreen","pinned":false,"published":"2026-08-27T15:51:34+08:00","first_seen":"2026-08-28T06:17:25.558910+08:00","original_url":"https://www.woshipm.com/share/6455442.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"e0a99392bc14","zh_title":"京东物流李亚曼：当AI进入物流全链路，产品经理要重新定义自己的价值","zh_summary":"京东物流李亚曼在2026 AI产品大会分享AI在物流中的四级演进：单点优化、流程重构、运营层重构、智能体重构。文中引用UPS ORION节省约3亿美元、中国人均年快递量141个等数据，说明AI正从局部提效走向网络级重构。并探讨产品经理如何适应AI带来的挑战与机遇。","reason":"物流是典型实体供应链场景，文中用真实案例和数据展示了AI从单点优化到系统重构的路径，对数据从业者理解AI在业务中的落地阶段与产品价值有参考意义。","category":"insight","category_label":"AI分析","vendors":[],"topics":["供应链"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":26,"quality_score":58,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":58,"shelf":"evergreen","pinned":false,"published":"2026-08-27T15:44:27+08:00","first_seen":"2026-08-28T06:17:25.558910+08:00","original_url":"https://www.woshipm.com/ai/6455237.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"d1f8a4b05ddf","zh_title":"非结构化数据的结构化处理：基于 Snowflake Cortex AI Functions","zh_summary":"文章提出将传统 raw→transformed→curated 三层数据架构扩展至非结构化数据，在 transformed 层使用 Snowflake Cortex AI Functions 直接在 SQL 内将文本、音频、图像转换为实体抽取、情感评分、摘要等结构化信息。增强后的输出进入 curated 层，可驱动 BI dashboard、ML pipeline 及 Cortex Analyst 自然语言探索，无需额外数据移动。文中还介绍了完整工作流及典型函数 AI_COMPLETE、AI_CLASSIFY 等，强调可复用数据资产。","reason":"数据从业者应关注，因为它展示了如何在数据平台内统一治理非结构化数据，以 SQL 原生 AI 函数完成转换，降低管道复杂性与数据移动成本。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["平台AI化"],"product_ids":["snowflake-cortex"],"focus":{"id":"ai-platform","label":"AI 数据平台","priority":1,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":[],"decision_concerns":["可维护性与复用"]},"heat":38,"quality_score":85,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-08-27T22:02:54+08:00","first_seen":"2026-08-28T06:17:25.558910+08:00","original_url":"https://www.infoq.cn/article/Xw6Nlqq7N2J0CKA0ehx8?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"86beae9f2748","zh_title":"如何把 Agent 的判断与行动变成可恢复的软件事实 | KDC 工程补篇","zh_summary":"本文从退款审批场景切入，指出 Agent 单次执行循环不等于业务就绪，系统必须让目标、判断、审批、执行、产物和反馈拥有稳定状态。作者提出业务因果链与运行事实链双链结构，将 Session、Harness 与执行环境解耦，并定义 Resume、Progress、Evaluation 三类 Contract 支撑状态恢复、交接与持续演进。适合 AI 架构师、Agent 系统工程师和数据平台建设者阅读。","reason":"数据从业者应关注 Agent 在生产环境中的可恢复、可控制与可审计能力，这是 Data Agent 从演示走向真实业务的关键工程基础。","category":"agent","category_label":"Data Agent","vendors":[],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","权限与治理"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","可维护性与复用"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-08-27T18:00:00+08:00","first_seen":"2026-08-28T06:17:25.558910+08:00","original_url":"https://www.infoq.cn/article/AkgUFEFE4uG7WIlqaO2g?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"3ab0ee43451d","zh_title":"Cortex Agents：从Text-to-SQL到真正干活的助手","zh_summary":"Snowflake Cortex AI系列第5周进入Applied层，聚焦Cortex Agents。作者在Week 4构建的Semantic View之上，搭建了一个支持工单分诊的Agent，并为其配置cortex_search和cortex_analyst_text_to_sql两个工具。文章指出Cortex Agent的核心不是回答单个问题，而是决定调用哪些工具、按什么顺序执行，以端到端完成任务。作者还实际观察到Agent出现错误决策，强调编排与判断能力的重要性。","reason":"数据从业者可从中了解Cortex Agents如何将Text-to-SQL、检索和语义视图组合为可执行任务的Data Agent，对Agent编排实践有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["Snowflake"],"topics":["Data Agent","语义层"],"product_ids":["snowflake-cortex"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","指标与语义"],"use_cases":["Agent构建","指标问答"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-08-28T05:01:01+08:00","first_seen":"2026-08-28T06:17:25.558910+08:00","original_url":"https://medium.com/snowflake/cortex-agents-from-text-to-sql-to-an-assistant-that-actually-does-something-306e8816dbbe?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"b8c871673575","zh_title":"不牺牲数据完整性的分析实践","zh_summary":"Amplitude认为分析工具不应因技术便利而牺牲数据完整性。他们指出用户不信任数据是影响分析决策的主要原因，而过去分析系统常常为易用性牺牲准确性。文章分享了为确保数据完整性所解决的4个技术问题。","reason":"分析工程师和数据平台团队可借此了解如何在系统设计中保障数据可信，避免因技术妥协影响业务决策。","category":"bi","category_label":"BI 与可视化","vendors":["Amplitude"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["准确性与语义一致性"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-08-28T04:04:18+08:00","first_seen":"2026-08-28T06:17:25.558910+08:00","original_url":"https://amplitude.com/blog/analytics-data-integrity","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"66e29f373297","zh_title":"优秀产品公司如何转型其产品分析技术栈","zh_summary":"文章指出，二十年前“在线”只是新获客渠道，如今在线本身就是产品，所有公司都在变成数字产品企业。自2000年以来，超过一半的财富500强公司已不复存在，幸存者通过敏捷、DevOps、微服务等实现每日多次发布。产品团队需要理解用户行为，但传统营销分析工具只能回答获客和转化漏斗问题，无法支持对产品内使用行为和功能影响的深入分析。成功团队正借助更完善的产品分析技术栈来加速产品迭代和决策闭环。","reason":"产品分析技术栈是数据从业者服务业务团队的重要阵地；本文清晰说明了传统营销分析工具的局限与产品分析的新要求，对设计数据产品和选择分析工具具有参考价值。","category":"product","category_label":"数据产品","vendors":[],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"evergreen","pinned":false,"published":"2026-08-28T04:04:18+08:00","first_seen":"2026-08-28T06:17:25.558910+08:00","original_url":"https://amplitude.com/blog/analytics-stack","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"d256128c2be7","zh_title":"AI时代CDO的角色演变：数据访问、产品与治理","zh_summary":"Fivetran博客指出，CDO平均任期不超过30个月，AI时代职责更重。其工作可归结为三个目标：确保数据访问、构建创新数据产品、负责任地管理数据。文章建议通过明确授权、将组织成熟度转化为具体能力、构建灵活的数据基础来应对挑战。","reason":"CDO角色定义直接影响数据团队的组织与优先级，AI时代尤其关键，值得数据从业者参考。","category":"product","category_label":"数据产品","vendors":["Fivetran"],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据接入"],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-27T05:57:02+08:00","first_seen":"2026-08-27T12:41:55.109658+08:00","original_url":"https://www.fivetran.com/blog/the-evolving-role-of-the-cdo-in-the-ai-era","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"fb749e18d61f","zh_title":"用Snowflake CREATE OR ALTER告别频繁Schema变更部署疲劳","zh_summary":"Snowflake 10.27版本发布说明宣布CREATE OR ALTER DYNAMIC TABLE正式可用。该命令合并了CREATE DYNAMIC TABLE与ALTER DYNAMIC TABLE功能：若动态表不存在则按定义创建；若已存在则更新为语句定义，并尽可能保持数据不变；若定义一致则无操作。该更新属于数据管道能力。","reason":"Snowflake动态表是自动化数据管道的关键能力，GA后用户可更简单地实现声明式数据转换，值得数仓/湖仓从业者关注。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["生产评估与运营"],"decision_concerns":["可维护性与复用"]},"heat":36,"quality_score":70,"trend_score":7,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-27T05:01:01+08:00","first_seen":"2026-08-27T12:41:55.109658+08:00","original_url":"https://medium.com/snowflake/work-smarter-not-harder-with-snowflake-create-or-alter-ccc6b0545618?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"},{"source":"Snowflake Release Notes"}],"source_badge":"RSS"},{"event_id":"21aaca4de4c7","zh_title":"开放权重模型是第一章，数据层才是关键","zh_summary":"开放权重模型只是四阶段序列的第一阶段：制品、工厂、连接组织、治理。文章以Jensen Huang联合25家公司致信华盛顿反对限制开放权重模型为例，指出软件开源用30年验证的路线正在AI加速重演。随着模型商品化，真正持久的价值在于底层数据层——记忆、上下文、运营数据。作者认为这些状态数据从来不属于实验室，而是开放生态中最该被守护的部分。","reason":"本文跳出模型发布之争，指出数据层是AI商品化后的长期壁垒，对规划数据平台与数据治理策略有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["PingCAP","TiDB"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":[],"decision_concerns":[]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-25T04:29:23+08:00","first_seen":"2026-08-27T12:41:55.109658+08:00","original_url":"https://www.pingcap.com/blog/open-weight-models-ai-data-layer/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"79c21caab6c3","zh_title":"迁移OAuth认证Kafka集群到Amazon MSK实战指南","zh_summary":"AWS介绍了如何使用MSK Replicator将启用OAuth 2.0（SASL/OAUTHBEARER）认证的外部或自管理Kafka集群迁移到Amazon MSK。文章逐一讲解了OAuth授权类型及其配置方法，指出了常见遗漏的网络与TLS前提条件，并说明了如何处理位于额外身份层后的身份提供商。该机制兼容Keycloak、Okta、Microsoft Entra ID、PingFederate和Auth0等OIDC提供商，目标集群可为MSK Standard或Express。","reason":"数据从业者可了解如何将自建Kafka集群平滑迁移到Amazon MSK，并掌握OAuth认证在Kafka迁移中的具体配置要点。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入"],"decision_concerns":["可靠性与评估"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-27T03:11:40+08:00","first_seen":"2026-08-27T04:05:07.577351+08:00","original_url":"https://aws.amazon.com/blogs/big-data/migrate-an-oauth-2-0-authenticated-apache-kafka-cluster-to-amazon-msk-with-msk-replicator/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"bd0a61be6b17","zh_title":"Amazon MSK 主题分区数选择指南","zh_summary":"Amazon MSK 新用户常问一个主题需要多少分区。文章解释分区是 Kafka 存储和并行度的基本单位，分区数量直接影响吞吐量、扩展性和运维复杂度，并给出确定理想分区数的实用指导。在 Kafka 中，主题被分为多个分区，每个分区是有序不可变日志，支持消费者组内并行读取。分区越多并行度越高，但也会增加运维复杂性。","reason":"Kafka/流式数据平台容量规划中，分区数决策直接影响性能、扩展性与运维成本，值得数据从业者参考。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon MSK"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-26T23:56:42+08:00","first_seen":"2026-08-27T04:05:07.577351+08:00","original_url":"https://aws.amazon.com/blogs/big-data/amazon-msk-service-101-how-many-partitions-does-an-amazon-msk-topic-need/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"4f8c0a7d39f2","zh_title":"技术革命：为 Agentic AI 时代做好准备","zh_summary":"文章探讨 Agentic AI 从被动助手转向自主决策主体，重点分析零售业 Agentic Commerce 场景、GEO 取代 SEO 对品牌可见性的影响，以及 UCP 等协议下商家智能体的作用。同时指出企业需构建统一、实时、受治理的数据基础，并具备智能体构建能力，才能支撑自动化交易与供应链运营。","reason":"数据从业者应关注智能体对数据基础架构的新要求，以及语义层、AI-ready 数据在 Agent 场景中的关键作用。","category":"agent","category_label":"Data Agent","vendors":[],"topics":["Data Agent","供应链"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","指标与语义"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-26T18:20:43+08:00","first_seen":"2026-08-26T21:17:51.519008+08:00","original_url":"https://www.infoq.cn/article/8ouuK09WuWA7Up35W9vb?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"d4736cba9e07","zh_title":"超越偏移滞后：PB级Apache Hudi数据湖管道的队列时间计算","zh_summary":"Twilio的数据湖支撑全公司分析、报表和机器学习，使用Apache Hudi从Kafka导入数据，截至2025年Q4每月处理超5万亿条记录，2025年网络星期一峰值达每秒1290万条消息。文章指出Kafka偏移滞后只反映消费者落后程度，不代表数据年龄，容易导致数据新鲜度SLA违规。作者提出time-in-queue指标：从最新Hudi提交文件读取Kafka检查点，测量该消息时间戳与当前时间的差，无需改动现有管道。该算法可回溯提交历史以处理缺失检查点，部署后时间延迟成为一等SLA指标，管道所有者可按管道自定义数据新鲜度警报。","reason":"本文解决了大规模数据湖管道中Kafka offset lag与真实数据年龄混淆的常见痛点，给出了一种可落地的数据新鲜度测量方法，对负责数据管道SLA和可观测性的工程师极具参考价值。","category":"platform","category_label":"AI 数据平台","vendors":[],"topics":["湖仓","实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-08-26T17:00:00+08:00","first_seen":"2026-08-26T21:17:51.519008+08:00","original_url":"https://www.infoq.com/articles/beyond-offset-lag-kafka-apache-hudi/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"4b74ba76aba5","zh_title":"DuckDB v2.0递归CTE性能提升42.6倍","zh_summary":"DuckDB官方博客详解v2.0中递归CTE执行引擎的重构：将可复用执行状态提升到查询计划生命周期，使迭代间复用管道调度、操作符和哈希构建，避免每次迭代重复支付执行开销。在一百万条边的可达性查询中，中位运行时间从v1.5.5的4.051秒降至v2.0预览版的0.095秒，获得42.6倍加速。同时介绍了USING KEY语义变化，以及内联执行与调度执行的选择策略。","reason":"递归CTE是复杂分析查询中的常见性能瓶颈，DuckDB通过状态生命周期拆分实现数量级加速，对数据平台引擎开发者和高性能分析实践者有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["DuckDB"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["成本与性能","准确性与语义一致性"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-25T08:00:00+08:00","first_seen":"2026-08-26T21:17:51.519008+08:00","original_url":"https://duckdb.org/2026/08/25/how-duckdb-runs-recursive-ctes-faster.html","items":[{"source":"DuckDB Engineering Blog"}],"source_badge":"RSS"},{"event_id":"2ce94d63e438","zh_title":"2026爱分析中国企业智能体平台竞争力榜单","zh_summary":"爱分析发布2026中国企业智能体平台竞争力榜单，从产品能力和市场影响力区分领导者、实践者、创新者、探索者四象限。字节跳动、腾讯、阿里等与神州数码、百融智能、迈富时、蓝凌智能等入选领导者，Dify、滴普等入选创新者。报告指出智能体生成SQL查询时可能选错数据表和指标口径，语义层将业务术语与指标口径转化为机器可识别的语义资产，是进入经营分析、供应链等核心业务的关键。未来竞争焦点将围绕语义层、记忆、AI办公和AI劳动力交易等边界扩张及平台内核演进展开。","reason":"该报告直接点出智能体在核心业务场景中的指标口径与语义一致性问题，并将语义层列为未来竞争主战场，对关注Data Agent与语义层选型的数据从业者有参考价值。","category":"product","category_label":"数据产品","vendors":["Dify","滴普"],"topics":["Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义"],"use_cases":["指标问答","Agent构建"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":null,"first_seen":"2026-08-26T09:13:04.624177+08:00","original_url":"https://www.ifenxi.com/research/content/6896","items":[{"source":"爱分析"}],"source_badge":"RSS"},{"event_id":"fe27a272d0ce","zh_title":"动态本体本质是数据，不是AI","zh_summary":"拓尔思副总裁曹辉提出动态本体不是知识图谱，而是业务建模，将对象、规则、时间、状态、空间、行为六要素关联，输出一库三图，包括领域动态本体库、建模图谱、实例图谱和时空运行图谱。该平台已在公安、部委、国防等领域落地，并逐步进入央企。曹辉强调动态本体核心是数据与业务逻辑融合，AI提升构建效率但改变不了本质。","reason":"动态本体是数据平台与业务建模结合的重要方法论，时空运行图谱为复杂决策提供沙盘推演能力，值得数据从业者关注。","category":"product","category_label":"数据产品","vendors":["拓尔思"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":[],"decision_concerns":["准确性与语义一致性"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":null,"first_seen":"2026-08-26T09:13:04.624177+08:00","original_url":"https://www.ifenxi.com/research/content/6894","items":[{"source":"爱分析"}],"source_badge":"RSS"},{"event_id":"657606c702fa","zh_title":"利用Databricks支持FISC安全指南","zh_summary":"FISC安全指南是日本金融机构IT环境管理与安全的核心基准。Databricks平台可配置身份管理、网络隔离、加密、数据访问和审计等控制，并通过Unity Catalog实现职责分离、细粒度权限与数据血缘。Databricks还提供FISC客户能力映射矩阵，帮助合规团队将指南条款映射到具体平台能力和客户责任。文章详细说明如何在现代数据与AI平台上落地FISC对齐架构。","reason":"面向金融行业的数据平台合规实践，说明如何用Databricks和Unity Catalog满足FISC安全要求，对数据治理与风险管理工作有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["风险管理"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":[],"decision_concerns":["权限与安全"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-26T08:00:00+08:00","first_seen":"2026-08-26T09:13:04.624177+08:00","original_url":"https://www.databricks.com/blog/leveraging-databricks-support-fisc-security-guidelines","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"0916566e9991","zh_title":"企业数据治理工具选型指南","zh_summary":"数据治理工具选型需匹配数据团队不同角色：数据工程师关注管线集成与自动化分类；数据管家关注所有权、策略与审计；数据科学家需要覆盖特征表、模型和AI代理的治理；分析师需要快速发现可信数据。文章还指出三大常见错误：忽略AI与代理治理、忽视多云多格式支持、跳过真实脏数据的概念验证。","reason":"面向数据团队的治理工具评估框架，帮助避免选型常见误区，数据平台从业者可直接参考。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理","数据资产"],"use_cases":["数据发现与搜索"],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-26T00:17:44+08:00","first_seen":"2026-08-26T09:13:04.624177+08:00","original_url":"https://www.databricks.com/blog/data-governance-tools","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"98029c1b119e","zh_title":"数据网格vs数据结构：湖仓如何化解架构之争","zh_summary":"文章对比Data Mesh与Data Fabric两种数据架构：前者强调领域团队将数据作为产品进行去中心化自治，后者是以元数据驱动的集中式自动化集成层。作者认为选择取决于瓶颈是组织性还是技术性，并指出现代湖仓可同时承载两者——领域团队发布数据产品，集中治理负责基础设施。目标读者为数据架构师与平台负责人，用于评估架构选型。","reason":"数据从业者在架构选型时常混淆Mesh与Fabric，本文给出清晰判定框架及湖仓融合路径，值得平台团队参考。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据发现与搜索"],"decision_concerns":[]},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-08-26T00:05:34+08:00","first_seen":"2026-08-26T09:13:04.624177+08:00","original_url":"https://www.databricks.com/blog/data-mesh-vs-data-fabric","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"db5674e1e03f","zh_title":"开放表格式解析：Iceberg vs. Delta vs. Hudi","zh_summary":"本文解析Apache Iceberg、Delta Lake和Apache Hudi三种主流开放表格式。它们作为对象存储之上的元数据层，为数据湖文件添加ACID事务、模式演进和时间旅行能力，使数据能像数据库表一样被一致读取和安全更新。文章对比了三种格式在事务支持和模式演进上的差异，并说明其与湖仓架构的关系。","reason":"开放表格式是湖仓架构的核心技术基石，理解Iceberg、Delta和Hudi的差异有助于数据平台从业者做技术选型与架构设计。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":[],"decision_concerns":["准确性与语义一致性"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-25T15:37:09+08:00","first_seen":"2026-08-26T09:13:04.624177+08:00","original_url":"https://www.databricks.com/blog/open-table-formats","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"d5cc6c757eb2","zh_title":"关系型与非关系型数据库选型指南","zh_summary":"本文从复杂查询与关系处理、分析聚合、混合负载等角度对比关系型与非关系型数据库。指出关系型数据库适合联表查询与聚合分析，非关系型数据库常需借助Apache Spark等外部框架处理复杂分析，而湖仓架构可弥补事务与分析之间的差距。文章还讨论了垂直扩展与水平扩展的权衡，以及多数据库混合持久化策略。","reason":"数据从业者在搭建数据平台或选型存储引擎时，需要理解关系型与非关系型数据库的适用边界及湖仓架构的价值，本文提供了清晰的决策参考。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks","Apache Spark"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":[],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"evergreen","pinned":false,"published":"2026-08-25T00:56:45+08:00","first_seen":"2026-08-26T09:13:04.624177+08:00","original_url":"https://www.databricks.com/blog/relational-vs-non-relational-database","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"73dcdf0229c0","zh_title":"事务型与分析型数据库选型：OLTP、OLAP还是HTAP？","zh_summary":"本文对比事务型与分析型数据库的并发控制机制，介绍悲观锁与乐观锁的差异，并给出降低锁竞争、测试并发负载的建议。在分析负载集成方面，讨论了CDC实时复制、ETL与ELT的取舍，以及HTAP单平台方案的权衡。适合需要规划数据库架构与数据管道的数据团队参考。","reason":"数据库选型是数据平台建设的基础决策，本文对OLTP/OLAP/HTAP的并发和数据集成模式做了清晰梳理，值得数据从业者阅读。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入"],"decision_concerns":["成本与性能"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-25T00:53:46+08:00","first_seen":"2026-08-26T09:13:04.624177+08:00","original_url":"https://www.databricks.com/blog/transactional-vs-analytical-database","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"1491e2cab966","zh_title":"AI规模化易，信任它难","zh_summary":"文章指出组织正将AI嵌入日常业务运营，但规模化成功远不止部署强大模型。调查显示92%的公司计划增加AI投资，仅1%认为自身AI部署成熟。缺乏可信数据、治理和业务上下文时，AI系统难以产出可靠可解释的结果。作者分析了数据质量、治理、所有权、成本和信任等挑战。","reason":"数据从业者应关注AI规模化中的数据信任与治理短板，理解可信数据基础设施为何成为AI成熟度的关键。","category":"platform","category_label":"AI 数据平台","vendors":["dbt Labs"],"topics":["平台AI化"],"product_ids":["dbt"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":[],"decision_concerns":["可靠性与评估","权限与安全"]},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-08-26T07:01:00+08:00","first_seen":"2026-08-26T09:13:04.624177+08:00","original_url":"https://www.getdbt.com/blog/scaling-ai-is-easy-trusting-it-is-hard","items":[{"source":"dbt Blog"}],"source_badge":"RSS"},{"event_id":"28640dc36b12","zh_title":"Suprema Gaming借助ClickHouse Cloud打造Agent-ready数据平台","zh_summary":"Suprema Gaming从Snowflake迁移至ClickHouse Cloud，以支撑公司向Agent优先运营转型。此前数据延迟达4小时，查询耗时数分钟，dbt管道每天只能全量重建一次，且成本随并发增长。迁移后，团队获得实时交互分析能力，可支持AI Agent问答与行动。","reason":"数据平台如何为Agent化改造底层架构是数据从业者关注的热点，ClickHouse Cloud的迁移案例提供了实时性与成本权衡的实践参考。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse","Snowflake","dbt"],"topics":["平台AI化","实时分析"],"product_ids":["dbt"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["自助分析"],"decision_concerns":["成本与性能"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-25T08:00:00+08:00","first_seen":"2026-08-26T09:13:04.624177+08:00","original_url":"https://clickhouse.com/blog/suprema-gaming-agent-ready-platform","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"1cffe8c0886e","zh_title":"跨云分析：使用IAM将BigQuery连接到Amazon S3 Tables","zh_summary":"本文演示如何让Google BigQuery用户直接查询存储在Amazon S3 Tables上的Iceberg表，实现跨云lakehouse访问，无需复制数据。Part 1聚焦AWS IAM方式，通过单一策略同时控制表元数据和数据访问；AWS Lake Formation方式将在Part 2介绍。该方案避免跨云复制带来的成本、延迟和对账开销，支持单一受治理数据集服务多云团队。","reason":"跨云数据湖仓的免复制访问架构与IAM权限设计，是多云分析平台实践中的关键参考，值得数据平台从业者关注。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Google BigQuery"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据接入"],"decision_concerns":["权限与安全"]},"heat":36,"quality_score":70,"trend_score":7,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-26T00:38:49+08:00","first_seen":"2026-08-26T09:13:04.624177+08:00","original_url":"https://aws.amazon.com/blogs/big-data/enable-cross-cloud-analytics-with-amazon-s3-tables-and-google-bigquery-part-1-iam-based-access-control/","items":[{"source":"AWS Big Data Blog"},{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"340d835ba088","zh_title":"优化Snowflake Cortex Analyst：提升准确率、降低延迟并构建反馈闭环","zh_summary":"本文介绍如何优化Snowflake Cortex Analyst，使自然语言查询企业数据更准确高效。核心方法包括精简语义模型、优化底层数据库结构、利用已验证查询构建优化循环，以及通过监控和追踪数据消除瓶颈。Snowflake官方建议语义模型应面向业务用户而非数据库结构设计，并围绕销售、财务等业务域组织。","reason":"面向Text-to-SQL Agent的落地优化方法，涉及语义模型、准确性和性能调优，对数据Agent实践者有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["Snowflake"],"topics":["ChatBI","语义层"],"product_ids":["snowflake-cortex"],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义"],"use_cases":["指标问答"],"decision_concerns":["准确性与语义一致性","成本与性能"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-26T05:01:01+08:00","first_seen":"2026-08-26T09:13:04.624177+08:00","original_url":"https://medium.com/snowflake/optimizing-snowflake-cortex-analyst-improving-accuracy-reducing-latency-and-building-a-723e82042b65?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"13ea46c500cf","zh_title":"劳动力市场紧俏度：哪里找工作最难也最易？","zh_summary":"Indeed Hiring Lab推出新指标，衡量美国800多个都市和微都市区的劳动力市场紧俏程度。加州和东南部市场最宽松，但原因各异：前者科技需求不足，后者存在供给错配。新英格兰和上中西部最紧俏，原因是老龄化与劳动力萎缩。自2022年初以来美国劳动力市场整体降温，但地区差异显著，如朱诺岗位比2020年初翻倍，洛杉矶和丹佛则减少近20%。","reason":"基于真实职位数据量化区域劳动力供需差异，为求职者与雇主提供可参考的市场判断，展示数据分析在劳动力决策中的应用。","category":"insight","category_label":"AI分析","vendors":["Indeed"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-25T17:00:00+08:00","first_seen":"2026-08-25T21:12:57.864716+08:00","original_url":"https://hiringlab.indeed.com/2026/08/25/labor-market-tightness/","items":[{"source":"Indeed Hiring Lab"}],"source_badge":"RSS"},{"event_id":"6202212eeef3","zh_title":"都市级AI暴露：GenAI如何重塑美国各地就业","zh_summary":"Indeed Hiring Lab推出新的AI暴露度指标，基于近2900项工作技能受生成式AI影响的程度，并结合各大都市的职位构成计算得分。结果显示，科技与知识型都市暴露度最高，依赖实操工作的都市暴露度最低。该指标衡量的是工作任务被重塑的潜力，而非岗位必然消失。实际影响取决于当地雇主采用AI的速度。","reason":"该研究用数据方法将生成式AI影响细化到都市和技能层面，为组织人才与区域劳动力决策提供依据。","category":"insight","category_label":"AI分析","vendors":["Indeed"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-25T17:00:00+08:00","first_seen":"2026-08-25T21:12:57.864716+08:00","original_url":"https://hiringlab.indeed.com/2026/08/25/metro-level-ai-exposure/","items":[{"source":"Indeed Hiring Lab"}],"source_badge":"RSS"},{"event_id":"a0dfec66106c","zh_title":"ClickGap：ClickHouse 的自主 QA 代理","zh_summary":"ClickHouse 每天合并 50 到 100 个 PR。ClickGap 是一个自主 QA 代理，审查每个合并后的变更，设计并执行测试，将回归归因到具体提交，并自动提交 issue 和 PR。上线五个月，ClickGap 已提交约 500 个 issue 和约 200 个 PR，其中一半以上 issue 已关闭，超 200 个已关闭 issue 关联了修复 PR。","reason":"在每天合并数十个 PR 的数据库项目中，用 AI Agent 自动化回归测试和缺陷归因，能显著降低人工审查负担，对数据基础设施团队有借鉴意义。","category":"agent","category_label":"Data Agent","vendors":["ClickHouse"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["Agent构建"],"decision_concerns":["可靠性与评估"]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"evergreen","pinned":false,"published":"2026-08-25T08:00:00+08:00","first_seen":"2026-08-25T21:12:57.864716+08:00","original_url":"https://clickhouse.com/blog/clickgap-autonomous-qa-for-clickhouse","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"10b6595d9b0a","zh_title":"Fivetran性能工程复盘：AI如何改变两年提速之路","zh_summary":"Fivetran启动高性能/低延迟（HSLL）计划，目标是将Oracle到Snowflake等管道提速2-3倍，即1TB数据两小时迁移（约137MB/s）。当时Oracle到Snowflake基准为26MB/s，Postgres到BigQuery为48MB/s。两年后分别达到139MB/s和259MB/s，生产吞吐量从7MB/s提升至70MB/s。文章总结了测量指标、定位瓶颈、围绕系统组织团队等性能工程方法，并谈及AI带来的改变。","reason":"数据从业者可借鉴Fivetran对分布式数据管道做性能工程的方法论，理解如何设定吞吐目标、衡量系统并推动整体改进。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran","Snowflake","BigQuery","Oracle"],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":36,"quality_score":72,"trend_score":7,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-25T21:00:01+08:00","first_seen":"2026-08-25T21:12:57.864716+08:00","original_url":"https://www.fivetran.com/blog/how-we-do-performance-engineering-at-fivetran-and-how-ai-changed-it-2-years-later","items":[{"source":"Fivetran Blog"},{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"e2adb769c3f5","zh_title":"Snowflake Summit 2026：Whatnot如何将超高速增长数据转化为业务洞察","zh_summary":"Whatnot 在 Snowflake Summit 2026 展示了支撑数十亿实时事件的数据平台实践，从集中式 dbt 管理转向基础设施即代码的去中心化架构，让各业务单元自建 Snowflake warehouse 和 pipelines。为缓解数据科学家瓶颈，Whatnot 先后尝试 Slackbot 自动生成 SQL、将 Snowflake semantic views 接入 Sigma 和 Glean，内部测试 text-to-SQL 准确率超 90%，并迈向 agentic analytics 阶段。该案例展示了高增长压力下数据平台的可观测性、成本控制与 AI 分析嵌入运维闭环的落地方式。","reason":"数据从业者可借鉴 Whatnot 在高并发、零容错场景下如何平衡去中心化数据团队与统一治理，并了解 AI 分析师从 Slackbot 到 agentic analytics 的演进路径。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake","Sigma","Glean","dbt"],"topics":["平台AI化"],"product_ids":["dbt"],"focus":{"id":"ai-platform","label":"AI 数据平台","priority":1,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","Agent接口与工具"],"use_cases":["指标问答","Agent构建"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-25T18:52:50+08:00","first_seen":"2026-08-25T21:12:57.864716+08:00","original_url":"https://www.infoq.cn/article/9a0qIhdK6QBwSEh1KQyY?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"01c578964b47","zh_title":"DuckDB Java表函数：将任意Java数据源接入SQL查询","zh_summary":"DuckDB官方博客介绍如何在Java客户端中注册纯Java编写的表函数，将任意Java可访问的数据源（如通过SDK或SOAP访问的系统）暴露为SQL表。这让DuckDB可以作为单节点查询引擎，跨远程系统和本地文件执行异构连接，无需导出步骤。文章还对比了DuckDB内置的Parquet、PostgreSQL、MySQL等连接方式以及ODBC扩展，说明表函数适合处理这些方式覆盖不到的数据源。","reason":"数据从业者应关注：该实践提供了一种在Java生态中扩展DuckDB数据接入能力的通用方法，有助于简化多源数据集成和提升查询灵活性。","category":"platform","category_label":"AI 数据平台","vendors":["DuckDB","MongoDB"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入"],"decision_concerns":["成本与性能"]},"heat":43,"quality_score":86,"trend_score":7,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":86,"shelf":"evergreen","pinned":false,"published":"2026-08-25T08:00:00+08:00","first_seen":"2026-08-25T21:12:57.864716+08:00","original_url":"https://duckdb.org/2026/08/25/table-functions-in-java.html","items":[{"source":"DuckDB Engineering Blog"},{"source":"DuckDB Engineering Blog"}],"source_badge":"RSS"},{"event_id":"d2b5cfdbe7ec","zh_title":"ThoughtSpot用AgentSpot构建七Agent内容开发流水线","zh_summary":"ThoughtSpot的eLearning开发团队使用AgentSpot构建了7个Agent，覆盖内容开发流程的每一步，将团队精力从手动操作转向高价值内容与策略。该团队管理约50门课程和数百个视频，分布在ThoughtSpot University的六条学习路径上。此前，他们需要花费大量时间阅读发布说明、追踪产品经理和手工编写脚本；现在每个环节由专门的Agent替代。首个Release Impact Agent会读取实时发布说明，并对六条学习路径进行None/Low/Medium/High四级影响评分。","reason":"展现了数据厂商如何用AgentSpot设计多Agent管线来处理复杂、重复的内容流程，对数据Agent的构建与编排实践有参考价值。","category":"agent","category_label":"Data Agent","vendors":["ThoughtSpot"],"topics":["Data Agent"],"product_ids":["thoughtspot"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","场景与方案"],"use_cases":["Agent构建","方案封装与分发"],"decision_concerns":[]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-25T11:23:25+08:00","first_seen":"2026-08-25T09:53:39.625495+08:00","original_url":"https://www.thoughtspot.com/blog/agentspot-elearning-workflow","items":[{"source":"ThoughtSpot Blog"}],"source_badge":"RSS"},{"event_id":"66b04ff2d911","zh_title":"Databricks用AI加速事故调查","zh_summary":"Databricks在博客中介绍其AI SRE调试代理如何加速事故调查：事故触发后，代理会立即关联跨技术栈的信号，引导工程师进行根因分析。该方案已应用于上百个微服务、1500多个Kubernetes集群，覆盖70多个区域和三个云。文章还复盘了其调试历程、系统架构以及让LLM在事故中可信赖的工程原则。","reason":"数据团队可从中借鉴如何构建可信、可解释的AI Agent用于生产系统故障诊断，对数据平台智能运维与Data Agent设计有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","知识与上下文"],"use_cases":["生产评估与运营","数据发现与搜索"],"decision_concerns":["可靠性与评估"]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-08-25T01:00:00+08:00","first_seen":"2026-08-25T03:00:34.378823+08:00","original_url":"https://www.databricks.com/blog/how-databricks-uses-ai-accelerate-incident-investigation","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"f4faeb6a40d3","zh_title":"dbt on Snowflake实践：把编排搬进数仓后真正的问题","zh_summary":"作者回顾了一次在400行DAG定义中手动追踪依赖的下午，指出代码优先的DAG缺乏可视化反馈，调试如同考古。他将真实项目迁移到dbt Projects on Snowflake，结合Workspaces、Task Graphs和Horizon Catalog，评估其承诺是否兑现。文章也列出了迁移后依然耗时的地方，以及编排移入数仓带来的实际体验。","reason":"dbt与Snowflake原生编排的集成是数据平台选型的重要信号，文中对可维护性和排障体验的复盘对数据从业者有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake","dbt"],"topics":["湖仓","数据人"],"product_ids":["dbt"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["生产评估与运营"],"decision_concerns":["可维护性与复用","可靠性与评估"]},"heat":34,"quality_score":76,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":76,"shelf":"evergreen","pinned":false,"published":"2026-08-24T22:01:05+08:00","first_seen":"2026-08-25T03:00:34.378823+08:00","original_url":"https://medium.com/snowflake/your-data-pipeline-shouldnt-require-a-phd-in-yaml-e18326226f42?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"ecaefd096734","zh_title":"ChartSpec：连接LLM与图表的缺失语言","zh_summary":"ThoughtSpot官方博客介绍了其自然语言图表服务Charts AI核心的ChartSpec规范。ChartSpec是一种类型化的Grammar-of-Graphics规范，足够小以便模型流畅生成，又能表达几乎所有图表，且与渲染后端无关。文章对比了三种常见方案，并说明声明式语法相比枚举类型和生成代码更可靠：可组合、可验证，并从结构上限制幻觉。该设计用于回答“哪些产品在亏损？”等自然语言问题并直接返回图表。","reason":"数据从业者应关注该架构选择，因为它展示了BI产品中LLM生成图表的关键中间表示设计，对构建ChatBI或可视化Agent有直接借鉴意义。","category":"bi","category_label":"BI 与可视化","vendors":["ThoughtSpot"],"topics":["ChatBI"],"product_ids":["thoughtspot"],"focus":{"id":"ai-dashboard","label":"AI 看板","priority":4,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["指标问答"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-24T19:50:56.246447+08:00","first_seen":"2026-08-24T19:50:56.246447+08:00","original_url":"https://www.thoughtspot.com/blog/the-missing-language-between-llms-and-charts","items":[{"source":"ThoughtSpot Blog"}],"source_badge":"RSS"},{"event_id":"f76b86977b69","zh_title":"ClickHouse Cloud如何通过OpenTelemetry实现每秒5000万事件接入","zh_summary":"ClickHouse Cloud公开其内部可观测性平台LogHouse的OpenTelemetry接入架构演进，从常见的agent-to-gateway两层架构起步，现已达到每秒5000万事件、存储177 PiB未压缩数据的规模。文章详细说明了面对数据库背压时，默认内存队列无法承受10GBps压缩数据吞吐，因此设计自定义S3-backed管道来保证持久性。重点讨论了大规模遥测场景下生产者速率不可控带来的工程挑战与权衡。","reason":"数据从业者可从中学习大规模遥测数据接入的架构演化、背压处理及成本性能权衡，是数据平台工程实践的高质量参考。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-08-24T08:00:00+08:00","first_seen":"2026-08-24T19:50:56.246447+08:00","original_url":"https://clickhouse.com/blog/reliable-opentelemetry-ingestion-at-scale","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"ebe3d9541f1b","zh_title":"2026爱分析·中国记忆市场研究报告正式发布","zh_summary":"爱分析发布《2026中国记忆市场研究报告》，将智能体记忆（Agent Memory）定义为智能体在长期交互中沉淀并指导决策的经验资产。报告测算中国记忆市场规模将从2025年14.4亿元增至2030年642.5亿元，复合增长率超110%。腾讯云Agent Memory将长期记忆准确率从48%提升至76%，火山引擎开源OpenViking使Token消耗成本降低91%。报告还分析了云大厂、模型厂商、独立记忆平台等五类玩家的竞争格局。","reason":"Agent Memory是数据Agent的关键基础设施，本报告厘清市场定义、测算规模并梳理竞争象限，帮助数据从业者理解智能体记忆的技术与商业演进方向。","category":"product","category_label":"数据产品","vendors":["腾讯云","阿里云","火山引擎","百度智能云","质变科技"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":["Agent构建"],"decision_concerns":["准确性与语义一致性","成本与性能"]},"heat":38,"quality_score":85,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":null,"first_seen":"2026-08-24T15:21:44.508021+08:00","original_url":"https://www.ifenxi.com/research/content/6891","items":[{"source":"爱分析"}],"source_badge":"RSS"},{"event_id":"424b235d79d4","zh_title":"风控产品经理在AI时代如何保持判断力，从身份证号码第15、16位说起","zh_summary":"文章依据国家标准 GB11643-1999，指出身份证第15、16位并非派出所代码，而是第15-17位共同构成顺序码。通过反证法说明若按派出所代码理解，一个派出所同一天最多只能容纳5男5女出生，逻辑上不成立；又从管理实践说明派出所分配号段而非将固定代码嵌入号码。作者借此强调，AI时代获得答案容易，但保持独立判断力对风控产品经理至关重要。","reason":"数据从业者在设计风控关联规则或身份证校验逻辑时，容易轻信常见说法导致误判；本文从标准与数学逻辑出发纠正误解，对数据产品经理和规则设计者有实际借鉴价值。","category":"product","category_label":"数据产品","vendors":[],"topics":["风险管理"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义"],"use_cases":[],"decision_concerns":["准确性与语义一致性"]},"heat":25,"quality_score":55,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":55,"shelf":"evergreen","pinned":false,"published":"2026-08-24T11:33:26+08:00","first_seen":"2026-08-24T15:21:44.508021+08:00","original_url":"https://www.woshipm.com/share/6453213.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"5c3a552147a1","zh_title":"ANASAC多国SAP转型：Fivetran打通ERP数据孤岛","zh_summary":"智利跨国农业工业公司ANASAC在拉美及全球19个市场推进ERP整合，统一迁移到SAP S/4HANA Cloud。Fivetran在案例中强调，仅有ERP统一不够，还需打破API限制、专有格式等造成的数据围墙花园，让ERP数据支撑分析、报表与长期现代化。该实践展示了跨国企业如何通过数据集成获得全局业务视图。","reason":"跨国ERP整合与数据集成治理是数据平台建设中的典型难题，Fivetran的实践案例对数据从业者有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran","SAP"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["可维护性与复用"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-08-23T23:56:32+08:00","first_seen":"2026-08-24T09:58:57.031333+08:00","original_url":"https://www.fivetran.com/blog/inside-anasacs-multi-country-sap-transformation","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"d7c6d34e3d28","zh_title":"制造业数字孪生是生态博弈：Snowflake与Agentic AI的跨组织智能","zh_summary":"本文探讨制造业数字孪生从单一资产仿真演变为跨价值链的多方生态构建。作者认为没有任何单一组织能独立掌握完整数据、模型与领域知识，数字孪生本质上是生态级合作。Snowflake AI Data Cloud 与 Agentic AI 架构作为协调层，通过跨越IT/OT鸿沟、AI代理实现语义互操作、以及零拷贝架构的受控数据共享，解决数据主权、信任与互操作等核心问题。Agentic AI将进一步把数字孪生从被动表征模型转化为在治理边界内自主决策的系统。","reason":"从数据平台与AI代理协同的视角，剖析制造业数字孪生落地的数据治理与生态架构，对关注数据平台化智能与供应链协同的从业者有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["平台AI化","供应链"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","指标与语义"],"use_cases":["数据接入","Agent构建"],"decision_concerns":["权限与安全"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-22T03:01:01+08:00","first_seen":"2026-08-22T09:51:26.667271+08:00","original_url":"https://medium.com/snowflake/digital-twin-in-manufacturing-is-an-ecosystem-play-916f12f8c4f4?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"7be0c18da6ba","zh_title":"数据和知识健康度：企业转型的赋能关键","zh_summary":"本文指出数据与知识健康度是企业转型的前提，不能事后补救或一次完成，而需要持续投入和维护。在数字化、分布式的工作环境中，HR共享服务和AI辅助流程要求数据准确、及时且上下文相关，否则AI生成的内容可能带来错误信息、信任侵蚀和合规风险。作者强调员工掌握大量机构知识，若管理不善将导致信息过时或冲突，影响组织竞争力。","reason":"从组织转型视角阐述数据质量与知识治理的持续价值，对数据平台建设和AI落地中的数据治理策略有参考意义。","category":"product","category_label":"数据产品","vendors":[],"topics":["组织人才","风险管理"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","知识与上下文"],"use_cases":[],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-15T03:25:45.400000+08:00","first_seen":"2026-08-22T01:32:18.268286+08:00","original_url":"https://www.mercer.com/insights/people-strategy/hr-transformation/data-and-knowledge-fitness-as-a-transformation-enabler/","items":[{"source":"Mercer Insights"}],"source_badge":"官网"},{"event_id":"f22b1abe499d","zh_title":"破解SQL迁移迷思：新SQL特性让存储过程平迁湖仓更轻松","zh_summary":"本文针对数据仓库迁移到湖仓时，遗留存储过程等过程化SQL逻辑难以迁移的痛点，以Oracle迁移场景为例，展示如何在Databricks Lakehouse上利用新SQL特性，将原有业务逻辑逐行翻译而非用Python/Spark重写。文章强调这样既保留原逻辑，也让SQL团队继续维护自己的业务逻辑，降低迁移门槛。","reason":"数据平台迁移中存储过程重构是常见难点，本文提供无需重写的平迁思路，对湖仓迁移实践有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-21T03:00:00+08:00","first_seen":"2026-08-22T01:32:18.268286+08:00","original_url":"https://www.databricks.com/blog/busting-sql-migration-myths-how-new-sql-features-make-lift-and-shift-lakehouse-easier","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"463acfe6a87d","zh_title":"Postgres服务器上还运行着什么？如何防止它拖垮数据库？","zh_summary":"ClickHouse Managed Postgres介绍了如何管理同一虚拟机上的辅助进程（PgBouncer、备份代理、监控导出器、Prometheus等），防止它们因内存泄漏、CPU饱和或磁盘写满导致数据库宕机。文章详细解释了通过GOMEMLIMIT、cgroup v2的memory.high和memory.max，以及磁盘满会话豁免等机制实现资源隔离。该方法将辅助进程纳入数据库故障模型，增强了托管数据库的稳定性。","reason":"数据库运维从业者可了解在共享基础设施上限制辅助进程资源、保障数据库可用性的具体实践。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-21T08:00:00+08:00","first_seen":"2026-08-22T01:32:18.268286+08:00","original_url":"https://clickhouse.com/blog/protect-postgres-from-supporting-processes","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"8c48e9aeec01","zh_title":"Postgres不慢，慢的是存储：NVMe与EBS性能对比","zh_summary":"本文回顾了POSETTE 2026上关于Postgres存储性能的演讲。基准测试显示，EBS在页读取上耗时约19ms，而NVMe仅0.3ms；WAL fsync在EBS上为11ms，NVMe为1.5ms。64个后端中，EBS上有29个等待IO:DataFileRead，而NVMe上只有9个。NVMe主机在240秒内累计占用约9.4核CPU，EBS仅约1核，说明EBS大量时间在等待存储。文章还讨论了如何通过集群级持久化在本地NVMe上实现生产级可用性。","reason":"数据库存储性能直接影响数据分析与查询效率，该实践对比为数据平台选型与成本性能优化提供实证参考。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse","PeerDB"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":36,"quality_score":70,"trend_score":7,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-20T08:00:00+08:00","first_seen":"2026-08-22T01:32:18.268286+08:00","original_url":"https://clickhouse.com/blog/posette-talk-recap-postgres-isnt-slow-your-storage-is","items":[{"source":"ClickHouse Blog"},{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"18d4c041883c","zh_title":"Shopify 用 ClickHouse 构建全球电商可观测性平台","zh_summary":"Shopify 在 ClickHouse 上统一全球可观测性，查询速度最高提升 30 倍，峰值每秒处理 1 亿事件。此前其日志、指标和追踪系统分散在多个厂商，成本高且难以预测，现在统一到单一引擎后降低了成本和复杂度。该实践来自 Shopify 工程总监在 ClickHouse 活动上的分享。","reason":"数据从业者可了解大型电商平台如何用 ClickHouse 统一可观测性，获得明确的性能与成本收益，是实时数据平台落地的参考案例。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-08-20T08:00:00+08:00","first_seen":"2026-08-22T01:32:18.268286+08:00","original_url":"https://clickhouse.com/blog/shopify-observability-at-global-scale","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"9809cc8aea4d","zh_title":"用自定义标签跟踪SageMaker Unified Studio项目成本","zh_summary":"AWS 官方博客介绍了在 SageMaker Unified Studio 中跟踪项目成本的方法。系统标签会自动传播到所有项目资源，但 CostCenter、Team 等自定义标签不会传播到通过 UI 创建的动态资源。文章提出一个无服务器方案，通过 Glue ETL 将自定义标签与 CUR 数据关联，并用 QuickSight 构建成本分析仪表盘，帮助团队按自定义维度查看支出。","reason":"面向数据平台团队，提供了 AI 项目成本治理与标签管理的可落地实践，适合关注数据平台成本运营的从业者。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-21T00:19:24+08:00","first_seen":"2026-08-22T01:32:18.268286+08:00","original_url":"https://aws.amazon.com/blogs/big-data/track-sagemaker-unified-studio-project-costs-with-custom-tags-and-aws-cur/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"41e1e7af7342","zh_title":"自建还是购买数据管道？Fivetran拆解真实成本","zh_summary":"Fivetran发文对比自建与购买数据管道的成本，指出最大开销并非初始开发，而是后续维护、连接器修复、schema变更适配等。文中引用数据称97%的企业因管道问题导致分析或AI项目延误。文章通过多源集成场景拆解了搭建、测试、运维等环节的隐性成本，帮助团队评估更经济的方案。","reason":"数据集成是数据平台建设的关键环节，该文提供了自建vs采购的成本框架，适合数据团队做技术选型参考。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入"],"decision_concerns":["成本与性能"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-21T05:39:28+08:00","first_seen":"2026-08-22T01:32:18.268286+08:00","original_url":"https://www.fivetran.com/blog/build-vs-buy-data-pipelines-costs-to-consider","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"75210254bb59","zh_title":"美团养虾记：十万人AI实验烧数亿，换来四重错配教训","zh_summary":"美团今年2-3月发起十万人全员“养虾”运动，8万人上手，两周产出10万个Skill，两个月烧掉数亿元算力费。名称源自开源框架OpenClaw，员工用最高规格模型搭建能查数据、写文案的Agent。核心本地商业CEO王莆中复盘称，AI幻觉已“干扰真实经营”并存在安全隐患，总结出认知、效率、场景、考核“四重错配”。这场实验展示了大厂全员Agent落地从盲目试错到精准复盘的组织代价。","reason":"大规模Agent的算力成本、幻觉风险和组织错配是数据Agent落地时绕不开的坑，美团案例提供了罕见的全员级复盘，适合做产品与平台策略参考。","category":"agent","category_label":"Data Agent","vendors":[],"topics":["Data Agent","组织人才"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","场景与方案"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["成本与性能","准确性与语义一致性"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-21T17:06:12+08:00","first_seen":"2026-08-22T01:32:18.268286+08:00","original_url":"https://www.woshipm.com/ai/6452433.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"5f9770dfca34","zh_title":"你的 Coding Agent 有多大价值，取决于它对你的数据了解多少","zh_summary":"文章指出Coding Agent虽能减少数据工程中的样板代码，但因缺乏生产环境上下文（如表生命周期、Schema治理、RBAC），生成结果常“看似正确实则不可用”。核心瓶颈不在模型能力，而在Agent运行时与数据基础设施的语义断连。作者认为真正落地需将治理元数据、权限模型等嵌入Agent运行时，并以Snowflake CoCo为例说明平台原生智能体如何利用角色权限与目录信息解决问题。","reason":"数据从业者可借此理解Agent在数据场景落地的关键瓶颈——上下文与治理，而非仅关注模型能力，对评估和建设数据Agent有实际参考价值。","category":"agent","category_label":"Data Agent","vendors":["Snowflake"],"topics":["Data Agent","平台AI化"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["准确性与语义一致性","权限与安全"]},"heat":34,"quality_score":76,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":76,"shelf":"evergreen","pinned":false,"published":"2026-08-21T00:12:45+08:00","first_seen":"2026-08-22T01:32:18.268286+08:00","original_url":"https://www.infoq.cn/article/CPidTC2YJ7AvlU7jUgiq?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"83357b7d65a2","zh_title":"Snowflake CoWork Automations 架构与执行模型深度解析","zh_summary":"Snowflake CoWork Automations（2026年8月公开预览）引入新的调度原语agent task，可在任务引擎上按计划运行完整的Cortex Agent流程，包括LLM编排、多工具推理、SQL生成与响应合成。文章从底层剖析了权限模型、执行管线以及Cortex Agent API的调用机制，并讨论了大规模治理下数据平台团队需要关注的权限与安全影响。该功能默认授予所有用户EXECUTE AGENT TASK权限，安全团队需评估并收紧这一默认配置。","reason":"这是对Snowflake将自然语言问题转化为可调度的Agent计算的技术详解，帮助数据平台团队理解Agent任务的权限模型与执行机制，是Data Agent落地的重要参考。","category":"agent","category_label":"Data Agent","vendors":["Snowflake"],"topics":["Data Agent","平台AI化"],"product_ids":["snowflake-cortex"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","权限与治理"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-08-21T22:01:04+08:00","first_seen":"2026-08-22T01:32:18.268286+08:00","original_url":"https://medium.com/snowflake/deep-dive-snowflake-cowork-automations-architecture-execution-model-and-the-agent-task-4de7b12a44b7?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"33b09d80e649","zh_title":"用Snowpark Python实现安全回填模式","zh_summary":"本文针对数据管道回填操作中的常见挑战，提出使用Snowpark Python的解决方案。当目标表为派生事实表、源为追加型事件日志时，每次批量处理可能包含插入、更新和删除，回填需处理冲突与数据新鲜度。文章总结了五种最常见的回填问题，并逐一给出简单可复用的模式。适合数据工程团队在维护当前状态表时参考。","reason":"回填是数据管道运维中的高频痛点，文章提供了基于Snowpark Python的实用模式，能帮助数据从业者避免数据一致性问题。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","可维护性与复用"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-21T03:01:01+08:00","first_seen":"2026-08-22T01:32:18.268286+08:00","original_url":"https://medium.com/snowflake/merge-safe-backfill-patterns-with-snowpark-python-e856b2fe24de?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"0aa16e2af514","zh_title":"Iceberg Catalog层选型指南：Horizon、Polaris、Glue与Nessie对比","zh_summary":"本文是Apache Iceberg大师系列第三部分，聚焦Catalog Layer在Iceberg架构中的关键作用与选型决策。Catalog层并非无足轻重，而是所有查询引擎必须达成一致的核心组件，负责元数据指针、原子交换与并发控制。当前格局正围绕开放REST标准整合：Polaris晋升为Apache顶级项目，Nessie并入Polaris，Snowflake将双Catalog统一到Horizon。文章为工程师提供了截至2026年中的Catalog选型地图。","reason":"Iceberg Catalog选型直接决定湖仓架构是否真正避免锁定，本文梳理主流Catalog落地方向，适合数据平台与湖仓从业者参考。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake","Dremio","AWS"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":[],"decision_concerns":["可维护性与复用"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-08-20T22:01:06+08:00","first_seen":"2026-08-22T01:32:18.268286+08:00","original_url":"https://medium.com/snowflake/the-iceberg-catalog-layer-explained-snowflake-horizon-open-catalog-polaris-glue-and-nessie-2e5565d2afa2?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"9f95b0f204de","zh_title":"十亿行亚秒级：Snowflake 哪种仓库真正能跟上？","zh_summary":"Manychat 数据工程团队在 Snowflake 上对九种计算配置做了服务端基准测试，从托管 Postgres 到 Interactive Analytics，并用近十亿事件的生产级数据集模拟面向数百万用户的实时看板查询。结果表明，真正决定能否在亚秒级返回的不是仓库规格上调，而是通过聚类键等数据布局实现的分区裁剪（pruning）；同时还暴露出编译、缓存局部性和超大工作集这三个新的性能边界。","reason":"为数据从业者提供了一份完整的 Snowflake 亚秒级查询基准方法和调优思路：在扩容之前先优化数据裁剪，成本与性能收益更直接。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["看板与报告","生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-08-19T22:01:04+08:00","first_seen":"2026-08-22T01:32:18.268286+08:00","original_url":"https://medium.com/snowflake/sub-second-on-a-billion-rows-which-snowflake-warehouse-actually-keeps-up-16ea0e73e627?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"2edb0885e1af","zh_title":"你的下一款BI工具不该是BI工具 | Hex","zh_summary":"Hex 官方博客回顾 BI 行业演变：2005年意味着分页报表，2015年意味着可视化发现与仪表盘，如今云、嵌入式、自动化洞察成为新需求。Hex 曾担心被贴上 BI 标签，但用户调查和 G2 评论显示许多人将 Hex 视为 BI 工具。客户反馈称“有数千个仪表盘但仍缺少洞察”，这促使 Hex 质疑传统 BI 范式是否仍然正确。","reason":"文章通过 Hex 从“反 BI”到被用户归类为 BI 的案例，揭示 BI 工具定义正随需求和 AI 演变，对数据平台选型与建设有参考价值。","category":"bi","category_label":"BI 与可视化","vendors":["Hex"],"topics":["BI变局"],"product_ids":["hex"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["报表与可视化"],"use_cases":["自助分析","看板与报告"],"decision_concerns":["用户采用与业务价值"]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"evergreen","pinned":false,"published":"2026-08-20T08:00:00+08:00","first_seen":"2026-08-22T01:32:18.268286+08:00","original_url":"https://hex.tech/blog/next-bi-tool/","items":[{"source":"Hex Blog"}],"source_badge":"官网"},{"event_id":"751bcb32efab","zh_title":"Netflix双Flink自动扩缩器：自研与开源之战的教训","zh_summary":"Netflix工程师Samuel Yeboah、Francesco Di Chiara和Mingliang Liu撰文介绍了他们运行两个Flink自动扩缩器的经历。自2017年起，Netflix在Apache Flink上运行超过30000个流处理作业，平台自动生成大部分作业。Netflix在2019年自研了基于外部指标的自动扩缩器，后来采用Apache Flink社区的自动扩缩器，现两者并存，正逐步过渡到开源方案。文章分享了关于指标、成本和维护自研基础设施的真实代价的深刻教训，对运行少量或大量Flink作业的团队均有参考价值。","reason":"对于在大型数据平台上运行流处理作业的团队，Netflix在自动扩缩器上的实战经验与权衡极具参考价值，涵盖了成本、指标和运维决策。","category":"platform","category_label":"AI 数据平台","vendors":["Netflix","Apache Flink"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-08-22T00:01:01+08:00","first_seen":"2026-08-22T01:32:18.268286+08:00","original_url":"https://netflixtechblog.com/a-tale-of-two-flink-autoscalers-e9f6a1b1492b?source=rss----2615bd06b42e---4","items":[{"source":"Netflix Technology Blog"}],"source_badge":"RSS"},{"event_id":"6c6fc36a363b","zh_title":"通用 Agent 来了，Data Agent 还要单独买吗？","zh_summary":"文章以 OpenClaw 接入 Aloudata CAN 语义平台、安装问数和归因 Skill 为例，说明通用 Agent 能模仿数据分析，但“会分析”不等于“能上岗”。作者认为 Data Agent 需一体化设计，在需求澄清、强制数据校验、结果可追溯等方面承担岗位责任，而非仅挂载 Skill。文中还强调数据 100% 准确要以分析过程 100% 可信为手段，并指出单独售卖 Skill 无法对任务完成率负责。","reason":"在通用 Agent 热潮下，本文清晰区分了“会分析”与“能上岗”，为数据团队评估 Data Agent 采购价值、设计可信分析流程提供了实用视角。","category":"agent","category_label":"Data Agent","vendors":["Aloudata"],"topics":["Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","Agent接口与工具"],"use_cases":["指标问答","Agent构建"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-08-19T15:07:09+08:00","first_seen":"2026-08-19T21:10:09.285909+08:00","original_url":"https://aloudata.com/blogs/general-agent-vs-data-agent-enterprise-necessity","items":[{"source":"Aloudata 博客"}],"source_badge":"官网"},{"event_id":"bf71c501757a","zh_title":"零售AI治理：需要上下文控制平面","zh_summary":"零售商正从生成式AI实验走向规模化应用，核心挑战从选择模型转向为每个AI体验提供正确的业务上下文。文章以一家大型分销商为例，说明结合机器学习与LLM优化产品目录，100天冲刺节省数百万美元。但当前企业更需要统一的上下文控制平面，以管理覆盖库存、定价及访问权限的策略。","reason":"文章聚焦AI落地中的数据上下文与权限治理，契合数据平台治理方向，对数据从业者设计企业级AI数据架构有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"ai-platform","label":"AI 数据平台","priority":1,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":[],"decision_concerns":["权限与安全"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-18T23:18:00+08:00","first_seen":"2026-08-19T09:54:18.525750+08:00","original_url":"https://www.databricks.com/blog/when-it-comes-governance-retailers-need-control-plane-context","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"f6add537db07","zh_title":"AI对软件开发岗位的真实影响：Visier分析360万员工记录","zh_summary":"Visier基于155+家企业、360万员工记录的分析显示，AI并未导致软件开发者岗位比例大幅下降，四年间整体招聘份额仅增长2%，对应7%的正增长。结合开发者体验负责人的访谈，岗位正在去专业化与重组，而真正的成本如导师制、团队凝聚力、技能退化并未体现在人头数据中。","reason":"用大规模员工数据反驳AI消灭软件岗位的流行叙事，揭示组织人才结构变化的真实信号，对数据从业者理解AI转型有参考价值。","category":"insight","category_label":"AI分析","vendors":["Visier"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-08-18T03:23:43.337000+08:00","first_seen":"2026-08-19T09:54:18.525750+08:00","original_url":"https://www.visier.com/blog/employee-perspective-ai-impact-software-development/","items":[{"source":"Visier Blog"}],"source_badge":"RSS"},{"event_id":"01c3a1427929","zh_title":"OpenSearch Service优化引擎：用SQL/PPL查询原始日志","zh_summary":"本文介绍如何用PPL和SQL在Amazon OpenSearch Service优化引擎上直接对原始日志和追踪数据运行快速分析查询。该引擎以Parquet列式存储配合DataFusion向量化执行，可对数十亿事件进行聚合、过滤和扫描，无需预先移动或重塑数据。文章通过一次事件调查，逐步演示多维分解、延迟分布、错误率和集群规模等分析。","reason":"该优化引擎展示了直接在原始日志数据上进行交互式分析的能力，对日志分析、可观测性与实时分析场景有实践参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["自助分析"],"decision_concerns":["成本与性能"]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-08-19T02:32:05+08:00","first_seen":"2026-08-19T09:54:18.525750+08:00","original_url":"https://aws.amazon.com/blogs/big-data/querying-raw-log-data-using-sql-and-ppl-with-the-optimized-engine-in-amazon-opensearch-service/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"1c087c0268b7","zh_title":"talabat构建跨AWS与Google Cloud的近实时分析架构","zh_summary":"talabat是中东北非领先的生活服务应用，截至2025年12月拥有超过700万月活跃用户，并于2024年12月在迪拜金融市场上市。作为Delivery Hero的子公司，其业务数据横跨AWS与Google Cloud两大云平台。本文介绍了talabat如何构建混合多云湖仓，在AWS上维护单一Apache Iceberg数据副本，同时在GCP上实现受治理的近实时分析。该架构同时应对跨云与跨区域挑战，为多云数据平台建设提供了参考。","reason":"跨云湖仓与近实时分析是数据平台领域的关键实践，该案例展示了如何在双云环境下保持数据一致性与分析时效性，值得数据从业者关注。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Google Cloud","BigQuery"],"topics":["湖仓","实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":[]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-19T00:56:53+08:00","first_seen":"2026-08-19T09:54:18.525750+08:00","original_url":"https://aws.amazon.com/blogs/big-data/fresher-insights-faster-decisions-talabats-near-real-time-analytics-across-aws-and-google-cloud/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"6d3a13fed4af","zh_title":"AWS：实时流数据为Agentic AI提供统一流式骨干","zh_summary":"AWS介绍面向Agentic AI时代的三种实时流数据架构模式：流式特征工程+实时推理+行动、事件驱动Agent调用、CDC与流管道保持Agent记忆实时同步。文章指出，Agentic AI系统已从研究原型进入生产，需要流式基础设施持续为自主Agent提供上下文，并保持实时湖仓新鲜，同时支撑生成式BI等多类消费。本文基于AWS 2024年博客进一步展开。","reason":"数据从业者可借鉴AWS提出的统一流式骨干架构，用于构建实时数据驱动的Agent系统和智能数据平台。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":["Data Agent","实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","数据资产"],"use_cases":["Agent构建","数据接入"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-08-19T00:42:15+08:00","first_seen":"2026-08-19T09:54:18.525750+08:00","original_url":"https://aws.amazon.com/blogs/big-data/powering-agentic-ai-with-real-time-streaming-data-on-aws/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"e1458227e025","zh_title":"Fivetran谈数据目的地：决定数据架构成败的5个要点","zh_summary":"Fivetran 认为数据目的地决定了数据在分析、AI和业务运营中被治理、查询、激活和复用的难易程度，是数据架构中最关键的决策之一。其目的地设计强调跨仓库一致的 schema 语义、表级同步模式选择、对开放湖格式的原生支持与自动目录注册，以及反向 ETL 层以避免数据死胡同。文中还指出，借助一致的 schema，dbt 模型和 Quickstart 包可跨 Snowflake、Databricks、BigQuery、Redshift 等平台移植。","reason":"数据集成常只关注源端，本文深入阐述目的地侧的 schema 一致性、开放格式与反向 ETL 设计，对数据湖仓架构选型和多平台迁移有实际参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran","Snowflake","Databricks","BigQuery","Redshift"],"topics":["湖仓"],"product_ids":["dbt"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-18T08:00:00+08:00","first_seen":"2026-08-19T09:54:18.525750+08:00","original_url":"https://www.fivetran.com/blog/5-things-to-know-about-where-fivetran-sends-your-data","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"29de685d5ab9","zh_title":"管理AI成本：分步教程设置每用户配额控制支出","zh_summary":"本文介绍如何在Snowflake中为Cortex AI设置每用户配额，防止用户无限调用AI_COMPLETE或循环使用Agent导致信用额度快速消耗。配额为每用户设置信用上限，在达到后几分钟内阻止新请求，并按日或月周期自动重置。教程演示了在Snowsight中通过用户标签界定范围，并可在Snowflake CoCo中强制执行。这是通用指南，也可用于其他配额场景。","reason":"数据团队采用AI功能时成本失控是普遍痛点，该教程提供了具体可操作的用户级配额方案，帮助平台管理者控制AI支出。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":[],"decision_concerns":["成本与性能"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-08-19T00:14:43+08:00","first_seen":"2026-08-19T09:54:18.525750+08:00","original_url":"https://medium.com/snowflake/managing-ai-costs-step-by-step-tutorial-to-set-up-a-per-user-quota-to-control-your-ai-spend-0cba55f29424?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"ea26c96e3ff7","zh_title":"评估AI Agent：Grounded Reasoning Cup赛事解析","zh_summary":"Databricks举办首届Grounded Reasoning Cup，11支北美学术团队基于OfficeQA基准开发并优化Agent，决赛采用新基准OfficeQA Pro V2测试泛化能力。斯坦福以63.3%准确率夺冠，比平均团队高约22个百分点，比离线前沿模型基线高约35个百分点，但仍有18.8%的问题无人解出。比赛还揭示了文档预处理、定向检索、并行Agent、结构化工具使用与验证等优化策略的价值，以及使用代表性留出集评估泛化能力的重要性。","reason":"企业级grounded reasoning评估方法、Agent优化策略与量化基线，对构建和评估数据分析/决策Agent有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具","知识与上下文"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","准确性与语义一致性"]},"heat":38,"quality_score":85,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-08-18T23:00:00+08:00","first_seen":"2026-08-18T21:08:57.868233+08:00","original_url":"https://www.databricks.com/blog/evaluating-ai-agents-live-grounded-reasoning-cup","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"bd7415fa4b93","zh_title":"Sony LIV基于ClickHouse Cloud构建十亿行级实时流分析","zh_summary":"Sony LIV将其原先分散的批处理、Elasticsearch和BigQuery工作负载整合到ClickHouse Cloud上，以支持每天数十亿级流媒体事件的亚秒级分析。该平台旨在为大型直播活动提供云原生、实时、高可扩展的数据基础设施，支撑商业智能和运营决策。副总裁Vaibhav Gupta表示，实时运营可见性和用户分析对业务至关重要。","reason":"展示了如何用ClickHouse Cloud替代碎片化批处理架构，支撑超大规模实时分析，对数据平台选型和架构演进有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-08-19T00:20:22.442000+08:00","first_seen":"2026-08-18T21:08:57.868233+08:00","original_url":"https://clickhouse.com/blog/sony-liv-real-time-analytics","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"e768a44d300c","zh_title":"原型税正在扼杀你的AI路线图","zh_summary":"文章提出“原型税”概念，指从尝试想法到可用原型之间的巨大成本，并认为它比模型能力限制更能拖垮AI路线图。造成该税的三大因素包括跨团队协作时的上下文碎片化、API封装对Agent构成的障碍、以及领域知识孤立。领先的团队并非使用更强大的Agent，而是通过业务语义为Agent提供更好的起点，让意图直接成为规格，并把治理内嵌到流程中。","reason":"数据从业者可从中理解构建数据分析Agent时语义层与上下文工程的关键性，对设计AI数据平台有直接启发。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","指标与语义"],"use_cases":["Agent构建"],"decision_concerns":["准确性与语义一致性"]},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-08-18T03:42:33+08:00","first_seen":"2026-08-18T09:51:35.114887+08:00","original_url":"https://www.databricks.com/blog/prototyping-tax-killing-your-ai-roadmap","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"d5bfdeffce5c","zh_title":"Databricks处理数据，dbt定义数据含义","zh_summary":"Databricks是优秀的数据平台，dbt与Databricks保持合作，数千团队在两者上运行生产工作负载。但选择Databricks作为计算平台与选择它来承载转换逻辑是两个不同的决策，多数公司往往一并批准。将转换逻辑完全置于Databricks会带来可移植性和可审计性风险，退出成本可能在日后成为数月的工程项目。","reason":"面向数据领导者的架构决策讨论，厘清计算平台与转换逻辑的边界，对数据平台选型与治理有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["dbt Labs","Databricks","dbt"],"topics":["数据人"],"product_ids":["dbt"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["可维护性与复用","成本与性能"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-18T00:47:00+08:00","first_seen":"2026-08-18T09:51:35.114887+08:00","original_url":"https://www.getdbt.com/blog/databricks-processes-your-data-dbt-defines-what-it-means","items":[{"source":"dbt Blog"}],"source_badge":"RSS"},{"event_id":"bcfd90e63775","zh_title":"为Token建模而非表：dbt仓储上下文节省20倍成本","zh_summary":"Gong通话记录是AI重要上下文，但直接调用API每次账户查询消耗约24万token且触及速率上限。团队用Fivetran将Gong数据同步至Snowflake，通过dbt建模并经dbt MCP server提供结构化上下文。最终token成本降低20倍，还能与账户其他数据关联形成更丰富的上下文层。","reason":"展示如何用现有数仓与dbt为AI Agent构建可治理、低成本的上下文层，避免直接调用事务性API，是数据平台服务AI的典型实践。","category":"platform","category_label":"AI 数据平台","vendors":["dbt Labs","Gong","Fivetran","Snowflake"],"topics":["平台AI化","数据人"],"product_ids":["dbt"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":["Agent构建"],"decision_concerns":["成本与性能","准确性与语义一致性"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-08-17T22:42:00+08:00","first_seen":"2026-08-18T09:51:35.114887+08:00","original_url":"https://www.getdbt.com/blog/model-for-the-token-not-the-table","items":[{"source":"dbt Blog"}],"source_badge":"RSS"},{"event_id":"6c6fa2765f00","zh_title":"Zepto如何用OpenSearch OR2实例实现亚秒级搜索","zh_summary":"Zepto是印度快速电商平台，其搜索体验基于Amazon OpenSearch Service。随着业务扩张，索引量线性增长，维持亚秒级搜索延迟和控制成本成为挑战。Zepto迁移到OpenSearch Optimized实例后，以原有三分之二的数据节点承载同等负载，索引吞吐提升超100%，成本降低30%。本文介绍了其架构决策、压测结果及生产迁移经验。","reason":"该实践展示了通过实例选型优化搜索性能与成本平衡的路径，对数据平台和实时分析从业者有直接借鉴价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon OpenSearch Service"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据发现与搜索"],"decision_concerns":["成本与性能"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-18T00:46:28+08:00","first_seen":"2026-08-18T09:51:35.114887+08:00","original_url":"https://aws.amazon.com/blogs/big-data/how-zepto-powers-sub-second-search-using-opensearch-service-or2-instances/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"7ebe29c893ee","zh_title":"Amazon MQ for RabbitMQ 支持IAM OAuth 2.0认证","zh_summary":"AWS 官方博客介绍了 Amazon MQ for RabbitMQ 通过 OAuth 2.0 集成 IAM 认证的方案，可消除静态凭据管理负担。文章说明客户端使用现有 IAM 身份获取短时 JWT 完成认证，访问控制集中在 IAM 角色和代理配置中。还演示了基于租户级 IAM 角色与 RabbitMQ scope alias 实现 vhost 级隔离的多租户用例。该功能要求 RabbitMQ 3.13 和 4.2 及以上版本。","reason":"面向数据平台工程师的认证与权限治理实践，展示如何用 IAM 替代静态凭据，提升多租户数据接入的安全性。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["数据接入"],"decision_concerns":["权限与安全"]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-08-18T00:37:43+08:00","first_seen":"2026-08-18T09:51:35.114887+08:00","original_url":"https://aws.amazon.com/blogs/big-data/iam-authentication-with-oauth-2-0-for-amazon-mq-for-rabbitmq/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"de350ca98624","zh_title":"Amazon MQ for RabbitMQ 的认证与授权选项","zh_summary":"在规模化场景下，消息代理的认证管理十分复杂，静态用户名密码方式会带来凭证分发、轮换与撤销等运维负担。Amazon MQ for RabbitMQ 支持简单凭证、OAuth 2.0、IAM、LDAP、HTTP 认证后端及 SSL 证书等多种认证授权方式，便于对接企业现有身份基础设施。文章介绍了各方式的特点，并帮助用户根据自身环境选择合适方案。","reason":"消息代理是数据管道与集成治理的重要组件，其认证授权设计直接影响数据平台的安全性与合规性，值得数据平台和治理团队参考。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":[],"decision_concerns":["权限与安全"]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"evergreen","pinned":false,"published":"2026-08-18T00:37:35+08:00","first_seen":"2026-08-18T09:51:35.114887+08:00","original_url":"https://aws.amazon.com/blogs/big-data/authentication-and-authorization-options-for-amazon-mq-for-rabbitmq/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"ece5a6f921ad","zh_title":"NaranjaX借助AWS RAM和Route 53实现跨账户MSK Serverless集群管理","zh_summary":"NaranjaX为从REST架构演进到事件驱动架构，采用Amazon MSK Serverless，并利用AWS RAM和Route 53 Resolver实现跨账户的MSK Serverless集群连接。该方案将共享VPC子网、Route 53解析端点与安全组相结合，支持集群分布在多个账户中，避免集中式配额依赖，同时保持可扩展性、可用性并降低运维开销。","reason":"跨账户流数据基础设施的DNS与资源共享实践，对采用托管Kafka的企业有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入"],"decision_concerns":["可靠性与评估"]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-08-18T00:28:00+08:00","first_seen":"2026-08-18T09:51:35.114887+08:00","original_url":"https://aws.amazon.com/blogs/big-data/naranjax-manages-multiple-amazon-msk-serverless-clusters-in-different-accounts-from-their-idp-using-aws-ram-and-route-53/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"cb619e8bf5e1","zh_title":"虚拟化优先还是现代化优先？Snowflake AIM迁移路径建议","zh_summary":"客户常问：已有Teradata存量，是先用Snowflake AIM虚拟化现有环境，还是直接原生重建现代化。Snowflake将两条路径统一为AIM，提供三条迁移路线：Teradata虚拟化、非Teradata数仓迁移、Spark负载现代化。作者认为这本质是业务风险问题，并建议在Teradata续约压力大、应用与Teradata SQL耦合深、无法承受大爆炸切换风险时优先选择虚拟化路径。","reason":"面向数据平台负责人，给出了Snowflake AIM三条迁移路线的适用判断，帮助在虚拟化与现代化之间做风险与成本权衡。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake","Teradata"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-17T22:01:05+08:00","first_seen":"2026-08-18T09:51:35.114887+08:00","original_url":"https://medium.com/snowflake/virtualize-first-or-modernize-first-how-i-actually-advise-clients-on-snowflake-aim-8d93ca0b3913?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"1109cee945b2","zh_title":"为何绝不该用LLM直接处理人力资源数据","zh_summary":"Visier 指出，HR数据比其他企业数据更易变、更具法律敏感性且强依赖上下文，通用LLM无法处理这种细微差异，会基于猜测给出答案，规模越大风险越大。S&P Global 调查显示，企业技术领袖认为生成式AI的主要短板是数据隐私与安全、回答准确性和系统集成。文章认为问题不在模型本身，而在底层架构，需要上下文层、持久护栏和随数据流动的语义基础。","reason":"对于负责HR数据平台和数据治理的从业者，本文直接点出通用LLM处理敏感员工数据的风险，并强调语义层与治理架构的关键作用，值得关注。","category":"platform","category_label":"AI 数据平台","vendors":["Visier"],"topics":["语义层","组织人才"],"product_ids":[],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","权限与治理"],"use_cases":[],"decision_concerns":["准确性与语义一致性","权限与安全"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-15T05:29:30.656000+08:00","first_seen":"2026-08-18T02:58:15.558273+08:00","original_url":"https://www.visier.com/blog/why-you-shouldnt-use-an-llm-for-workforce-data/","items":[{"source":"Visier Blog"}],"source_badge":"RSS"},{"event_id":"7db363bb1279","zh_title":"Grab用AI Agent将机械分析工作占比从44%降至30%","zh_summary":"Grab利用AI Agent自动化分析工作流，将分析师处理的机械性工单份额从2月的44%降至6月的30%。其方法基于五级自主模型，结合agent自主性、认证数据、上下文管理和人工监督。Spartan系统通过50多个技能和120个分析框架处理自然语言分析请求，并依赖5000多个认证表和指标、4000份上下文文档及2000条golden records。Grab表示，自助分析正越来越多地处理指标、数据和SQL请求，无需分析师干预。","reason":"Grab提供了AI Agent在数据分析场景的落地案例和分级自主模型，展示了如何平衡自动化与人工监督，对数据团队规划Agent应用和指标治理有直接参考价值。","category":"insight","category_label":"AI分析","vendors":[],"topics":["组织人才"],"product_ids":[],"focus":{"id":"ai-platform","label":"AI 数据平台","priority":1,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","指标与语义"],"use_cases":["指标问答","自助分析"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-08-17T21:41:00+08:00","first_seen":"2026-08-18T02:58:15.558273+08:00","original_url":"https://www.infoq.com/news/2026/08/grab-ai-analytics-agents/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"99e77da46ab2","zh_title":"从海量到唯一：构建LLM驱动的选择系统","zh_summary":"Jendrik Jördening分享了将LLM集成到生产管道的工程策略，重点解决非确定性、schema限制、语义提取与确定性代码分离等问题，并使用判别模型验证选择结果。他提出以MVC方式组织LLM应用，确保数据库完整性、可观测性和系统可靠性。该实践源自采购自动化中的成本中心选择场景，对构建生产级Data Agent有直接参考价值。","reason":"数据从业者应关注如何在生产管道中可靠地使用LLM做选择决策，涉及准确性、验证和系统架构等关键问题，对构建Data Agent有实际借鉴意义。","category":"agent","category_label":"Data Agent","vendors":[],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"evergreen","pinned":false,"published":"2026-08-17T17:06:00+08:00","first_seen":"2026-08-18T02:58:15.558273+08:00","original_url":"https://www.infoq.com/presentations/architecture-patterns-llm/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"96ab4b9624a6","zh_title":"技能变迁与劳动力重塑：2024研究揭示大 disruption","zh_summary":"研究报告基于Lightcast数据，分析2016年以来美国职业技能的变化，发现平均每个职位前20项技能中37%已改变，22%为全新技能。金融、设计媒体、业务管理、HR和IT等领域变化更快。报告识别出HR职能中数据化、新型人才获取和利益相关者引领三大趋势，并为雇主、员工、教育者和公共部门提供应对策略。","reason":"该研究以数据量化技能迁移，给出可执行的人才策略，帮助数据从业者理解组织人才与数据技能的结构性变化。","category":"insight","category_label":"AI分析","vendors":[],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-15T21:22:55.908000+08:00","first_seen":"2026-08-17T02:47:44.190425+08:00","original_url":"https://lightcast.io/resources/research/shifting-skills","items":[{"source":"Lightcast Research"}],"source_badge":"官网"},{"event_id":"d3c5241619d2","zh_title":"Allegis与Lightcast报告：劳动力市场数据助力人才决策","zh_summary":"Allegis与Lightcast发布劳动力趋势报告，指出全球低失业率、技能短缺与工资通胀并存。以伦敦项目经理为例，该岗位劳动力规模约4.8万人，广告中位薪资为4.6万英镑。报告强调混合办公等政策影响人才获取范围，企业需借助劳动力数据制定面向未来的人才策略。","reason":"报告用具体数据揭示人才市场变化，展示数据在组织人才决策中的实际价值，适合关注数据分析驱动业务决策的从业者。","category":"insight","category_label":"AI分析","vendors":["Lightcast"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-15T21:21:10.106000+08:00","first_seen":"2026-08-17T02:47:44.190425+08:00","original_url":"https://lightcast.io/resources/research/allegis-workforce-trends","items":[{"source":"Lightcast Research"}],"source_badge":"官网"},{"event_id":"c076af28e6b5","zh_title":"数据仓库中AI函数的高价值用例","zh_summary":"Databricks 介绍在数据仓库中直接使用 AI 函数处理非结构化数据（如评论、工单、PDF）并与结构化数据结合。通过 SQL 调用模型，推理过程保留在现有管道和 Unity Catalog 治理范围内，支持默认安全治理、SQL 原生使用、统一计费及专用函数如 ai_classify、ai_extract 等。该方案可避免数据搬移带来的安全风险，并简化 AI 工作流。","reason":"展示数据仓库平台如何将 AI 能力内嵌到 SQL 分析流程，兼顾治理与易用性，对数据平台建设者具有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["数据接入"],"decision_concerns":["权限与安全"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-15T05:30:00+08:00","first_seen":"2026-08-15T23:46:57.983286+08:00","original_url":"https://www.databricks.com/blog/using-aifunctions-your-data-warehouse-top-use-cases","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"ea9a3a96fb86","zh_title":"Agentic AI项目失败的原因与修复之道","zh_summary":"Wayfair用AI Agent每月自动化4.1万张供应商支持工单；C.H. Robinson的Agent每天自动创建超5500个货运订单，节省600人时。而Klarna的客服Agent却导致质量问题和客户满意度下滑。Gartner预测超40%的Agentic AI项目将在2027年底前被取消，Fivetran报告显示仅15%组织准备就绪。文章指出成败关键不在模型，而在数据质量与治理。","reason":"用真实案例和行业数据揭示AI Agent成败的数据关键，帮助数据团队理解数据质量与治理在Agent项目中的决定性作用。","category":"insight","category_label":"AI分析","vendors":["dbt Labs","Fivetran"],"topics":["Data Agent"],"product_ids":["dbt"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["准确性与语义一致性","用户采用与业务价值"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-15T05:24:00+08:00","first_seen":"2026-08-15T23:46:57.983286+08:00","original_url":"https://www.getdbt.com/blog/why-agentics-projects-fail-and-how-to-fix-them","items":[{"source":"dbt Blog"}],"source_badge":"RSS"},{"event_id":"aac18bc37c0e","zh_title":"从临时取数到可复用系统：数据分析师与 CoCo 的第一周","zh_summary":"CoCo 是运行在 Snowsight 内的 agentic assistant，能帮助数据分析师探索数据、编写和重构 SQL、构建应用并审查工作。文章基于一位分析师的第一周体验，展示如何通过对话快速了解新表、把模糊需求转化为具体查询，并将临时取数沉淀为可复用系统。它不替代分析师的判断，而是取代耗时的机械环节。","reason":"这篇文章展示了在 Snowflake 环境中使用 Data Agent 完成数据探索、SQL 生成与查询复用的真实工作流，对关注 ChatBI/Data Agent 落地价值的人有参考意义。","category":"agent","category_label":"Data Agent","vendors":["Snowflake"],"topics":["ChatBI","Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","Agent接口与工具"],"use_cases":["数据发现与搜索","Agent构建"],"decision_concerns":["可维护性与复用"]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"evergreen","pinned":false,"published":"2026-08-15T02:01:17+08:00","first_seen":"2026-08-15T23:46:57.983286+08:00","original_url":"https://medium.com/snowflake/from-ad-hoc-answers-to-reusable-systems-a-data-analysts-first-week-with-coco-bc06e55c9397?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"59839f525322","zh_title":"Amplitude开放模型评估指南：Kimi实现Sonnet级性能","zh_summary":"Amplitude产品经理详细介绍了如何评估开放权重模型，并以其改进Agent的实践为例，说明在特定任务上开放模型已接近前沿闭源模型。文中引用斯坦福HAI数据称，开放与封闭模型的人类偏好差距一年内从8%降至1.7%，并提到Moonshot发布的2.8万亿参数开放模型Kimi K3据称可与Anthropic的Fable 5竞争。文章旨在帮助团队自行测试开放模型，以优化成本与性能。","reason":"数据Agent团队可借鉴开放权重模型的评估方法与选型思路，在保证性能的同时降低模型成本与供应商锁定风险。","category":"agent","category_label":"Data Agent","vendors":["Amplitude","Moonshot","Anthropic"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["Agent构建"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-08-14T08:00:00+08:00","first_seen":"2026-08-15T23:46:57.983286+08:00","original_url":"https://amplitude.com/blog/open-weights-experimentation","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"11caa8f9632f","zh_title":"Anthropic经济指数：AI使用衡量新维度","zh_summary":"Anthropic发布第四份经济指数报告，提出任务复杂度、技能水平、用途、自主性和成功率五个经济基元，用于追踪Claude对经济的影响。报告基于2025年11月以Claude Sonnet 4.5为主的对话样本，分析AI在不同任务上的成功率及对职业的去技能化风险。该报告为理解AI在实际工作中的使用模式提供了量化框架。","reason":"报告用大规模真实对话数据拆解AI任务特征，为数据分析师和AI应用研究者提供了衡量AI经济影响的方法论与实证发现。","category":"insight","category_label":"AI分析","vendors":["Anthropic","Claude"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-07-09T06:08:50+08:00","first_seen":"2026-08-14T23:10:44.360706+08:00","original_url":"https://www.anthropic.com/research/economic-index-primitives","items":[{"source":"Anthropic Economic Index"}],"source_badge":"官网"},{"event_id":"0c00044a00c6","zh_title":"技能智能：定义、运作方式与最佳平台","zh_summary":"本文介绍技能智能如何帮助企业掌握员工现有能力并预测未来业务需求。世界经济论坛报告称，预计五年内39%的员工核心技能将发生变化。文章提出通过技能数据而非仅凭编制来识别能力缺口，并建议采取发展、重新部署或招聘等行动。还讨论了技能分类法、最佳平台及衡量技能智能成效的四个成功指标。","reason":"数据从业者可了解如何将技能数据用于劳动力决策，是组织人才分析领域的参考方法论。","category":"insight","category_label":"AI分析","vendors":["AIHR"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-13T23:55:25+08:00","first_seen":"2026-08-14T23:10:44.360706+08:00","original_url":"https://www.aihr.com/blog/skills-intelligence/","items":[{"source":"AIHR"}],"source_badge":"RSS"},{"event_id":"97215171d286","zh_title":"如何在HR中明智地使用AI","zh_summary":"Lightcast发布指南，基于其劳动力市场数据观察HR领域AI采用趋势：2023年38%的HR专业人士在日常工作中使用AI，33%希望尝试；2022年美国2.05%的工作涉及AI相关技能，约为2014年的四倍。2023年前五个月，要求生成式AI技能的招聘信息量是2022全年的6倍。指南强调AI效果取决于数据质量，数据过小、有偏见或有缺口会导致AI失效甚至加剧问题，建议HR领导者审慎采用AI并成为明智的AI产品消费者。","reason":"用具体数据展示AI在HR应用的增长趋势与数据质量风险，对从事劳动力数据分析或组织人才方向的数据从业者有参考价值。","category":"insight","category_label":"AI分析","vendors":["Lightcast"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["可靠性与评估"]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-07-02T04:04:41.492000+08:00","first_seen":"2026-08-14T23:10:44.360706+08:00","original_url":"https://lightcast.io/resources/reports/how-to-use-ai-in-hr","items":[{"source":"Lightcast Research"}],"source_badge":"官网"},{"event_id":"de4f194acee8","zh_title":"Autodesk 如何将23亿文档迁移至 Amazon OpenSearch Service","zh_summary":"Autodesk 使用 Migration Assistant 和智能路由，将 Forma 数据管理组件从单个 Elasticsearch 7.1.1 域重构为四个多索引 OpenSearch Service 域，共迁移 23 亿文档。该实践旨在解决单索引达到 100TB 后的性能瓶颈和扩展难题，并展示了大规模搜索负载下的分片与路由策略。","reason":"数据从业者可借鉴大规模搜索数据迁移、索引分片和智能路由的设计思路，适用于海量数据平台演进场景。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["成本与性能"]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"evergreen","pinned":false,"published":"2026-08-14T22:40:11+08:00","first_seen":"2026-08-14T23:10:44.360706+08:00","original_url":"https://aws.amazon.com/blogs/big-data/how-autodesk-migrated-2-3-billion-documents-to-amazon-opensearch-service-using-migration-assistant-and-intelligent-routing/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"cb734e7a1469","zh_title":"用Blame图在OpenSearch上追踪多Agent级联决策失败","zh_summary":"AWS方案架构师构建了一个五Agent股票研究流水线，每个Agent依次工作并最终输出BUY、SELL或HOLD决策。当决策错误时，日志虽完整但无法定位是哪个Agent导致。他们使用Amazon OpenSearch Service存储图谱数据，结合Amazon Bedrock生成嵌入和推理，构建blame graph来追溯失败源头，并展示了三种常见生产故障模式。","reason":"多Agent系统调试是数据Agent落地中的关键难题，该文提供了基于图存储和LLM的根因定位思路，对构建可靠的数据Agent流水线有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["AWS"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-14T22:32:13+08:00","first_seen":"2026-08-14T23:10:44.360706+08:00","original_url":"https://aws.amazon.com/blogs/big-data/trace-cascading-decision-failures-with-a-blame-graph-on-amazon-opensearch-service/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"c5616347cb4f","zh_title":"苏格兰水务用Databricks Genie实现资本投资数据对话式访问","zh_summary":"苏格兰水务的资本投资项目团队过去需依赖大量报表或数据专家才能获取项目状态、财务、交付里程碑和风险信息。他们基于Databricks Genie构建了内部工具SPARK，通过Microsoft Teams以自然语言提问，由Copilot编排并经MCP连接Genie Space，在Unity Catalog治理下返回可信答案。该方案减少了重复报表制作，让项目团队能快速自助获取数据。","reason":"该案例展示了Databricks Genie结合Teams与语义层在企业内部落地ChatBI的架构，对数据从业者设计对话式数据访问方案有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["ChatBI","Data Agent"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","指标与语义"],"use_cases":["指标问答","生产评估与运营"],"decision_concerns":["准确性与语义一致性","权限与安全"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-08-14T05:00:00+08:00","first_seen":"2026-08-14T09:10:33.868404+08:00","original_url":"https://www.databricks.com/blog/how-scottish-water-made-its-capital-investment-data-conversational-databricks-genie","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"e7f241b84ae2","zh_title":"如何在APJ为CoCo配置跨区域推理","zh_summary":"Snowflake 官方博客介绍了在亚太（APJ）区域为 CoCo 配置跨区域推理（CRI）的方法。许多模型未在悉尼、东京、新加坡等区域原生部署，因此需要跨区域调用。通过设置 CORTEX_ENABLED_CROSS_REGION 参数为 AWS_APJ、AWS_AU 或 AWS_JP 等区域限定值，可以仅允许流量在亚太区域内经过云厂商私网传输，从而满足数据驻留审查要求。","reason":"面向数据平台管理员的安全配置实践，涉及数据驻留与跨区域推理边界，对使用 Snowflake AI 功能的从业者具有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["生产评估与运营"],"decision_concerns":["权限与安全"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-14T03:41:38+08:00","first_seen":"2026-08-14T09:10:33.868404+08:00","original_url":"https://medium.com/snowflake/how-to-set-up-cross-region-inference-for-coco-in-apj-8672d40a6dc3?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"07e502da82c2","zh_title":"Snowflake CoCo提示词技巧与最佳实践","zh_summary":"Snowflake官方博客介绍了如何充分利用CoCo，强调其已了解账户中的表、查询历史和成本，可查询数据、追踪血缘、构建管道并运行引导式技能。文章提出提示词四要素：目标、约束、上下文和验证，并建议复杂任务使用计划模式。同时通过模糊与具体提示的对比示例，说明明确指定表名、列名和条件可更快获得准确结果。","reason":"针对Data Agent的提示工程给出可操作框架，帮助数据从业者提升ChatBI/Text-to-SQL场景下的准确性与效率。","category":"agent","category_label":"Data Agent","vendors":["Snowflake"],"topics":["ChatBI","Data Agent"],"product_ids":[],"focus":{"id":"ai-analysis","label":"AI 数据分析","priority":3,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["指标问答"],"decision_concerns":["准确性与语义一致性"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-08-14T03:41:24+08:00","first_seen":"2026-08-14T09:10:33.868404+08:00","original_url":"https://medium.com/snowflake/how-to-get-the-most-out-of-snowflake-coco-prompting-tips-best-practices-58b9c047c123?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"10a590ba05c3","zh_title":"AppFolio借Amazon MSK Express重构实时数据流架构","zh_summary":"AppFolio采用Amazon MSK Express brokers改造其流式数据平台，以替代耗时数小时的再平衡和手动存储规划。该平台每日处理数百万笔交易，通过CDC和服务器端事件实时接入数据，并支撑实时欺诈检测、财务报告和自动化物业管理等下游场景。文章详细介绍了其旧架构的局限与新架构的自动扩展能力。","reason":"真实企业级实时数据流架构升级实践，涉及Kafka托管服务、CDC接入与自动扩展，对数据平台工程师有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon Web Services"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["数据接入","生产评估与运营"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-08-13T23:50:30+08:00","first_seen":"2026-08-14T02:19:28.206489+08:00","original_url":"https://aws.amazon.com/blogs/big-data/how-appfolio-transformed-its-data-streaming-architecture-with-amazon-msk-express-brokers/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"89e0bffe4749","zh_title":"Handshake发布2026届毕业生报告：AI技能需求激增、就业市场仍紧","zh_summary":"Handshake基于平台一年数据，发布2026年及以后Z世代招聘趋势，涵盖增长最快的专业、热门学位、校园活动形式、各州入门薪资、薪资透明趋势、求职地点及远程岗位需求等八个方面。报告发现金融、会计及工程类专业学生占比上升，雇主对商科、教育、公共卫生专业的触达增加，而对金融、营销和计算机科学学生的招聘触达减少。报告还指出 networking 活动更能吸引学生兴趣，并为雇主制定2026年数据驱动的招聘策略提供参考。","reason":"基于平台数据的招聘趋势分析，为组织人才招聘决策提供具体数据依据和策略建议，值得人才与分析从业者关注。","category":"insight","category_label":"AI分析","vendors":["Handshake"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["用户采用与业务价值"]},"heat":40,"quality_score":72,"trend_score":15,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":null,"first_seen":"2026-08-13T21:48:09.098754+08:00","original_url":"https://joinhandshake.com/research/economic-research/class-of-2026-ai-outlook/","items":[{"source":"Handshake Network Trends"},{"source":"Handshake Network Trends"},{"source":"Handshake Network Trends"}],"source_badge":"RSS"},{"event_id":"5b0f19a6ef69","zh_title":"下一个“过半”的，会是数据分析吗？","zh_summary":"Cloudflare 报告显示，2026年非人类流量首次超过互联网流量50%，AI训练爬虫请求占比从2025年春季的22%升至2026年6月的52%。GitHub Copilot 用户达5000万，约三分之一的 Pull Request 已涉及 Agent，Copilot Code Review 一年完成超6000万次审查。文章类比高频交易与程序化广告，预测最晚2029年企业中由 Data Agent 发起并完成的数据任务量将超过传统 BI 产品。对数据从业者而言，需要提前应对 Agent 产出的管理与治理问题。","reason":"Data Agent 正在从工具走向任务级执行，本文用多行业“过半”案例预判其替代传统 BI 的拐点，值得数据团队关注后续治理与度量方式。","category":"agent","category_label":"Data Agent","vendors":["Aloudata","NoETL"],"topics":["BI变局"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["可靠性与评估"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-08-13T10:42:12+08:00","first_seen":"2026-08-13T19:55:43.359599+08:00","original_url":"https://aloudata.com/blogs/will-data-analysis-be-the-next-to-cross-50-percent","items":[{"source":"Aloudata 博客"}],"source_badge":"官网"},{"event_id":"ded49e4ed330","zh_title":"语义层方案如何选型？五级分层与三条分界线","zh_summary":"本文提出语义层五级能力模型，从L0提示词语义到L4过程语义，并指出L1到L2是质变：语义从辅助模型猜测变为无需猜测的约束。作者引用Cube配对实验数据，仅提供schema时前沿模型准确率在45.5%-50.5%，补充4KB手写语义说明文档后升至67.7%-68.7%。文章通过三条分界线为语义层选型提供衡量标尺，帮助从业者识别方案真实上限。","reason":"语义层是当前数据平台与AI分析的热点，本文提供可操作的分级框架和实证数据，便于从业者在概念泛滥时理性选型。","category":"product","category_label":"数据产品","vendors":["Aloudata","Cube"],"topics":["语义层"],"product_ids":[],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义"],"use_cases":[],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-08-05T11:49:02+08:00","first_seen":"2026-08-13T19:55:43.359599+08:00","original_url":"https://aloudata.com/blogs/semantic-layer-upper-limit-evaluation","items":[{"source":"Aloudata 博客"}],"source_badge":"官网"},{"event_id":"5422d3495b2d","zh_title":"ThoughtSpot AgentQL：SQL形态意图，不直接生成SQL的工程路线","zh_summary":"ThoughtSpot 工程博客介绍了 AgentQL——一种以 SQL 语法表达分析意图、但不用 LLM 直接生成 SQL 的能力。其背景是 Spotter 的搜索令牌(token)存在表达力缺口，无法覆盖多步对比、层级计算等复杂查询。AgentQL 选择 SQL 语法作为意图语言，同时拒绝 SQL 执行模型，以统一查询引擎执行。文章详述了背后的工程取舍与设计原则。","reason":"数据从业者可从中了解 ChatBI/Text-to-SQL 的一种架构思路：用 SQL 形状的中间意图而非直接生成 SQL，兼顾表达力与可执行性，对构建分析 Agent 有借鉴价值。","category":"agent","category_label":"Data Agent","vendors":["ThoughtSpot"],"topics":["ChatBI","Data Agent"],"product_ids":["thoughtspot"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","Agent接口与工具"],"use_cases":["指标问答","Agent构建"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-08-13T10:23:00+08:00","first_seen":"2026-08-13T19:55:43.359599+08:00","original_url":"https://www.thoughtspot.com/blog/agentql-sql-shaped-intent","items":[{"source":"ThoughtSpot Blog"}],"source_badge":"RSS"},{"event_id":"0b602400e43b","zh_title":"Apache Iceberg Variant类型：半结构化数据新解法","zh_summary":"Apache Iceberg v3引入Variant类型，用于在单列中存储任意形状的半结构化数据，并以紧凑二进制形式保持原生类型。相比JSON字符串和固定扁平schema，Variant兼具灵活性与查询性能，且无需预定义schema和迁移。本文是该系列首篇，后续将介绍shredding技术。","reason":"湖仓从业者需关注Variant如何改善半结构化数据的存储与查询效率，影响表格式设计与引擎兼容策略。","category":"platform","category_label":"AI 数据平台","vendors":["Apache Iceberg"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":[],"decision_concerns":["准确性与语义一致性","成本与性能"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-08-12T08:00:00+08:00","first_seen":"2026-08-13T15:53:47.905923+08:00","original_url":"https://iceberg.apache.org/blog/variant-in-apache-iceberg/","items":[{"source":"Apache Iceberg Blog"}],"source_badge":"RSS"},{"event_id":"f0a996fceedf","zh_title":"战略编制规划：如何让HR与财务保持同步","zh_summary":"文章探讨在AI Agent普及背景下，人力规划需将自动化工作与AI专家成本纳入考量，HR与财务需通过互联的员工数据保持对齐。Gartner预测到2026年底超40%企业应用将嵌入任务型AI Agent。作者提出三个核心阶段中HR与财务协同的方法，并给出提升敏捷性、精确性和一致性的收益。","reason":"以数据和分析为依据，回答AI转型下人力与财务协同的业务问题，并提供可操作的规划框架，对数据从业者理解组织级AI成本与人才布局有参考价值。","category":"insight","category_label":"AI分析","vendors":["Visier"],"topics":["组织人才","财务经营"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["用户采用与业务价值"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2022-12-07T05:29:24.329000+08:00","first_seen":"2026-08-13T15:11:00.161405+08:00","original_url":"https://www.visier.com/blog/how-to-keep-hr-and-finance-in-sync-on-workforce-planning/","items":[{"source":"Visier Blog"}],"source_badge":"RSS"},{"event_id":"cd516e1927b0","zh_title":"企业AI中的劳动力数据盲区","zh_summary":"本文指出企业AI投资回报未达预期的根源在于劳动力数据碎片化、缺乏治理且被孤立。麦肯锡估计八成企业使用生成式AI，但同样比例报告无显著利润影响；德勤CEO调查显示96% CEO正在或计划部署生成式AI，但企业级价值尚未显现。作者认为问题不在AI模型本身，而在于数据孤岛和过时基础设施导致错误决策。","reason":"数据从业者应关注企业AI落地中常被忽略的数据治理盲区，重视劳动力数据资产的质量与治理。","category":"product","category_label":"数据产品","vendors":["Visier"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":[],"decision_concerns":["用户采用与业务价值"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-07-24T05:23:51.975000+08:00","first_seen":"2026-08-13T15:11:00.161405+08:00","original_url":"https://www.visier.com/blog/workforce-data-blind-spot-enterprise-ai/","items":[{"source":"Visier Blog"}],"source_badge":"RSS"},{"event_id":"cf462f603c77","zh_title":"Databricks重构无服务器网络配置交付：延迟降低97.5%","zh_summary":"Databricks 无服务器平台每天启动数千万台虚拟机，每台都需要网络配置（如允许访问的存储目标、私有端点、Unity Catalog 权限和 Delta Sharing 目标）。旧架构在集群创建关键路径上同步调用多个上游服务，导致 p99 延迟高达 5000ms。团队改用事件驱动管道和快照预计算架构，将 RPC 延迟降至 125ms，并实现 99.99% 的服务可用性。该实践展示了大规模数据平台如何通过架构优化解决网络配置交付的瓶颈。","reason":"面向数据平台工程师的深度架构实践，展示了大规模无服务器数据平台在配置交付上的延迟与可用性优化方法，具有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-08-13T04:00:00+08:00","first_seen":"2026-08-13T10:47:48.429538+08:00","original_url":"https://www.databricks.com/blog/databricks-network-configuration-delivery-tens-millions-serverless-vms","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"5b66bceba7c5","zh_title":"Amtrak 构建铁路智能平台，用 Databricks 统一数据骨干","zh_summary":"Amtrak 正在推进50多年来最大规模的物理转型，引入新列车并重建基础设施。为匹配这一规模，其基于 Databricks 构建名为 Rail Intelligence 的统一数据平台，通过 Lakeflow Connect 和实时流处理整合车队物联网、道旁检测器等信号。该平台旨在打破原有数据孤岛，为分析、运营和预测性维护奠定统一治理基础。","reason":"大型传统企业以统一数据平台支撑大规模资产转型的实践，对数据平台架构和湖仓建设有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["湖仓","数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["可维护性与复用"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-08-13T03:45:00+08:00","first_seen":"2026-08-13T10:47:48.429538+08:00","original_url":"https://www.databricks.com/blog/how-amtrak-building-data-backbone-its-largest-transformation-over-50-years","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"009c04918a87","zh_title":"AI开始争夺专家数据","zh_summary":"爱分析与景联文科技CTO张梦轩对话，探讨AI数据服务产业演进。通用标注需求收缩，高价值专家推理、智能体轨迹和行业数据需求增加。数据工程成为模型的一部分，真实场景决定具身数据价值，流程工业需要专家数据生产体系。","reason":"数据从业者应关注AI数据服务从通用标注向专家数据生产的转变，理解数据工程在模型中的新角色。","category":"product","category_label":"数据产品","vendors":["景联文科技"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":null,"first_seen":"2026-08-13T03:20:45.939796+08:00","original_url":"https://www.ifenxi.com/research/content/6866","items":[{"source":"爱分析"}],"source_badge":"RSS"},{"event_id":"42d6165ced5d","zh_title":"加拿大大型铁路用Databricks Genie Code将管道创建自动化率提至90%","zh_summary":"加拿大最大铁路网络之一运营约2万英里线路，年承运货物价值超2500亿加元。其数据团队借助Databricks Genie Code、Unity Catalog、自定义Agent Skills及Databricks Apps上的Streamlit应用，将管道开发变成可复制的工厂：一段YAML提示即可生成生产级摄取代码，涵盖表定义、历史加载、流式摄入、增量合并和自动化测试。结果新表摄入自动化率超过90%，管道交付从数天压缩至数分钟。","reason":"数据从业者可借鉴如何用AI Agent与元数据驱动大规模数据管道现代化，降低手工重复开发。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["湖仓","平台AI化"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","Agent接口与工具"],"use_cases":["数据接入","Agent构建"],"decision_concerns":["可维护性与复用","可靠性与评估"]},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-08-13T00:35:18+08:00","first_seen":"2026-08-13T03:20:45.939796+08:00","original_url":"https://www.databricks.com/blog/how-major-freight-railroad-scaled-pipeline-creation-genie-code","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"5f7ac34525b8","zh_title":"iFood 用 ClickHouse Cloud 构建智能体安全平台","zh_summary":"iFood 将原本基于 Databricks 的内部安全平台改用 ClickHouse Cloud 重建，实现了 9–16 倍查询加速，成本仅为原来的 40–50%，数据从小时级批量更新变为近实时。这一转变支持了智能体威胁狩猎：多个子代理并行查询超过 30 TB 数据，将分析师原本一周的工作缩短到约 2 小时。iFood 是巴西领先的食品配送平台，安全团队约 100 人。","reason":"该案例展示了在真实海量日志场景下，用 ClickHouse Cloud 替代 Databricks 走向近实时分析与智能体威胁狩猎的实践，对数据平台选型和 AI Agent 落地有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["ClickHouse","Databricks"],"topics":["Data Agent","风险管理"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","Agent接口与工具"],"use_cases":["数据发现与搜索","Agent构建"],"decision_concerns":["成本与性能"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-08-12T23:29:05.833000+08:00","first_seen":"2026-08-13T03:20:45.939796+08:00","original_url":"https://clickhouse.com/blog/ifood-agentic-security-platform","items":[{"source":"ClickHouse Blog"}],"source_badge":"RSS"},{"event_id":"16d70a9b5e86","zh_title":"Spotify为数据湖构建外部索引实现低延迟点查询","zh_summary":"Spotify推出随机访问Parquet（RAP）存储架构，通过外部索引层将查找键直接映射到Parquet文件中的行位置，从而在数据湖上实现低延迟点查询，无需将数据复制到运营数据库。该方案支持在线服务和AI应用从同一数据集读取单个记录，同时继续用于分析、机器学习和在线服务。Spotify表示，其数据湖中存储着EB级数据，而Bigtable中存储PB级在线数据，大规模复制成本高昂。","reason":"该架构展示了如何在保持数据湖统一存储的同时满足在线点查询性能，对湖仓架构设计有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":[],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["成本与性能"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-12T22:26:00+08:00","first_seen":"2026-08-13T03:20:45.939796+08:00","original_url":"https://www.infoq.com/news/2026/08/spotify-data-lake-point-queries/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"f01dc118d37a","zh_title":"Snowflake CoCo跨区域推理配置与合规指南","zh_summary":"为 Snowflake CoCo 配置模型时，应设置账户级默认模型为 auto，并为每个入口设置用户每日额度上限，除非法律要求否则保持模型 RBAC 不变。CoCo 通过 Snowflake Cortex 提供模型，管理员可配置默认模型、支出上限和成本归属。目前仅支持 models.orchestration 这一配置键，无法按工作负载分开设置。建议使用 auto 由 Snowflake 选择模型，仅在需要可复现评估或合规要求时固定具体模型。","reason":"Snowflake CoCo 是数据领域 Agent 产品，模型配置直接影响成本与权限治理；本文给出了面向 ACCOUNTADMIN 的明确操作建议，适合正在落地 Data Agent 的平台团队参考。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["平台AI化","Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理","Agent接口与工具"],"use_cases":["生产评估与运营","Agent构建"],"decision_concerns":["权限与安全","成本与性能"]},"heat":35,"quality_score":68,"trend_score":7,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-08-13T02:55:17+08:00","first_seen":"2026-08-13T03:20:45.939796+08:00","original_url":"https://medium.com/snowflake/how-to-set-up-cross-region-inference-for-coco-in-emea-a7dd5650b261?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"},{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"4395c235c498","zh_title":"跨区域推理：是什么，启用它实际涉及什么","zh_summary":"Snowflake CoCo依赖跨区域推理（CRI）才能访问前沿AI模型和完整Cortex AI产品；若账号级参数禁用，开发者打开CoCo将无响应。启用CRI有四个关键点：区域限制来自云提供商、数据不经过公共互联网、可保留推理在本区域、启用不会改变账单。例如，将CORTEX_ENABLED_CROSS_REGION限定为同一云提供商，推理流量走AWS或Azure私有骨干而非公共互联网。该限制本质由云提供商的区域容量和模型部署范围决定。","reason":"数据从业者需要理解Snowflake跨区域推理的配置影响，尤其是数据合规、区域可用性和Cortex AI启用前提，以便规划平台AI化落地。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["权限与治理"],"use_cases":["生产评估与运营"],"decision_concerns":["权限与安全"]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"evergreen","pinned":false,"published":"2026-08-13T02:55:09+08:00","first_seen":"2026-08-13T03:20:45.939796+08:00","original_url":"https://medium.com/snowflake/cross-region-inference-what-it-is-and-what-enabling-it-actually-involves-b7a79608e8c7?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"16934756bbd8","zh_title":"Cortex Analyst与Snowflake Agents：打造生产级分析服务指南","zh_summary":"本文针对Cortex Analyst和Agent项目中常见的响应慢、结果不正确问题，指出根源往往在于语义模型、编排指令和工具描述等基础设置未受重视。内容包括如何精简现有语义视图、使用Cortex Search解析真实取值、用验证查询锚定SQL，以及通过工具描述和Agent指令路由问题，从而提升服务准确性与速度。","reason":"面向生产级Data Agent部署的深度实践指南，直击ChatBI项目落地中的性能和准确性问题，值得数据从业者参考。","category":"agent","category_label":"Data Agent","vendors":["Snowflake"],"topics":["语义层"],"product_ids":["snowflake-cortex"],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","知识与上下文"],"use_cases":["指标问答","Agent构建"],"decision_concerns":["准确性与语义一致性","成本与性能"]},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-08-12T22:01:04+08:00","first_seen":"2026-08-13T03:20:45.939796+08:00","original_url":"https://medium.com/snowflake/cortex-analyst-snowflake-agents-the-definitive-guide-to-a-production-grade-analyst-service-%EF%B8%8F-39b22d2614f7?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"0b039fb415c1","zh_title":"AI加速数据使用，Dataverse助力数据治理准备","zh_summary":"AI增加了业务数据的规模、价值和用途。Dataverse为管理员提供容量、保留、安全、审计和恢复等管理控制。文章以制造商在采购、财务和供应链中使用AI为例，说明管理员需支撑交易量和数据增长，并回答哪些环境与表在增长、哪些记录需保留、谁能访问、能否恢复等实际问题。文章强调数据所有权、访问模型、生命周期和定期复核是AI时代数据治理的基础。","reason":"数据从业者应关注AI落地对数据治理提出的新要求：自动化Agent持续读写数据时，容量、权限、保留和审计成为必须解决的实操问题。","category":"platform","category_label":"AI 数据平台","vendors":["Microsoft","Power BI"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","权限与治理"],"use_cases":["生产评估与运营"],"decision_concerns":["权限与安全","成本与性能"]},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-11T22:00:00+08:00","first_seen":"2026-08-13T03:20:45.939796+08:00","original_url":"https://www.microsoft.com/en-us/power-platform/blog/2026/08/11/your-company-is-racing-to-deploy-ai-is-your-data-ready/","items":[{"source":"Microsoft Power BI（Power Platform Blog）"}],"source_badge":"RSS"},{"event_id":"8fe614eddcbb","zh_title":"Deloitte：AI价值取决于工作重构而非工具叠加","zh_summary":"Deloitte与Oxford Economics调查89个国家的9,000多名业务与HR领导者发现，85%的领导者认为组织和员工快速适应至关重要，但只有7%认为自己在帮助员工持续成长和适应方面处于领先。仅6%的领导者表示在人机协作设计上取得进展，65%的组织认为文化需要因AI发生显著变化。","reason":"这份报告把AI回报与岗位、流程、决策权和组织文化放在同一框架内，适合OD和HR团队据此评估组织重构，而不只是统计工具采用率。","category":"insight","category_label":"AI分析","vendors":["Deloitte"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":43,"quality_score":95,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":95,"shelf":"evergreen","pinned":false,"published":"2026-03-04T00:00:00-05:00","first_seen":"2026-08-12T22:36:00+08:00","original_url":"https://www.deloitte.com/us/en/about/press-room/deloitte-report-winning-organizations-will-build-the-human-advantage.html","items":[{"source":"Deloitte"}],"source_badge":"RSS"},{"event_id":"4c65d42c540c","zh_title":"微软：组织环境对AI成效的影响是个人努力的两倍","zh_summary":"微软基于10个国家20,000名AI用户和匿名Microsoft 365信号的研究显示，文化、管理者支持和人才实践等组织因素，对员工自报AI成效的解释力为67%，个人心态与行为为32%。但只有26%的AI用户认为领导层对AI方向清晰且一致，说明员工能力提升快于组织系统改造。","reason":"报告为OD和人才分析提供了可操作的组织变量：管理者示范、质量标准、试验空间、绩效与发展机制，比单纯培训个人更能解释AI成效。","category":"insight","category_label":"AI分析","vendors":["Microsoft"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":43,"quality_score":95,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":95,"shelf":"evergreen","pinned":false,"published":"2026-05-05T00:00:00-07:00","first_seen":"2026-08-12T22:36:00+08:00","original_url":"https://www.microsoft.com/en-us/worklab/work-trend-index/agents-human-agency-and-the-opportunity-for-every-organization","items":[{"source":"Microsoft WorkLab"}],"source_badge":"官网"},{"event_id":"dbe61a6475ee","zh_title":"Payscale：AI技能进入岗位要求，薪酬溢价却未跟上","zh_summary":"Payscale对3,413份薪酬管理调查答卷的分析显示，61%的组织已经在既有岗位中加入AI技能或能力要求，但55%没有为这些技能增加基础薪酬、奖金、股权或其他溢价。与此同时，51%的组织把员工薪酬预期与财务约束之间的平衡视为首要挑战。","reason":"这为薪酬团队提供了一个直接的数据问题：岗位要求已经变化，岗位评估、技能溢价和薪酬公平机制是否仍停留在AI之前。","category":"insight","category_label":"AI分析","vendors":["Payscale"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":42,"quality_score":93,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":93,"shelf":"evergreen","pinned":false,"published":"2026-02-24T00:00:00-05:00","first_seen":"2026-08-12T22:36:00+08:00","original_url":"https://www.payscale.com/press-releases/2026-compensation-best-practices-report","items":[{"source":"Payscale"}],"source_badge":"RSS"},{"event_id":"566f6790c35c","zh_title":"SHRM：招聘高管预计AI将进入流程与预测分析","zh_summary":"SHRM对298名招聘负责人的调查显示，92%预计生成式AI撰写职位描述和招聘内容会更加普遍，87%预计一般招聘流程中的AI和自动化会增加，85%预计AI将更多用于招聘指标和预测分析。与此同时，18%的招聘负责人仍把“收集或使用数据指导招聘策略”视为职能挑战。","reason":"报告既说明招聘AI的预期采用方向，也暴露数据能力与流程效率短板，适合招聘负责人把自动化项目与质量、偏差和业务结果指标连接起来。","category":"insight","category_label":"AI分析","vendors":["SHRM"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":41,"quality_score":91,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":91,"shelf":"evergreen","pinned":false,"published":"2026-06-23T00:00:00-04:00","first_seen":"2026-08-12T22:36:00+08:00","original_url":"https://www.shrm.org/topics-tools/research/recruiting-executives-priorities-perspectives-2026/repp26-full-report","items":[{"source":"SHRM"}],"source_badge":"RSS"},{"event_id":"e68fa92fad0f","zh_title":"Lightcast：AI技能岗位溢价28%，需求已跨出IT","zh_summary":"Lightcast基于超过13亿条招聘信息的研究发现，2024年要求AI技能的岗位中，超过一半位于IT和计算机科学之外；提及AI技能的岗位薪资平均高28%，约合每年多18,000美元。报告进一步按HR、财务、科研、教育培训等职业领域拆解具体技能与培训优先级。","reason":"这份劳动力市场数据能帮助招聘、L&D和人才规划团队把泛化的“AI素养”拆成不同岗位真正增长、具有价值且受AI影响的技能。","category":"insight","category_label":"AI分析","vendors":["Lightcast"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":42,"quality_score":94,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":94,"shelf":"evergreen","pinned":false,"published":"2025-07-14T00:00:00-06:00","first_seen":"2026-08-12T22:36:00+08:00","original_url":"https://lightcast.io/resources/research/beyond-the-buzz-developing-the-ai-skills-employers-actually-need","items":[{"source":"Lightcast"}],"source_badge":"RSS"},{"event_id":"8be1e5305105","zh_title":"LinkedIn：AI为招聘节省时间，但招聘质量仍难衡量","zh_summary":"LinkedIn调查23个国家的1,271名招聘管理者，并结合平台数据发现，37%的招聘从业者正在试验或整合生成式AI，已使用者平均报告每周工作量减少20%。然而89%认为招聘质量的衡量会更重要，只有25%对所在组织有效衡量招聘质量的能力高度有信心。","reason":"报告提醒招聘团队，AI节省时间只是过程指标，真正需要建立的是招聘质量、技能匹配和录用后表现的闭环数据。","category":"insight","category_label":"AI分析","vendors":["LinkedIn"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":41,"quality_score":92,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":92,"shelf":"evergreen","pinned":false,"published":"2025-02-13T00:00:00-08:00","first_seen":"2026-08-12T22:36:00+08:00","original_url":"https://www.linkedin.com/business/talent/blog/talent-acquisition/future-of-recruiting-2025","items":[{"source":"LinkedIn"}],"source_badge":"RSS"},{"event_id":"98c97903bcf1","zh_title":"WEF：到2030年岗位净增7800万，但近四成技能将变化","zh_summary":"世界经济论坛汇总55个经济体、22个行业集群的1,000多家雇主数据，覆盖超过1,400万名员工。报告预计到2030年将新增1.7亿个岗位、替代9,200万个岗位，净增7,800万个；近40%的岗位技能将变化，63%的雇主已把技能缺口视为业务转型的主要障碍。","reason":"这为战略劳动力规划提供了全球基线：AI带来的不是单向裁员预测，而是岗位新增、消失与技能迁移同时发生，需要把招聘、再培训和内部流动放在同一模型中。","category":"insight","category_label":"AI分析","vendors":["World Economic Forum"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":43,"quality_score":95,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":95,"shelf":"evergreen","pinned":false,"published":"2025-01-07T00:00:00+01:00","first_seen":"2026-08-12T22:36:00+08:00","original_url":"https://www.weforum.org/press/2025/01/future-of-jobs-report-2025-78-million-new-job-opportunities-by-2030-but-urgent-upskilling-needed-to-prepare-workforces/","items":[{"source":"World Economic Forum"}],"source_badge":"RSS"},{"event_id":"e4930118a675","zh_title":"Visier与RedThread：人才分析技术市场转向重构","zh_summary":"RedThread Research与Visier分析161家People Analytics技术厂商发现，市场规模达到104亿美元，但增速从41%降至28%；50%的厂商提高价格，71%同时采用传统机器学习与生成式AI，而支持数据伦理的厂商比例降至47%。","reason":"这份厂商侧市场数据适合People Analytics和HRIS团队评估产品路线、价格与数据伦理支持，但结论来自Visier参与发布的研究，采购时应结合独立证据验证。","category":"insight","category_label":"AI分析","vendors":["Visier","RedThread Research"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":40,"quality_score":89,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":89,"shelf":"evergreen","pinned":false,"published":"2025-06-02T00:00:00-07:00","first_seen":"2026-08-12T22:36:00+08:00","original_url":"https://www.visier.com/lp/people-analytics-technology-report/","items":[{"source":"RedThread Research × Visier"}],"source_badge":"RSS"},{"event_id":"474a4fade92e","zh_title":"AI如何改写数据分析师的职责","zh_summary":"数据分析师角色常被宣告死亡，但AI实际自动化的是低价值任务，如数据整理、为每个新利益相关者重建仪表板、编写一次性SQL。真正增长价值的是那些定义业务问题并推动决策的分析师。文章指出，能提出好问题的分析师比会写SQL的更成功。平台如Databricks AI/BI正朝自然语言驱动分析发展，但提问能力仍是关键。","reason":"本文探讨AI对数据分析师角色的深层影响，强调提问能力的重要性，对数据从业者理解自身价值有借鉴意义。","category":"insight","category_label":"AI分析","vendors":["Databricks"],"topics":["数据人"],"product_ids":[],"focus":{"id":"ai-analysis","label":"AI 数据分析","priority":3,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["用户采用与业务价值"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-12T21:00:00+08:00","first_seen":"2026-08-12T20:45:22.974647+08:00","original_url":"https://www.databricks.com/blog/future-data-analytics-why-ai-rewriting-analysts-job-description","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"fde18bebfbc0","zh_title":"SHRM调查：HR中的AI仍集中在招聘与流程自动化","zh_summary":"SHRM调查1,908名HR从业者发现，AI在HR中的应用主要集中于招聘、HR技术、学习发展和员工体验。超过一半的受访者尚未正式衡量AI投资成效，真实应用也仍以简历解析、面试排期和职位描述等流程型任务为主。这说明HR需要从工具采用进一步走向效果指标、治理和人才决策能力建设。","reason":"这份研究同时给出了HR AI的应用分布、组织规模差异和效果衡量缺口，适合CHRO和People Analytics团队用作现状基准。","category":"insight","category_label":"AI分析","vendors":["SHRM"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":41,"quality_score":92,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":92,"shelf":"evergreen","pinned":false,"published":"2026-03-31T00:00:00+00:00","first_seen":"2026-08-12T18:58:29+08:00","original_url":"https://www.shrm.org/topics-tools/research/state-of-ai-hr-2026","items":[{"source":"SHRM"}],"source_badge":"RSS"},{"event_id":"875c99b3755b","zh_title":"Mercer：AI转型正在倒逼岗位重构与技能再配置","zh_summary":"Mercer对近12,000名高管、HR负责人、员工和投资者的调查显示，企业把AI视为增长工具，但人才稀缺、技能错配和员工焦虑正在限制转型。65%的高管预计未来两年将有11%至30%的员工因AI被重新部署或再培训；员工对AI导致失业的担忧也从2024年的28%升至2026年的40%。","reason":"报告把组织设计、技能体系、员工体验与AI投资回报放在同一框架内，能帮助HR判断转型不能只由IT或工具采购驱动。","category":"insight","category_label":"AI分析","vendors":["Mercer"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":45,"quality_score":91,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-08-12T18:58:29+08:00","discovery_source":"X·@jasonaverbook","importance":91,"shelf":"evergreen","pinned":false,"published":"2026-02-25T00:00:00+00:00","first_seen":"2026-08-12T18:58:29+08:00","original_url":"https://www.mercer.com/about/newsroom/mercer-s-global-talent-trends-2026-report/","items":[{"source":"Mercer"},{"source":"X 线索·@jasonaverbook"}],"source_badge":"RSS"},{"event_id":"01bd33c269e9","zh_title":"LINE Yahoo将生成式AI系统性引入人事全流程","zh_summary":"LINE Yahoo计划在2026年春前在人事总务领域上线10项AI工具，覆盖招聘分析、面试官训练、面试排期、员工职业发展和内部流动，预计每月减少1,600小时以上的工作量。公司同时规定AI输出只作为参考，最终判断必须由人完成，并由人事与AI治理团队按风险确定使用边界。","reason":"这是少见的HR AI一手落地案例，既有具体场景和效率目标，也公开了人工决策与风险治理边界。","category":"insight","category_label":"AI分析","vendors":["LINE Yahoo"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":40,"quality_score":90,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":90,"shelf":"evergreen","pinned":false,"published":"2026-02-10T19:13:38+08:00","first_seen":"2026-08-12T18:58:29+08:00","original_url":"https://prtimes.jp/main/html/rd/p/000001622.000129774.html","items":[{"source":"LINE Yahoo"}],"source_badge":"RSS"},{"event_id":"8f1a098ff064","zh_title":"Gartner：管理者是员工有效使用AI的关键中间层","zh_summary":"Gartner调查发现，45%的管理者认为AI改善团队工作的效果符合预期，但管理者和普通员工在主动试验AI方面存在明显差距。研究认为，CHRO不能只让员工自行探索AI，而应让管理者负责把工具转化为具体工作方式、任务分配与绩效目标。","reason":"这把HR AI落地问题从“有没有工具”推进到“谁负责改变团队工作方式”，对管理者赋能和变革管理具有直接价值。","category":"insight","category_label":"AI分析","vendors":["Gartner"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":39,"quality_score":87,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":87,"shelf":"evergreen","pinned":false,"published":"2026-03-04T00:00:00+00:00","first_seen":"2026-08-12T18:58:29+08:00","original_url":"https://www.gartner.com/en/newsroom/press-releases/2026-3-4-gartner-hr-survey-reveals-45-percent-of-managers-report-ai-has-lived-up-to-their-expectations","items":[{"source":"Gartner"}],"source_badge":"RSS"},{"event_id":"bb45de9b3b4f","zh_title":"ADP全球调查揭示AI使用、生产力感受与岗位焦虑错位","zh_summary":"ADP Research覆盖36个市场、39,000多名员工的调查显示，只有22%的员工强烈认同自己的岗位不会被淘汰。频繁使用AI并不自动转化为更好的生产力感受：每天使用AI的人反而更可能认为自己没有达到应有的生产力水平。不同年龄层对AI的期待也存在明显差异。","reason":"这份员工侧研究提醒HR不能只用登录量或使用频率判断AI成功，还要同时观察岗位安全感、敬业度、学习支持与真实工作结果。","category":"insight","category_label":"AI分析","vendors":["ADP"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":40,"quality_score":89,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":89,"shelf":"evergreen","pinned":false,"published":"2026-03-25T00:00:00+00:00","first_seen":"2026-08-12T18:58:29+08:00","original_url":"https://mediacenter.adp.com/2026-03-25-ADP-Research-Only-22-of-Workers-Confident-Their-Job-is-Safe-from-Elimination%2C-Underscoring-the-Importance-of-Talent-Strategies-that-Prepare-Employees-for-the-Future%2C1","items":[{"source":"ADP Research"}],"source_badge":"RSS"},{"event_id":"849a2dcfc7c0","zh_title":"Workday：AI缓解倦怠的同时可能加深职场连接缺失","zh_summary":"Workday对2,150名大型企业AI用户的调查显示，AI可能帮助员工减轻倦怠、提升信心，但也伴随着信任、协作和人际连接的新风险。超过五分之一的受访者认为，采用AI后与同事的个人关系变差并感到更孤独；年轻员工受到的影响尤其值得HR关注。","reason":"员工体验不能只以效率和压力下降衡量，这项调查补充了AI对团队连接、协作和年轻员工心理感受的潜在副作用。","category":"insight","category_label":"AI分析","vendors":["Workday"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":38,"quality_score":85,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-05-27T00:00:00+00:00","first_seen":"2026-08-12T18:58:29+08:00","original_url":"https://newsroom.workday.com/2026-05-27-New-Workday-Global-Research-Finds-AI-is-Easing-Burnout-but-May-Be-Deepening-a-Connection-Deficit-at-Work","items":[{"source":"Workday"}],"source_badge":"RSS"},{"event_id":"d44afcf41d63","zh_title":"评估人员分析与劳动力智能方案的9条标准","zh_summary":"本文为HR技术领导者提供了一个评估人员分析与劳动力智能解决方案的实用框架，涵盖数据模型成熟度、总拥有成本等大多数RFP易忽略的标准。文章指出，许多供应商评估流程只优化当前问题，未考虑长期可行性。在AI加速技术栈价值兑现的背景下，选择能随劳动力变化而演进的合作伙伴至关重要。","reason":"人员分析是数据产品在组织人才场景的重要应用，该评估框架帮助从业者避开常见采购误区，关注数据模型成熟度与长期成本，对数据产品选型和建设有参考价值。","category":"product","category_label":"数据产品","vendors":["Visier"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["成本与性能","可维护性与复用"]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"evergreen","pinned":false,"published":"2026-07-30T04:18:05.082000+08:00","first_seen":"2026-08-12T14:58:34.644431+08:00","original_url":"https://www.visier.com/blog/evaluate-people-analytics-workforce-intelligence-solutions/","items":[{"source":"Visier Blog"}],"source_badge":"RSS"},{"event_id":"d5b1f80826c9","zh_title":"劳动力分析：是什么、如何运作及为何重要","zh_summary":"文章介绍劳动力分析的定义、类型及在员工生命周期中的应用。引用Visier与Deloitte对500名高管的调研，仅3%认为拥有充分信息支持人员决策；另有Deloitte研究显示83%的公司劳动力分析成熟度较低。文中提出提升成熟度的关键：将HR与生产力系统数据统一为可信模型，并建立基于洞察及时行动的组织纪律。","reason":"帮助数据从业者理解劳动力分析如何连接多源数据并支持人员决策，是数据分析方法论在组织人才场景的典型实践参考。","category":"insight","category_label":"AI分析","vendors":["Visier"],"topics":["组织人才"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":26,"quality_score":58,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":58,"shelf":"evergreen","pinned":false,"published":"2022-12-14T09:46:21.089000+08:00","first_seen":"2026-08-12T14:58:34.644431+08:00","original_url":"https://www.visier.com/blog/workforce-analytics/","items":[{"source":"Visier Blog"}],"source_badge":"RSS"},{"event_id":"b4ff3df743a4","zh_title":"爱分析发布2026中国本体平台市场洞察报告","zh_summary":"爱分析发布《2026爱分析·中国本体平台市场洞察报告》，系统梳理中国市场的本体实践路径与能力演进方向。报告指出，中国市场尚未形成统一的本体定义，并归纳出知识工程、语义层、业务本体、可执行本体四条路径。报告认为，本体平台需要形成语义表达、业务计算、行动执行和持续治理的闭环，并参考Palantir作为能力参照。","reason":"本体平台是语义层与Data Agent落地的重要基础，报告梳理了中国市场的四类实践路径，帮助数据从业者理解产品边界与演进方向。","category":"product","category_label":"数据产品","vendors":["Palantir"],"topics":["语义层","Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","知识与上下文"],"use_cases":["Agent构建","方案封装与分发"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":null,"first_seen":"2026-08-12T14:39:14.991555+08:00","original_url":"https://www.ifenxi.com/research/content/6863","items":[{"source":"爱分析"}],"source_badge":"RSS"},{"event_id":"de330de1394c","zh_title":"AI时代，数据中台焕发新生？","zh_summary":"数澜科技创始人甘云锋在接受爱分析访谈时表示，“拆中台”是个误会，AI兴起后数据中台窗口重新打开。他认为数据基座的核心目标是持续输出高质量数据集，本体与语义层是企业AI消除歧义、降低幻觉的关键。数澜从高峰期500人缩减至几十人后，如今定位为“数据+AI”公司，专注数据基座、行业模型和数据智能体，服务军工、央国企及大型民企客户。","reason":"数据从业者应关注数据中台向AI数据基座演进的路径，以及本体语义层在企业级AI中的落地价值。","category":"platform","category_label":"AI 数据平台","vendors":["数澜科技"],"topics":["语义层","平台AI化"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","指标与语义"],"use_cases":["数据接入","Agent构建"],"decision_concerns":["准确性与语义一致性"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":null,"first_seen":"2026-08-12T14:39:14.991555+08:00","original_url":"https://www.ifenxi.com/research/content/6854","items":[{"source":"爱分析"}],"source_badge":"RSS"},{"event_id":"4c404bb47e34","zh_title":"现代风险要求实时数据基础：CRO的使命","zh_summary":"文章指出企业风险管理当前受制于数据延迟而非建模复杂度，遗留批处理架构造成可见性缺口。以硅谷银行事件为例，其因利率快速上升出售证券实现18亿美元亏损，暴露数据架构缺陷。Deloitte调查显示超90%受访者认为风险管理对战略目标更重要。现代CRO需要实时、集成的数据基础来支撑决策。","reason":"实时数据架构是风险管理的核心支撑，本文提供了业务驱动与金融机构案例，值得数据平台从业者关注。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-11T20:30:00+08:00","first_seen":"2026-08-12T14:39:14.991555+08:00","original_url":"https://www.databricks.com/blog/modern-risk-demands-real-time-foundation-cros-mandate","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"0faa3f1f97f8","zh_title":"数据复制工具指南：8款主流方案对比","zh_summary":"文章介绍数据复制的基本概念与四种复制方式，并对比8款领先的数据复制工具，分析各自优缺点。同时提供选型框架，帮助团队在规模增长时选择不会失效的架构，避免手动脚本和管道故障的循环。","reason":"数据复制是数据集成治理的基础环节，工具选型直接影响数据管道稳定性与分析时效，值得数据平台从业者参考。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran","Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["数据接入"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-10T08:00:00+08:00","first_seen":"2026-08-12T14:39:14.991555+08:00","original_url":"https://www.fivetran.com/blog/data-replication-tools-comparing-fivetrans-deployment-options","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"2db4b086244c","zh_title":"Snowflake性能技巧与调优实践（第5部分）","zh_summary":"本文是Snowflake支持团队基于DataEngBytes 2026演讲扩展的性能调优系列第5篇，涵盖仓库大小选择、SELECT列表中的相关子查询、谓词转换以及并发查询拥塞等主题。内容来自数据领域厂商官方博客，属于数据库性能优化实践。","reason":"针对Snowflake真实场景的性能调优方法，对数据平台工程师优化查询与资源成本有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-11T22:01:05+08:00","first_seen":"2026-08-12T14:39:14.991555+08:00","original_url":"https://medium.com/snowflake/snowflake-performance-tips-and-tricks-part-5-3689d2384d3d?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"f9d8ce10886b","zh_title":"AI将实验推向业务关键地位","zh_summary":"Amplitude 产品管理总监 Eric Metelka 撰文指出，AI 快速演变让实验成为业务关键。OpenAI 收购 Statsig 表明，基于可信数据的测试已不再是可选项。文章提出三点：AI 微调会影响准确性、延迟、安全与满意度；个性化需要实验提供因果验证；AI 评估虽重要但不足以替代实验。","reason":"数据从业者可借此理解AI时代如何用实验评估支撑AI功能迭代和业务决策。","category":"product","category_label":"数据产品","vendors":["Amplitude","Statsig","OpenAI"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["生产评估与运营"],"decision_concerns":["可靠性与评估","用户采用与业务价值"]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2025-09-12T08:00:00+08:00","first_seen":"2026-08-12T13:40:18.379118+08:00","original_url":"https://amplitude.com/blog/ai-experimentation","items":[{"source":"Amplitude Blog"}],"source_badge":"官网"},{"event_id":"190e28d13cb4","zh_title":"Netflix实时分布式图查询实践：gRPC执行API","zh_summary":"本文是Netflix构建实时分布式图（RDG）系列的第三篇，重点介绍查询层设计。作者Nilesh Mishra和Ajit Koti展示了如何通过gRPC执行API支持对数十亿节点和边的低延迟查询，并兼顾灵活性与性能。结合前文的数据处理流水线与存储层设计，完整呈现了Netflix大规模实时图数据平台的技术路径。","reason":"面向大规模实时图数据的查询API设计，涉及数据平台基础设施的延迟与灵活性权衡，值得数据从业者参考。","category":"platform","category_label":"AI 数据平台","vendors":[],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["自助分析"],"decision_concerns":["成本与性能"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-08T00:01:02+08:00","first_seen":"2026-08-12T13:40:18.379118+08:00","original_url":"https://netflixtechblog.com/how-and-why-netflix-built-a-real-time-distributed-graph-part-3-querying-the-graph-with-grpc-0f3468349607?source=rss----2615bd06b42e---4","items":[{"source":"Netflix Technology Blog"}],"source_badge":"RSS"},{"event_id":"9f8ca8dc2ec6","zh_title":"Netflix设备能力建模与分析实践","zh_summary":"Netflix支持从4K流媒体、沉浸式音频到直播和云游戏等多种功能，但设备硬件限制（如内存、CPU、显示能力）导致部分功能无法在所有设备上支持。为保证最佳用户体验，Netflix投资于对设备能力的深入理解，并将其建模用于分析。该实践展示了如何将设备能力转化为可分析的数据资产。","reason":"数据从业者可关注Netflix如何将设备能力建模为可复用的分析数据资产，支撑用户体验优化决策。","category":"platform","category_label":"AI 数据平台","vendors":[],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":[],"decision_concerns":[]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-08-01T00:01:02+08:00","first_seen":"2026-08-12T13:40:18.379118+08:00","original_url":"https://netflixtechblog.com/modeling-device-capabilities-for-analytics-e7607acebde8?source=rss----2615bd06b42e---4","items":[{"source":"Netflix Technology Blog"}],"source_badge":"RSS"},{"event_id":"5c4d28e53f75","zh_title":"Agentic AI 架构为何需要数据库，不只是向量存储","zh_summary":"TiDB工程师在SCaiLE Europe 2026上论述，单独的向量数据库并非AI应用的必要代价，而是数据同步约束下的变通方案。每个新增AI组件都会复制一份数据，带来独立的接入路径、运维和同步任务，导致栈越堆越复杂。TiDB通过同一Raft流同步行存储、列存储、向量索引和全文索引，由SQL优化器决定查询走哪个存储。文章认为分布式SQL原生支持向量搜索与分析能力，可减少数据漂移和多系统运维成本。","reason":"数据从业者关注的多系统同步与数据一致性痛点，本文给出分布式数据库一体化方案，对构建Agentic AI数据栈有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["PingCAP","TiDB"],"topics":["Data Agent","平台AI化","湖仓"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["可靠性与评估","可维护性与复用"]},"heat":38,"quality_score":75,"trend_score":7,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-08-10T21:00:00+08:00","first_seen":"2026-08-12T13:40:18.379118+08:00","original_url":"https://www.pingcap.com/blog/agentic-ai-architecture/","items":[{"source":"TiDB Blog"},{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"341ca51f8349","zh_title":"完整Agent状态栈：内存、文件与Serverless数据库持久化","zh_summary":"TiDB博客文章指出，AI应用需要四种持久化层：Agent记忆、生成文件、操作状态和检索数据。无服务器数据库能自动扩缩容、按用量计费并支持缩容到零，适合突发流量。文章建议评估引擎而非标签，重点关注连接行为和冷启动，并认为分散的技术栈会累积问题，单一引擎可消除系统边界和一致性缺陷。","reason":"数据库从业者可借此理解AI应用对数据持久化的新需求，以及Serverless数据库在Agent场景中的适配逻辑。","category":"platform","category_label":"AI 数据平台","vendors":["PingCAP","TiDB"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产","知识与上下文"],"use_cases":["Agent构建"],"decision_concerns":["成本与性能","可靠性与评估"]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-08-07T21:00:00+08:00","first_seen":"2026-08-12T13:40:18.379118+08:00","original_url":"https://www.pingcap.com/blog/serverless-database/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"ddcb4a5b6b52","zh_title":"开源数据层将赢得AI未来","zh_summary":"AI改变了重写应用代码的成本，但持久化数据层的迁移成本依然高昂。封闭数据平台会让路线图、定价和部署选择受制于人，而开源数据层能保留关键控制力。TiDB 已被 Kimi、Pinterest、Atlassian、Dify 等用于生产负载，证明开放性与规模化并非取舍。","reason":"数据从业者可借此评估AI时代数据平台选型，理解开放数据层在避免锁定和保持控制权方面的战略价值。","category":"platform","category_label":"AI 数据平台","vendors":["PingCAP","TiDB"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["可维护性与复用"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-06T03:20:17+08:00","first_seen":"2026-08-12T13:40:18.379118+08:00","original_url":"https://www.pingcap.com/blog/open-source-data-layer-ai/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"a09c3221be78","zh_title":"使用Debezium CDC将实时数据迁移到TiDB","zh_summary":"本文介绍如何利用Debezium CDC将实时数据迁移到TiDB，覆盖从MySQL、PostgreSQL、Oracle等数据库捕获变更并流式写入TiDB的架构。方案通过Debezium读取源库事务日志，将变更事件发送到Kafka，再经JDBC sink写入兼容MySQL协议的TiDB。初始快照与持续流式同步相结合，实现近零停机迁移。文中以PostgreSQL为例验证了“任意源→Kafka→TiDB”的可复用管道。","reason":"数据从业者可借鉴Debezium+TiDB构建跨数据库实时同步与迁移管道，理解CDC在数据接入与持续同步中的实践价值。","category":"platform","category_label":"AI 数据平台","vendors":["PingCAP","TiDB","Debezium","Apache Kafka"],"topics":["实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["场景与方案"],"use_cases":["数据接入"],"decision_concerns":["可靠性与评估"]},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-08-04T21:00:17+08:00","first_seen":"2026-08-12T13:40:18.379118+08:00","original_url":"https://www.pingcap.com/blog/debezium-cdc-to-tidb/","items":[{"source":"TiDB Blog"}],"source_badge":"RSS"},{"event_id":"477745cf963d","zh_title":"ElectricSQL加入Databricks，为AI Agent沙箱带来WASM Postgres","zh_summary":"PGlite开发方ElectricSQL加入Databricks，双方计划把WASM Postgres带入AI Agent沙箱。每个Agent可在自己的运行环境中获得低延迟本地数据库，并通过同步引擎连接中心状态。这让Databricks的Postgres能力从湖仓进一步延伸到边缘和Agent运行时。","reason":"AI Agent正在形成独立的运行时数据层，PGlite与实时同步的组合值得数据平台和Agent基础设施团队持续关注。","category":"agent","category_label":"Data Agent","vendors":["Databricks","ElectricSQL"],"topics":["Data Agent","平台AI化"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"heat":44,"quality_score":88,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-08-12T08:20:00+08:00","discovery_source":"X·@databricks","importance":88,"shelf":"news","pinned":false,"published":"2026-08-11T15:00:00+08:00","first_seen":"2026-08-12T08:20:00+08:00","original_url":"https://www.databricks.com/blog/electric-joins-databricks-bring-wasm-postgres-ai-agent-sandboxes","items":[{"source":"Databricks Blog"},{"source":"X 线索·@databricks"}],"source_badge":"RSS"},{"event_id":"44517f2e6a68","zh_title":"Databricks称专用数据Agent比通用Coding Agent更准更省","zh_summary":"Databricks用401个真实内部任务对Genie Code与三款通用Coding Agent进行评测。厂商公布的结果显示，Genie Code准确率为76.6%，平均每项任务成本0.55美元，正确答案成本不到最接近对手的一半。该结果属于Databricks自建基准，应结合评测设计审慎解读。","reason":"这是少见的专用数据Agent与通用Coding Agent成本、准确率同场比较，能帮助团队理解语义搜索和企业上下文的实际价值。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["Data Agent","平台AI化"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"heat":42,"quality_score":84,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-08-12T08:20:00+08:00","discovery_source":"X·@databricks","importance":84,"shelf":"news","pinned":false,"published":"2026-07-23T23:33:58+08:00","first_seen":"2026-08-12T08:20:00+08:00","original_url":"https://www.databricks.com/blog/why-frontier-data-agent-outperforms-general-coding-agents-quality-and-cost","items":[{"source":"Databricks Blog"},{"source":"X 线索·@databricks"}],"source_badge":"RSS"},{"event_id":"87c9acba5c38","zh_title":"pg_clickhouse 0.10增强查询下推，TPC-H Q17降至37毫秒","zh_summary":"pg_clickhouse 0.10加入相关子查询下推、重构的纯C驱动和更多聚合函数。在22个TPC-H查询中，已有16个可完整下推；官方给出的Q17结果从32.7秒缩短到37毫秒。版本继续强化PostgreSQL查询ClickHouse时的透明加速能力。","reason":"查询下推覆盖率直接决定PostgreSQL与ClickHouse组合方案的实用性，这次升级包含可量化的性能进展。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse","PostgreSQL"],"topics":["实时分析","平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":40,"quality_score":80,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-08-12T08:20:00+08:00","discovery_source":"X·@ClickHouseDB","importance":80,"shelf":"news","pinned":false,"published":"2026-08-12T01:40:40.622000+08:00","first_seen":"2026-08-12T08:20:00+08:00","original_url":"https://clickhouse.com/blog/pg_clickhouse-whats-new-july-2026","items":[{"source":"ClickHouse Blog"},{"source":"X 线索·@ClickHouseDB"}],"source_badge":"RSS"},{"event_id":"e7420873acde","zh_title":"ClickHouse成立基础数据库研究团队ClickHouse Labs","zh_summary":"数据库研究者Andy Pavlo加入ClickHouse并担任数据库研究副总裁，ClickHouse同时成立ClickHouse Labs。团队计划把研究成果放到ClickHouse、PostgreSQL等真实负载中验证，并以论文和开源成果的形式公开。","reason":"数据库厂商重新建立面向基础研究的长期团队，可能影响查询优化、存储引擎和AI时代数据库架构的演进。","category":"platform","category_label":"AI 数据平台","vendors":["ClickHouse","PostgreSQL"],"topics":["数据人","平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":43,"quality_score":86,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-08-12T08:20:00+08:00","discovery_source":"X·@ClickHouseDB","importance":86,"shelf":"news","pinned":false,"published":"2026-08-03T21:33:44.646000+08:00","first_seen":"2026-08-12T08:20:00+08:00","original_url":"https://clickhouse.com/blog/andy-pavlo-joins-clickhouse","items":[{"source":"ClickHouse Blog"},{"source":"X 线索·@ClickHouseDB"}],"source_badge":"RSS"},{"event_id":"2a6cb6153284","zh_title":"MotherDuck用Guides补齐Data Agent看不到的业务上下文","zh_summary":"MotherDuck推出Guides，把指标定义、表关系、历史迁移和业务例外等说明作为可查询、可版本化的上下文保存在数仓中。Agent在执行查询或构建数据任务时，可以按需发现并加载这些说明，减少仅凭schema猜测业务语义造成的错误。","reason":"企业数据Agent的核心瓶颈正在从SQL生成转向上下文治理，Guides提供了一个接近‘数仓内技能文件’的实现样本。","category":"agent","category_label":"Data Agent","vendors":["MotherDuck","DuckDB"],"topics":["Data Agent","语义层"],"product_ids":["motherduck"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"heat":41,"quality_score":82,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-08-12T08:20:00+08:00","discovery_source":"X·@motherduck","importance":82,"shelf":"news","pinned":false,"published":"2026-08-11T22:03:01+08:00","first_seen":"2026-08-12T08:20:00+08:00","original_url":"https://motherduck.com/docs/key-tasks/guides/","items":[{"source":"MotherDuck Docs"},{"source":"X 线索·@motherduck"}],"source_badge":"RSS"},{"event_id":"74499ad15c94","zh_title":"数据Agent将制造机器查询洪峰，传统数仓面临新负载","zh_summary":"MotherDuck认为，LLM最近半年才开始较稳定地生成SQL，数据Agent并没有错过窗口。新的挑战是Agent会在很短时间内发起大量探索和验证查询，而传统数仓主要围绕人工交互与定时任务设计，需要重新考虑并发、隔离和成本控制。","reason":"这条观点把讨论从‘Agent能否写SQL’推进到‘数据平台能否承受机器规模的查询行为’，对容量规划很有启发。","category":"agent","category_label":"Data Agent","vendors":["MotherDuck"],"topics":["Data Agent","平台AI化"],"product_ids":["motherduck"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"heat":40,"quality_score":79,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-08-12T08:20:00+08:00","discovery_source":"X·@motherduck","importance":79,"shelf":"news","pinned":false,"published":"2026-08-06T08:00:00+08:00","first_seen":"2026-08-12T08:20:00+08:00","original_url":"https://www.infoworld.com/article/4203157/agents-are-coming-for-data-just-slowly.html","items":[{"source":"InfoWorld"},{"source":"X 线索·@motherduck"}],"source_badge":"RSS"},{"event_id":"7dc53089a3b8","zh_title":"dbt State让Fivetran单个模型运行时间从40分钟降到40秒","zh_summary":"dbt Labs 宣布 dbt State 正式 GA，可在 dbt 平台中追踪每个模型的逻辑或上游数据是否变化，若未变化则复用上次构建结果。文中对比两个每小时运行的相同 dbt 作业，启用 dbt State 的作业几乎全部模型被标记为“reused”，复用模型的测试也不再运行。dbt 平台每天构建超过 2200 万个模型，其中多数在上游未变化时仍会重建；dbt State 支持按模型粒度跨作业复用，以降低数据仓库成本。它通过比较节点的编译 SQL 逻辑和上游数据新鲜度，决定复用、重建等操作。","reason":"dbt 用户与数据平台团队应关注该能力，因为它直接优化数仓构建成本与运行效率，并涉及模型逻辑和上游数据变化检测下的复用机制。","category":"platform","category_label":"AI 数据平台","vendors":["dbt Labs","Fivetran"],"topics":["平台AI化"],"product_ids":["dbt"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["数据资产"],"use_cases":["生产评估与运营"],"decision_concerns":["成本与性能","准确性与语义一致性"]},"heat":44,"quality_score":80,"trend_score":15,"star":true,"editorial_pick":true,"curated_at":"2026-08-12T08:20:00+08:00","discovery_source":"X·@getdbt","importance":80,"shelf":"news","pinned":false,"published":"2026-08-10T23:10:28+08:00","first_seen":"2026-08-12T08:20:00+08:00","original_url":"https://www.getdbt.com/product/dbt-state","items":[{"source":"dbt"},{"source":"X 线索·@getdbt"},{"source":"dbt Blog"}],"source_badge":"RSS"},{"event_id":"7e23299ee03d","zh_title":"DuckDB引入异步I/O，适应云端远程数据读取","zh_summary":"DuckDB计划从v2.0开始支持Parquet和CSV异步读取，解决EC2/S3等计算存储分离环境中工作线程等待网络I/O的问题。随着DuckDB从本地SSD查询扩展到远程数据湖和服务化场景，异步请求有望更充分利用带宽。","reason":"异步I/O是DuckDB从嵌入式本地分析走向远程数据湖负载的重要架构变化，值得湖仓与查询引擎团队关注。","category":"platform","category_label":"AI 数据平台","vendors":["DuckDB"],"topics":["湖仓","实时分析"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":41,"quality_score":83,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-08-12T08:20:00+08:00","discovery_source":"X·@duckdb","importance":83,"shelf":"news","pinned":false,"published":"2026-07-31T08:00:00+08:00","first_seen":"2026-08-12T08:20:00+08:00","original_url":"https://duckdb.org/2026/07/31/asynchronous-io.html","items":[{"source":"DuckDB Blog"},{"source":"X 线索·@duckdb"}],"source_badge":"RSS"},{"event_id":"9653f52649c8","zh_title":"Tableau Agent进入Dashboard，提供受治理的对话式分析","zh_summary":"Tableau Agent in Dashboards为Dashboard使用者提供概览、图表洞察和自然语言问答。功能遵循现有权限、访问控制和行级安全规则，回答可以包含文本与表格，目标是让业务用户在不排队等待分析师的情况下继续深挖数据。","reason":"对话式分析正在从独立聊天框进入Dashboard主工作流，权限继承和受治理语义将成为ChatBI落地的关键。","category":"bi","category_label":"BI 与可视化","vendors":["Tableau","Salesforce"],"topics":["ChatBI","BI变局"],"product_ids":[],"focus":{"id":"ai-dashboard","label":"AI 看板","priority":4,"practical":true},"heat":40,"quality_score":81,"trend_score":7,"star":true,"editorial_pick":true,"curated_at":"2026-08-12T08:20:00+08:00","discovery_source":"X·@tableau","importance":81,"shelf":"news","pinned":false,"published":"2026-08-07T21:00:00+08:00","first_seen":"2026-08-12T08:20:00+08:00","original_url":"https://help.tableau.com/current/pro/desktop/en-us/dashboard_narratives_overview.htm","items":[{"source":"Tableau Help"},{"source":"X 线索·@tableau"}],"source_badge":"RSS"},{"event_id":"65c35101abc1","zh_title":"跨100+ AWS账户的集中CloudTrail监控","zh_summary":"AWS Big Data Blog 介绍了如何在 Amazon OpenSearch Service 上构建集中式 CloudTrail 监控方案，使用 Terraform 管理全栈资源。该方案每日处理 200 GB 日志，覆盖 100+ AWS 账户，提供自动化威胁检测，并支持按需生成 SOC 2、PCI DSS 和 HIPAA 合规报告，同时为四个团队提供隔离的权限访问。","reason":"面向大规模多云账户的安全日志集中分析与合规报告实践，对数据平台建设者具有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon OpenSearch Service"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-08-11T23:48:03+08:00","first_seen":"2026-08-12T00:33:30.539407+08:00","original_url":"https://aws.amazon.com/blogs/big-data/centralized-cloudtrail-monitoring-across-100-aws-accounts/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"dfb9071b69e0","zh_title":"BigQuery支持Gemini 3.1 Flash Lite与3.5 Flash GA模型","zh_summary":"BigQuery宣布正式支持gemini-3.1-flash-lite和gemini-3.5-flash GA模型，适用于us、eu及global多区域端点。用户可在所有生成式AI函数中使用这些模型。该更新源自BigQuery官方发布说明。","reason":"数据从业者可在BigQuery内直接调用最新Gemini模型进行生成式分析，降低AI功能集成成本。","category":"platform","category_label":"AI 数据平台","vendors":["Google","BigQuery","Google Cloud"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":67,"quality_score":70,"trend_score":65,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"news","pinned":false,"published":"2026-10-13T15:00:00+08:00","first_seen":"2026-08-12T00:33:30.539407+08:00","original_url":"https://docs.cloud.google.com/bigquery/docs/release-notes#August_10_2026","items":[{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"},{"source":"Google BigQuery Release Notes"}],"source_badge":"RSS"},{"event_id":"ba8377c644db","zh_title":"扩展Claude能力：Skills与MCP协同构建智能体","zh_summary":"Anthropic于2025年12月19日发布文章，介绍如何结合Skills和MCP构建遵循工作流程的智能体。MCP负责连接外部工具，Skills则教导Claude如何高效使用这些工具。例如，通过MCP连接Notion并添加会议准备技能，Claude能自动提取相关页面并按团队标准格式化文档。文章还发布了Agent Skills开放标准，旨在实现跨平台的可移植性。","reason":"该文章详细解析了MCP与Skills的互补关系，对构建代理的数据平台和Agent开发者具有直接指导意义。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent","平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["可维护性与复用","用户采用与业务价值"]},"heat":38,"quality_score":85,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2025-12-19T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/extending-claude-capabilities-with-skills-mcp-servers","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"679beacaaad9","zh_title":"Anthropic Claude Code团队详解Agent循环工程入门","zh_summary":"Claude Code团队在官方博客中定义了agentic循环的概念，即智能体重复工作周期直至满足停止条件，并依据触发方式、停止条件、所用Claude Code原语和适用任务类型，将循环分为基于turn、目标驱动、基于时间和主动式等几类。文章提供了从turn-based循环逐步过渡到更复杂循环的实践指南，并讨论了在管理token消耗的同时保证代码质量的策略。作者强调并非所有任务都需要复杂循环，建议从最简单的方案开始，有选择地使用这些模式。","reason":"Agent循环设计是构建高效Data Agent的关键工程实践，来自Claude Code团队的官方定义与选型指南对数据领域的智能体开发有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["可靠性与评估","成本与性能"]},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-06-30T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/getting-started-with-loops","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"99fb5308d61b","zh_title":"Agent Harness设计：3种模式发挥Claude智能","zh_summary":"Anthropic的Chris Olah指出，生成式AI系统如Claude更多是“生长”而非“构建”，因此构建应用时对模型的假设会过时。本文介绍Agent Harness（模型外的软件脚手架，包括循环、工具、上下文管理和护栏）设计的三种模式：利用模型已知能力、审视可停止的步骤、谨慎设置边界。例如Claude 3.5 Sonnet在SWE-bench Verified上仅凭bash和文本编辑器工具达到49%的成绩，说明应让模型主导而非依赖复杂工具。","reason":"数据从业者构建Data Agent或ChatBI时可借鉴Agent Harness设计原则，平衡智能、延迟与成本，提升Agent构建效率。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"ai-platform","label":"AI 数据平台","priority":1,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["成本与性能"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-04-02T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/harnessing-claudes-intelligence","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"c07808b097ea","zh_title":"Anthropic如何保障AI原生软件开发流程的安全","zh_summary":"Anthropic副CISO Jason Clinton撰文介绍其安全工程团队如何保障由AI主导的软件开发流程安全。目前Anthropic合并的代码中约80%由Claude编写，超过一半代码由内部版本的Claude Tag合并，人类工程师负责指导、设定意图并最终批准。文章详述了针对受攻击或提示注入的智能体、供应链和依赖投毒等威胁的安全策略，包括将安全左移并与开发阶段全面整合等。","reason":"本文为数据与AI领域的技术实践，展示了在AI生成代码占比极高的环境下如何实施安全控制，对构建和维护AI Agent相关数据平台的安全体系有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","权限与治理"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["权限与安全","可靠性与评估"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-07-21T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/how-anthropic-secures-its-ai-native-software-development-lifecycle","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"0d666c08c243","zh_title":"Anthropic营销运营团队用Claude Cowork自动化报告和活动构建","zh_summary":"Anthropic的营销运营团队成员Ian Chan和Annabel Custer分享了如何利用Claude Cowork自动化跨平台的报告和活动构建工作。Ian过去每周花费一到两天时间整理营销指标周报，现在通过工作流压缩至数小时。Annabel过去需要依次点击Salesforce、HubSpot等工具设置活动，现在也大幅节省时间。节省的时间让他们更专注于赋能、验证以及依赖的数据和流程。","reason":"展示了营销运营中报告与活动构建的自动化实践，对关注AI在数据分析和运营场景落地的从业者具有参考价值。","category":"insight","category_label":"AI分析","vendors":["Anthropic","Claude","Salesforce","HubSpot"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","Agent接口与工具"],"use_cases":["数据发现与搜索","Agent构建"],"decision_concerns":["用户采用与业务价值"]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-07-08T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/how-anthropics-marketing-operations-team-uses-claude-cowork-to-automate-reporting-and-campaign-builds","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"b74623b58b77","zh_title":"Claude Code在大型代码库中的最佳实践","zh_summary":"本文是Anthropic关于Claude Code在大型代码库中部署最佳实践的系列文章之一，介绍了在数百万行级单体仓库、遗留系统及多仓库架构中成功采用Claude Code的模式。文章指出Claude Code像软件工程师一样通过文件系统遍历、grep等方式导航代码，无需建立代码库索引。内容涵盖配置、工具链和组织结构上的可复用模式，适合考虑采用Claude Code的工程团队参考。","reason":"内容聚焦AI编程工具在大型工程代码库的落地实践，与本站数据领域五个范畴均不直接相关。","category":"product","category_label":"数据产品","vendors":["Anthropic","Claude"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":10,"quality_score":23,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":23,"shelf":"evergreen","pinned":false,"published":"2026-05-14T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/how-claude-code-works-in-large-codebases-best-practices-and-where-to-start","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"8e5b13e46c10","zh_title":"领先零售商如何将AI试点扩展为企业级转型","zh_summary":"多数企业AI计划起步强劲但停滞迅速，本文基于对零售组织的研究，揭示了领先者与落后者的差别。报告指出三步骤区分AI领导者，来自与可见ROI组织的合作。零售商面临利润薄、客户期望高、自动化压力与服务质量平衡等挑战，PwC报告88%高管计划增加AI投资。Shopify部署Claude驱动Sidekick，将自然语言请求转为ShopifyQL查询；L'Oréal构建以Claude为核心的多Agent系统，为150国44,000员工提供洞察和可视化。","reason":"为数据从业者提供零售业AI规模化的具体实践与路径，涵盖Agent在业务场景中的落地参考。","category":"insight","category_label":"AI分析","vendors":["Anthropic","Claude"],"topics":["销售增长","客户运营"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文"],"use_cases":["数据发现与搜索"],"decision_concerns":["用户采用与业务价值"]},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-01-28T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/how-leading-retailers-are-turning-ai-pilots-into-enterprise-wide-transformation","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"98d739699601","zh_title":"Claude Code 高级配置：如何设置 Hooks","zh_summary":"本文介绍如何配置 Claude Code 的 hooks 来自动化重复任务、强制执行项目规则、并在编码会话中注入动态上下文。文章面向已有基础的开发者，涵盖八种 hook 类型、适用场景、配置方法和调试技巧。Hooks 是自定义 shell 命令，可在特定事件前后自动执行，如文件写入或提示提交时。","reason":"该内容涉及 AI 编码工具的高级配置，与数据领域无关。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":0,"quality_score":1,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":1,"shelf":"evergreen","pinned":false,"published":"2025-12-11T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/how-to-configure-hooks","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"735b02a1d1e4","zh_title":"如何为Claude创建Skills：步骤与示例","zh_summary":"本指南介绍了如何为Claude创建自定义Skills，通过SKILL.md文件扩展其能力。文中强调了Skills能编码机构知识、标准化输出并处理复杂多步骤工作流。提供了创建Skills的5个步骤，包括明确核心需求、编写名称、描述和指令等。此外，还提供了技能创建者模板和手动创建方法，并说明了触发机制的关键要素。","reason":"为AI Agent定制技能是数据从业者提升ChatBI/Data Agent效能的关键实践，本文提供了具体方法论和步骤，具有实操价值。","category":"insight","category_label":"AI分析","vendors":["Anthropic","Claude"],"topics":["ChatBI","Data Agent"],"product_ids":[],"focus":{"id":"ai-analysis","label":"AI 数据分析","priority":3,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["可维护性与复用","用户采用与业务价值"]},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2025-11-19T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/how-to-create-skills-key-steps-limitations-and-examples","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"dc870b113f92","zh_title":"如何无缝集成API：构建弹性集成的系统方法","zh_summary":"本文介绍了如何在API集成中处理认证过期、速率限制和第三方API Schema变化等常见故障。作者主张从生产事故驱动的被动调试转向系统性集成规划，提前识别风险点并建立弹性的错误处理机制。文章列举了令牌过期、速率限制等典型故障模式，并提供了构建可靠集成的建议。","reason":"该文专注于通用API集成工程实践，没有涉及数据垂直领域（Data Agent、数据平台、BI、数据产品、AI分析）的具体应用或案例。","category":"platform","category_label":"AI 数据平台","vendors":["Anthropic","Claude"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["可靠性与评估"]},"heat":4,"quality_score":10,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":10,"shelf":"evergreen","pinned":false,"published":"2025-10-27T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/integrate-apis-seamlessly","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"15799bed7e83","zh_title":"Agentic coding简介：从代码补全到自主执行任务","zh_summary":"Claude官方博客介绍agentic coding，即AI从自动补全转向自主执行多步开发任务。系统通过读取整个代码库、运行测试并迭代直至满足需求，而非仅基于编辑器可见代码预测下一个片段。文章回顾了AI编程工具从代码预测、补全到智能体的演进过程，并对比了传统辅助与自主代理的区别。","reason":"本文介绍Claude Code的agentic coding概念，但属于AI辅助编程领域，与本站数据Agent、数据平台等五个覆盖领域无关。","category":"platform","category_label":"AI 数据平台","vendors":["Anthropic","Claude"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":14,"quality_score":30,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":30,"shelf":"evergreen","pinned":false,"published":"2025-10-30T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/introduction-to-agentic-coding","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"c759c2325b45","zh_title":"构建Claude Code的经验：我们如何使用skills","zh_summary":"Anthropic分享了在Claude Code中构建和扩展数百个内部技能的经验。技能是代理可以发现的指令、脚本和资源的文件夹，而不仅仅是markdown文件。通过梳理内部技能，他们发现技能分为九类，最佳技能应清晰归类。文中还讨论了如何构建技能、何时分享等最佳实践。","reason":"该文深入探讨了AI代理中技能的设计与组织，对数据Agent的构建与复用具有指导意义，适合数据从业者参考。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["可维护性与复用"]},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-06-03T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/lessons-from-building-claude-code-how-we-use-skills","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"fe9ed70935a3","zh_title":"构建Claude Code的教训：提示缓存至关重要","zh_summary":"Anthropic分享了在Claude Code中优化提示缓存的实践，包括如何有效组织提示、使用工具以及分层压缩。Claude Code的整个框架都围绕提示缓存构建，高缓存命中率可降低成本并提高速率限制。文章强调了静态内容在前、动态内容在后的提示结构，以最大化缓存命中，并指出了如时间戳或工具排序变动等可能破坏缓存的问题。","reason":"该文章聚焦于AI Agent技术实现中的提示缓存优化，与本站五大领域中的Data Agent相关，但话题更偏向模型推理性能而非数据场景，故不收录。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":14,"quality_score":30,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":30,"shelf":"evergreen","pinned":false,"published":"2026-04-30T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/lessons-from-building-claude-code-prompt-caching-is-everything","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"06ffc5e72f47","zh_title":"Anthropic发布Claude Cowork企业部署指南","zh_summary":"Anthropic发布新指南，介绍如何用Claude Cowork在企业中部署代理式AI。Claude Cowork将Claude Code的代理能力带至桌面端，支持本地文件、Slack、Google Drive等集成，并可结合Claude for Excel和PowerPoint处理跨表格和幻灯片的流程。指南包括五级成熟度模型、试点评估方法、六个月的推广路线图，以及Anthropic财务、法务、销售和产品团队的实际用例。","reason":"数据从业者可了解AI代理在办公场景的落地方法，尤其是Claude Cowork如何通过插件和技能适配企业数据工作流，对部署类似数据Agent有参考价值。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["用户采用与业务价值"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-04-29T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/new-guide-deploying-claude-across-the-enterprise-with-claude-cowork","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"ccc4b7fc179e","zh_title":"克劳德代码入职：17年开发经验的启示","zh_summary":"Skyline实验室的Brendan通过将Claude Code视为新开发者来入职，成功管理了庞大的代码库。他将AI上下文移入独立仓库，使用CLAUDE.md文件和技能指导Claude，显著降低了调试开销。Claude Code完成了搁置一年的项目，自动化了教程图像和每日测试摘要，实验室开发者现在主要指导Claude而非亲自编码。","reason":"展示了如何通过结构化上下文和技能引导AI编码工具，解决大型项目中的技术债务和开发效率问题，对数据平台和Agent构建有借鉴意义。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["可维护性与复用"]},"heat":38,"quality_score":85,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":false,"published":"2026-04-28T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/onboarding-claude-code-like-a-new-developer-lessons-from-17-years-of-development","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"f5f77fd32d06","zh_title":"智能体时代的产品开发实践","zh_summary":"Anthropic 的 Claude Managed Agents 产品经理 Jess Yan 分享了在智能体时代如何利用自身产品来提升产品开发效率。她指出，使用 Claude 可以快速验证想法、自动化工作流，并将更多时间投入到产品设计上。通过 Claude Code，她能够在预发布版本上快速构建并测试 API 原型，从而及时调整抽象设计。这些实践改变了产品经理的日常工作方式，并为类似工作流提供了可借鉴的模式。","reason":"该文章提供了在AI智能体时代进行产品开发的实际案例和方法，对数据Agent产品经理及开发团队具有借鉴意义。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["可维护性与复用"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-04-29T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/product-development-in-the-agentic-era","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"4842d16865d3","zh_title":"AI指数时代的产品管理：Claude Code产品主管分享","zh_summary":"Claude Code的产品主管Cat Wu分享了在模型智能快速演进下，产品管理团队如何调整工作流程和路线图。她指出传统产品管理方法假设项目开始时与结束时技术能力大致相同，但指数级改进的模型打破了这一假设，团队需要围绕快速实验、持续发布并加码有效策略的新节奏进行重组。文章提及从2024年10月的Claude Sonnet 3.5到2025年6月的Opus 4，再到Opus 4.6，模型能力不断提升，使得现场演示成为可能。","reason":"文章揭示了AI产品管理在模型快速迭代下的新方法论，对数据Agent和平台产品经理具有借鉴意义。","category":"product","category_label":"数据产品","vendors":["Anthropic","Claude"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":["用户采用与业务价值"]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-03-19T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/product-management-on-the-ai-exponential","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"15663b335fc2","zh_title":"运行AI原生的工程组织","zh_summary":"Anthropic的Claude Code团队分享了向AI原生工程组织转型的经验。文章指出，当智能体编程消除了实际输入代码的需求后，瓶颈从编写代码转移到了验证、代码审查和安全上。团队重写了规划流程，转向及时规划，减少预先设计和产品评审。文章探讨了人类如何跟上AI生成代码的审查速度等问题。","reason":"该文章聚焦于AI原生工程组织的管理实践，而非数据领域的具体产品、技术或分析，因此对数据从业者的直接参考价值有限。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":9,"quality_score":20,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":20,"shelf":"evergreen","pinned":false,"published":"2026-06-03T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/running-an-ai-native-engineering-org","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"dcb97c54e8f3","zh_title":"如何在工程组织规模化代理式编码","zh_summary":"文章基于对不同行业工程团队的观察，指出成功采用代理式编码的关键在于执行、工作流变更和技能发展，而非特定工具。建议从20-50名超级用户试点开始，通过黑客马拉松启动推广，并利用内部专家扩展。强调使用CLAUDE.md文件记录项目约定，并给出衡量成功的指标如Sprint吞吐量、任务完成时间和开发者满意度。","reason":"面向工程管理者的深度实践指南，提供了可操作的规模化策略和衡量指标，对希望推广Data Agent和ChatBI的团队同样有借鉴意义。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":["Agent构建"],"decision_concerns":["用户采用与业务价值","可维护性与复用"]},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2025-10-15T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/scaling-agentic-coding","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"f7606c6bf1ab","zh_title":"像智能体一样思考：Claude Code工具设计实践","zh_summary":"本文由Anthropic团队分享其在构建Claude Code时设计智能体工具的经验。作者提出一个框架：为智能体选择工具应基于其自身能力，并通过观察和实验来理解其能力。他们通过三个迭代版本开发了AskUserQuestion工具以改进启发式提问，用Task工具替换TodoWrite以更好地支持子代理协作，并用Grep工具替代RAG以让Claude自主搜索代码库。文章强调随着模型能力增强，曾经有用的工具可能成为限制，需要不断重新审视。","reason":"文章提供了数据Agent（如ChatBI/Text-to-SQL）工具设计的实战方法论，对构建智能分析代理的开发者具有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["可靠性与评估","用户采用与业务价值"]},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":false,"published":"2026-04-10T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/seeing-like-an-agent","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"63587adfe4de","zh_title":"Claude Code指南：CLAUDE.md、技能、钩子与子代理的使用时机","zh_summary":"本文是Anthropic官方发布的Claude Code使用指南，详细解释了规则（Rules）、技能（Skills）、钩子（Hooks）和子代理（Subagents）四种配置机制的区别与适用场景。规则可配置路径作用域以按需加载，技能通过斜杠命令或自动匹配触发，子代理则用于分工协作。文中给出具体建议，例如跨领域约束用路径作用域规则，过程性指令（如部署流程）应放在技能中。","reason":"对于构建和优化数据Agent的开发者，掌握Claude Code的配置机制有助于提升Agent开发的效率与可维护性。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["可维护性与复用"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-06-18T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/steering-claude-code-skills-hooks-rules-subagents-and-more","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"909af102152a","zh_title":"Claude Code子代理的使用指南，提升复杂任务效率","zh_summary":"本文介绍了Claude Code中的子代理功能，子代理拥有独立上下文窗口，可并行执行任务，仅返回结果，避免主会话上下文膨胀。文中讨论了何时使用子代理、如何调用以及何时不值得使用，并提及了内置子代理类型如计划代理和探索代理。适合处理复杂多步项目中的旁支任务，但需权衡额外开销。","reason":"为Data Agent构建与使用提供实践指导，帮助数据从业者优化代理工作流，提升效率与成本控制。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["成本与性能"]},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-04-07T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/subagents-in-claude-code","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"670aa1988526","zh_title":"AI原生初创企业建设手册","zh_summary":"Anthropic发布了一份关于构建AI原生初创企业的手册，将创业生命周期分为创意、MVP、发布和规模化四个阶段，包含目标、退出标准、常见失败模式和AI驱动的练习。手册分享了验证问题假设、利用AI进行客户发现、防止AI生成代码累积技术债务等实践，并提到使用Claude系列工具及Ambral、Carta Healthcare等创始人的故事。","reason":"内容聚焦AI原生创业方法论，与数据平台或数据分析领域无直接关联，不属于本站覆盖范围。","category":"product","category_label":"数据产品","vendors":["Anthropic","Claude"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":9,"quality_score":20,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":20,"shelf":"evergreen","pinned":false,"published":"2026-05-14T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/the-founders-playbook","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"3576da62258e","zh_title":"Claude Code 会话管理与100万上下文实践","zh_summary":"Anthropic 发布了 /usage 命令，帮助用户了解 Claude Code 的使用情况，该功能源于与客户的多次对话。文章讨论了用户管理会话的多种方式，特别是在更新到100万上下文后，如何通过继续、回退、清空或压缩等操作优化上下文窗口使用。还介绍了上下文窗口、压缩和上下文腐烂的概念，并强调会话管理对体验的重要影响。","reason":"数据从业者使用 Claude Code 等 AI 编码工具时，上下文管理直接影响效率和质量，本文提供了实用指南。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["成本与性能"]},"heat":25,"quality_score":55,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":55,"shelf":"evergreen","pinned":false,"published":"2026-04-15T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/using-claude-code-session-management-and-1m-context","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"a9f36b216c3c","zh_title":"使用Claude Code：HTML的惊人有效性","zh_summary":"文章探讨了在Claude Code中使用HTML而非Markdown的优势，包括信息密度更高、视觉清晰易读、易于分享以及支持双向交互。作者认为HTML几乎可以高效表示所有信息，并建议将规范、报告等输出为HTML以便于阅读和分享。","reason":"该文章属于AI工具使用技巧，内容不直接涉及数据领域五个核心方向，相关性低。","category":"product","category_label":"数据产品","vendors":["Anthropic","Claude"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":9,"quality_score":20,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":20,"shelf":"evergreen","pinned":false,"published":"2026-05-20T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/using-claude-code-the-unreasonable-effectiveness-of-html","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"dee09fbc2a06","zh_title":"使用CLAUDE.MD文件：为你的代码库定制Claude Code","zh_summary":"本文介绍了CLAUDE.md配置文件，它能为Claude Code提供项目特定的上下文，如架构、编码标准和常用命令，从而减少重复解释。文章示例了配置文件的结构，并提供了最佳实践。然而，内容围绕AI编程助手，与数据领域（数据分析、数据库、数据基础设施等）无直接关联。","reason":"内容聚焦AI编程助手的配置，不涉及数据产品、数据分析或相关基础设施，不符合五类领域任一范畴。","category":"product","category_label":"数据产品","vendors":["Anthropic","Claude"],"topics":[],"product_ids":[],"focus":{"id":"ai-analysis","label":"AI 数据分析","priority":3,"practical":true},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":[],"use_cases":[],"decision_concerns":[]},"heat":9,"quality_score":20,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":20,"shelf":"evergreen","pinned":false,"published":"2025-11-25T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/using-claude-md-files","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"6beb8036da98","zh_title":"用LLM保护源代码：Claude安全实践指南","zh_summary":"Anthropic分享了使用Claude Opus进行源代码安全扫描的实践指南，强调发现漏洞已可并行化，瓶颈转向验证、分类和修补。截至2026年5月22日，已披露1596个漏洞，仅97个被修补。文章详细介绍了威胁建模、沙箱、发现、验证、分类和修补六个步骤，并提供了配套代码库和技能。","reason":"该指南展示了如何将LLM应用于代码安全这一数据场景，提供了可操作的流程和方法，对数据团队构建AI代理有借鉴意义。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["ChatBI","Data Agent"],"product_ids":[],"focus":{"id":"ai-analysis","label":"AI 数据分析","priority":3,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["可靠性与评估"]},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-05-27T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/using-llms-to-secure-source-code","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"fc1ed813ad68","zh_title":"Thomson Reuters如何用Claude构建高风险专业AI","zh_summary":"Thomson Reuters在Claude平台分享为高风险专业场景构建AI的经验，涉及法律、税务等领域的AI应用实践，强调准确性与可靠性。文章探讨了如何将Claude集成到专业工作流中，并确保输出的可信度。这对数据与AI从业者理解专业领域AI落地具有参考价值。","reason":"展示了在专业高风险场景中构建AI的实践，对数据与AI从业者有借鉴意义。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["Agent接口与工具"],"use_cases":["Agent构建"],"decision_concerns":["准确性与语义一致性"]},"heat":29,"quality_score":65,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":65,"shelf":"evergreen","pinned":false,"published":"2026-07-08T08:00:00+08:00","first_seen":"2026-08-11T10:19:53.100342+08:00","original_url":"https://claude.com/blog/working-at-the-frontier-how-thomson-reuters-builds-ai-for-high--stakes-professional-work","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"c96797b511e6","zh_title":"如何在保留治理的同时将Genie Agents接地到结构化数据与文档","zh_summary":"Databricks介绍如何让Genie Agents同时基于结构化数据（如Managed Tables、Views、Metric Views等）和非结构化文件（Unity Catalog Volumes）进行分析与回答，而无需在系统间桥接数据。其治理核心在于Genie Agents以最终用户身份运行，Unity Catalog通过AIM、对象权限、ABAC、行过滤器和列掩码自动执行权限控制。这样单一Agent即使访问大量数据，也不会向错误的人泄露错误信息，且无需额外设置即可继承现有治理体系。","reason":"数据从业者应关注如何在构建Data Agent/ChatBI时同时支持多模态数据接入，并沿用统一目录的权限治理，避免Agent成为新的数据安全缺口。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["Data Agent"],"product_ids":["databricks-genie"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"heat":37,"quality_score":82,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-08-11T07:08:50+08:00","first_seen":"2026-08-11T08:31:56.608473+08:00","original_url":"https://www.databricks.com/blog/how-ground-genie-agents-both-structured-data-and-documents-without-losing-governance","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"1a5723bd7772","zh_title":"CWT如何将AI分析转化为数百万美元资产","zh_summary":"ThoughtSpot高级副总裁James Smith撰文介绍CWT的AI分析转型实践。CWT曾是传统BI架构，依赖Cognos和静态PDF，后采用ThoughtSpot和Snowflake，实现超过10万用户使用实时对话式洞察。其分析能力在CWT被收购时被母公司明确视为核心驱动因素。","reason":"真实客户案例展示了从传统BI向AI驱动分析升级的路径，以及数据产品如何成为企业收购中的核心资产。","category":"bi","category_label":"BI 与可视化","vendors":["ThoughtSpot","Snowflake"],"topics":["数据人"],"product_ids":["thoughtspot"],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-11T03:16:26.868598+08:00","first_seen":"2026-08-11T03:16:26.868598+08:00","original_url":"https://www.thoughtspot.com/blog/how-cwt-drives-value-with-thoughtspot-and-snowflake","items":[{"source":"ThoughtSpot Blog"}],"source_badge":"RSS"},{"event_id":"852499f0cb49","zh_title":"Epic Games如何调优OpenSearch支撑Fortnite分析","zh_summary":"Epic Games与AWS合作，对其Amazon OpenSearch Service集群进行优化，用于Fortnite游戏遥测数据的存储与分析。团队通过调整实例规格、重新平衡分片、优化索引映射以及升级引擎和Graviton版本，在降低运营成本的同时显著提升了查询延迟和吞吐量。该实践支撑了数十亿级遥测事件的处理，帮助Epic识别玩法趋势并辅助实时运营决策。","reason":"聚焦游戏数据分析场景下的OpenSearch调优实践，涉及大规模遥测处理、查询性能与成本优化，对数据平台从业者有直接参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":["实时分析","数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":false,"published":"2026-08-11T00:26:32+08:00","first_seen":"2026-08-11T01:38:20.381714+08:00","original_url":"https://aws.amazon.com/blogs/big-data/how-a-team-at-epic-games-tuned-amazon-opensearch-service-for-fortnite-analytics/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"9e059ac6ed28","zh_title":"Fivetran用AI构建状态页，替换6.5万美元SaaS","zh_summary":"Fivetran的两名工程师使用AI编码代理，在约4个月内设计、构建并上线了公司公开状态页的替代方案，替代了每年花费6.5万美元的Atlassian Statuspage。该系统现服务约2.6万名通知订阅者。文章详细介绍了实际成本、有效做法以及过程中出现的失误。","reason":"Fivetran作为数据基础设施厂商，公开分享用AI编码代理替代昂贵SaaS的工程实践，对数据从业者评估AI开发效率与成本控制有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran"],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":31,"quality_score":60,"trend_score":7,"star":false,"editorial_pick":true,"curated_at":"2026-08-12T08:20:00+08:00","discovery_source":"X·@fivetran","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-08-07T08:00:00+08:00","first_seen":"2026-08-10T23:14:17.717381+08:00","original_url":"https://www.fivetran.com/blog/we-built-our-own-status-page-with-ai-replacing-a-65k-saas-product","items":[{"source":"Fivetran Blog"},{"source":"X 线索·@fivetran"}],"source_badge":"RSS"},{"event_id":"036431034b26","zh_title":"构建医疗AI无需重建数据平台","zh_summary":"Fivetran与phData联合发文，指出充分利用AI需要自动化数据集成、上下文工程和代理化基础设施。文章提到37%的医院处于亏损或低利润运营，Fivetran的Epic EMR连接器帮助Inova Health和Sharp Healthcare等机构保持医疗数据AI就绪、合规且可访问。通过现代化的AI-ready数据基础，医疗机构可在临床文档、预测性患者监测、诊断影像等领域部署AI。","reason":"数据从业者可了解医疗行业如何在不重构数据平台的前提下，通过集成与治理能力支撑AI应用，是数据平台AI化的落地案例。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran","phData"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"ai-platform","label":"AI 数据平台","priority":1,"practical":true},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-08-10T08:00:00+08:00","first_seen":"2026-08-10T22:31:12.120461+08:00","original_url":"https://www.fivetran.com/blog/building-healthcare-ai-without-rebuilding-your-data-platform","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"f70f3be61bc1","zh_title":"数据分析Skill设计指南：从问题定义到流程拆解","zh_summary":"文章提出数据分析Skill本质是操作流程，需先明确问题、数据底表、操作步骤和输出成果，再借助Codex、Claude Code、Trae等AI工具生成。强调放弃通用Skill，按业务场景拆分，并给出指标异动、用户行为、效果评估、预测、策略优化五大问题类型及各自解法。最后指出AI不能替代数据治理和业务沟通，底表设计和业务假设仍需人工把控。","reason":"面向数据分析Agent的Skill设计方法论，帮助数据从业者系统化拆解分析场景并落地AI辅助分析。","category":"agent","category_label":"Data Agent","vendors":[],"topics":["Data Agent","数据人"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"heat":31,"quality_score":68,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":68,"shelf":"evergreen","pinned":false,"published":"2026-08-11T00:08:59+08:00","first_seen":"2026-08-10T16:44:59+08:00","original_url":"https://www.woshipm.com/share/6444173.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"c0107b7e1677","zh_title":"2026企业AI代理构建之道","zh_summary":"Anthropic联合研究机构调查超500名技术领导者，发现57%的组织已部署多阶段工作流AI代理，81%计划在2026年应对更复杂用例。近90%组织用AI辅助开发，60%将数据分析和报告生成列为最高影响用例。","reason":"直接展示企业级Data Agent在数据分析与报告生成场景的落地数据，帮助数据从业者把握趋势。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2025-12-09T08:00:00+08:00","first_seen":"2026-08-10T16:04:16.947568+08:00","original_url":"https://claude.com/blog/how-enterprises-are-building-ai-agents-in-2026","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"11bd570decd5","zh_title":"银行目标部门分析筛选：乙方视角的部门墙拆解","zh_summary":"本文从层级与部门双维度切入银行客户分析，拆解公司业务部、风险管控部、科技子公司等典型组织的职能、KPI与预算逻辑。提出用六维框架（职能定位、核心KPI、典型动作、出入帐、产品匹配、生态补全缺口）精准定位目标部门。作者曾用该方法分析24个部门、上百种产品，发现4款产品打错部门、3个需求从未触达。该方法论可平移至电网、医院等大型ToB组织。","reason":"面向数据产品厂商的银行客户销售方法论，帮助数据从业者理解客户决策链条与预算入口，精准切入金融科技项目。","category":"product","category_label":"数据产品","vendors":[],"topics":["数据人"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":28,"quality_score":62,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":62,"shelf":"evergreen","pinned":false,"published":"2026-08-10T23:08:37+08:00","first_seen":"2026-08-10T15:14:37+08:00","original_url":"https://www.woshipm.com/share/6436415.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"b07c642afcbe","zh_title":"Hebbia如何用Claude打造滴水不漏的金融尽职调查AI","zh_summary":"Hebbia为金融机构构建AI尽职调查软件，客户覆盖Top50资产管理公司中超过三分之一及顶级投行和律所。其meta-prompting技术将自然语言请求转化为提示，由Claude逐步执行。在最新测试中，Claude Fable 5取得了研究团队记录的最大准确率提升，并能追踪此前模型遗漏的复杂查询。创始产品经理Divya Mehta约一半时间用于服务核心客户。","reason":"金融尽职调查涉及海量文档与多步推理，Hebbia的meta-prompting实践展示了如何利用大模型降低漏查风险，对构建分析型Data Agent有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude","Hebbia"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-07-13T08:00:00+08:00","first_seen":"2026-08-10T10:34:20.934560+08:00","original_url":"https://claude.com/blog/working-at-the-frontier-how-hebbia-builds-ai-for-financial-diligence-that-cant-miss-a-detail","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"07887457a24c","zh_title":"多智能体协调五种模式及选用时机","zh_summary":"Anthropic 发布博客文章，介绍多智能体协调的五种模式：生成器-验证器、编排者-子智能体、智能体团队、消息总线、共享状态。文章强调从最简单模式开始，根据问题演进。适合已决定使用多智能体系统的团队参考。","reason":"多智能体协调是 Data Agent 领域的核心工程问题，本文提供了可操作的模式选择框架，帮助数据从业者设计分析 Agent 的协作架构。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":38,"quality_score":75,"trend_score":7,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":false,"published":"2026-04-10T08:00:00+08:00","first_seen":"2026-08-10T09:48:06.984083+08:00","original_url":"https://claude.com/blog/multi-agent-coordination-patterns","items":[{"source":"Claude 官方博客"},{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"cbaf1f7bd561","zh_title":"2026年提示工程最佳实践 | Claude by Anthropic","zh_summary":"Anthropic团队在Claude官方博客发布2026年提示工程最佳实践指南。文章归类为Agents，指出提示工程是构建更好AI输出的关键，并与上下文工程加速融合。相比含糊的提示，经过精心设计的提示能将目标一次到位，减少多轮澄清成本。文章提供了从日常简单习惯到复杂项目高级方法的实用技巧。","reason":"提示工程是构建Data Agent、ChatBI等数据应用的底层能力，掌握Anthropic团队的方法论有助于提升数据产品的交互效果与准确率。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2025-11-10T08:00:00+08:00","first_seen":"2026-08-10T09:48:06.984083+08:00","original_url":"https://claude.com/blog/best-practices-for-prompt-engineering","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"d17e13a7ceb3","zh_title":"用MCP构建可达生产系统的Agent","zh_summary":"Anthropic官方博客探讨如何让Agent连接外部生产系统，总结直接API调用、CLI与MCP三种主流路径。文章指出，直接API调用在集成数量增多后会面临M×N集成难题，而MCP作为通用协议层，能减少定制化成本，因此成为生产级Agent落地的关键方向。","reason":"MCP是Data Agent连接数据平台与外部系统的关键协议，数据从业者需要理解其技术选型与集成模式。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2026-04-22T08:00:00+08:00","first_seen":"2026-08-10T09:48:06.984083+08:00","original_url":"https://claude.com/blog/building-agents-that-reach-production-systems-with-mcp","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"1f6b975a6a4f","zh_title":"MCP是什么？连接AI与世界的开放协议","zh_summary":"Model Context Protocol（MCP）是连接AI助手与外部工具的开放标准，被誉为“LLM的USB-C”。它让Claude等AI助手无需自定义集成即可访问数据与工具，替代手动复制粘贴上下文。本文介绍MCP的定义、价值与应用场景，值得数据从业者了解AI与数据工具集成的新范式。","reason":"MCP是AI与数据工具标准化连接的关键协议，直接影响Data Agent和AI数据平台的集成方式，数据从业者应尽早理解其原理与潜力。","category":"agent","category_label":"Data Agent","vendors":["Anthropic","Claude"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"heat":32,"quality_score":70,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":70,"shelf":"evergreen","pinned":false,"published":"2025-10-31T08:00:00+08:00","first_seen":"2026-08-10T09:13:24.703914+08:00","original_url":"https://claude.com/blog/what-is-model-context-protocol","items":[{"source":"Claude 官方博客"}],"source_badge":"官网"},{"event_id":"5f8de8bd22e1","zh_title":"OpenAI自研数据智能体：内部600PB数据查询从几天缩至几分钟","zh_summary":"OpenAI公开了其内部自建数据智能体的实践细节。该智能体为3500多名员工提供数据服务，覆盖7万个数据集、超过600PB数据。它将获取洞察的时间从几天缩短到几分钟，显著降低各职能部门的数据分析门槛。智能体结合Codex驱动的表格级知识与持续学习记忆，可执行端到端分析。","reason":"这是一线大模型公司内部数据智能体落地的一手案例，展示了Agent在超大规模数据平台上的真实路径，对数据团队和BI产品设计有参考价值。","category":"agent","category_label":"Data Agent","vendors":["OpenAI"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"heat":34,"quality_score":75,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":75,"shelf":"evergreen","pinned":true,"published":null,"first_seen":"2026-08-10T09:12:21.582276+08:00","original_url":"https://openai.com/zh-Hans-CN/index/inside-our-in-house-data-agent/","items":[{"source":"主编收录"}],"source_badge":"收录"},{"event_id":"c93bfa7909b8","zh_title":"Anthropic用Claude自动化95%数据分析查询","zh_summary":"Anthropic 官方博客介绍在 Slack 中通过 Claude Tag 实现自助式数据分析的实践。核心架构决策是将技能文件视为持续刷新的服务内容，因为数据模型一天可能变化多次，旧技能会导致自信的错误答案。Claude Tag 运行时挂载数据仓库的 skills/ 目录并在每次对话时重读。除知识技能外，还需补充分析师式的工作技能，才能回答“什么导致了下降”这类开放问题。","reason":"这一实践展示了数据代理在面对频繁变化的语义层时，如何通过动态技能文件保证准确性与可维护性，对关注 ChatBI/Data Agent 落地的从业者有直接参考价值。","category":"product","category_label":"数据产品","vendors":["Anthropic","Claude"],"topics":["ChatBI","Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["指标与语义","知识与上下文"],"use_cases":["指标问答","自助分析"],"decision_concerns":["准确性与语义一致性","可维护性与复用"]},"heat":42,"quality_score":85,"trend_score":7,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":true,"published":"2026-06-03T08:00:00+08:00","first_seen":"2026-08-10T09:10:55.713518+08:00","original_url":"https://claude.com/blog/how-anthropic-enables-self-service-data-analytics-with-claude","items":[{"source":"主编收录"},{"source":"Claude 官方博客"}],"source_badge":"收录"},{"event_id":"d4f17e123698","zh_title":"构建高效AI代理：Anthropic的实用指南","zh_summary":"本文是Anthropic基于与数十个团队的合作经验，分享构建LLM代理的实用建议。文章指出，最成功的实现往往采用简单、可组合的模式，而非复杂框架。Anthropic区分了工作流与代理，并强调在构建应用时应从最简单方案开始，仅在必要时增加复杂性。","reason":"一线经验总结，对AI代理开发具有直接指导意义，值得数据领域从业者参考。","category":"agent","category_label":"Data Agent","vendors":["Anthropic"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":42,"quality_score":85,"trend_score":7,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":true,"published":"2024-12-19T00:00:00+08:00","first_seen":"2026-08-10T01:31:34.077328+08:00","original_url":"https://www.anthropic.com/research/building-effective-agents","items":[{"source":"主编收录"},{"source":"主编收录"}],"source_badge":"收录"},{"event_id":"097d6cd340b4","zh_title":"Anthropic多智能体研究系统从原型到生产的工程实践","zh_summary":"Anthropic工程团队分享了构建Claude Research多智能体系统的历程与经验。该系统利用多个Claude代理并行探索复杂主题，解决了开放研究任务中无法预定义路径的难题。文章深入剖析了多智能体系统在协调、评估和可靠性方面面临的挑战，并总结了关键技术决策。","reason":"多智能体系统是数据代理领域的前沿方向，Anthropic的工程经验对构建同类系统具有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["Anthropic"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":35,"quality_score":78,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":78,"shelf":"evergreen","pinned":true,"published":"2025-06-13T00:00:00+08:00","first_seen":"2026-08-10T01:31:34.077328+08:00","original_url":"https://www.anthropic.com/engineering/multi-agent-research-system","items":[{"source":"主编收录"}],"source_badge":"收录"},{"event_id":"ac7c75fedd0b","zh_title":"一招教你鉴定真假Data Agent","zh_summary":"文章提出一套鉴别真假Data Agent的审查清单：真正的企业级Data Agent需同时满足语义层、目标驱动、证据链与自愈、权限治理、反馈沉淀五项要求。判断基准是它不能只是“会写SQL的聊天框”，必须回答理解数据、安全访问、可验证结果、沉淀资产四个问题。作者直言市场上八成产品只是NL2SQL套聊天框，用半小时逐项验证即可识别套壳。","reason":"数据从业者选型或评估Data Agent时，可参照这套清单快速识别套壳产品，避免被厂商的PPT和架构宣讲误导。","category":"agent","category_label":"Data Agent","vendors":[],"topics":["Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":true,"published":"2026-08-10T01:26:27.487315+08:00","first_seen":"2026-08-10T01:26:27.487315+08:00","original_url":"https://mp.weixin.qq.com/s/jc5hyDKwuDzTnycU6N1rRw","items":[{"source":"微信公众号"}],"source_badge":"RSS"},{"event_id":"3bb9e34e59c3","zh_title":"构建企业级数据分析助手：Data Agent开发实践","zh_summary":"阿里云DMS推出Data Agent for Analytics，定位企业级数据分析智能体，基于Agentic AI技术，帮助用户查数据、做分析、生成报告并深入洞察。文章从能力边界定义、技术内核、企业级能力三方面剖析其技术思考与实践，为开发者提供参考。","reason":"深度拆解企业级Data Agent的产品架构与落地实践，对ChatBI/分析Agent从业者具有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["阿里云"],"topics":["ChatBI","Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"heat":38,"quality_score":85,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":85,"shelf":"evergreen","pinned":true,"published":"2025-10-15T19:38:47+08:00","first_seen":"2026-08-10T01:26:27.487315+08:00","original_url":"https://developer.aliyun.com/article/1685078","items":[{"source":"主编收录"}],"source_badge":"收录"},{"event_id":"1526c962704f","zh_title":"Data Agent：超越BI与AI的边界","zh_summary":"文章梳理数据分析工具从Excel、BI到ChatBI的演进困局，指出传统BI与ChatBI仍是被动响应、答案导向，未能解决数据问题向业务问题的转化。火山引擎数智平台VeDI提出Data Agent概念，强调从“数据工具”升级为“数字专家”，实现从记录过去到理解现在、预测未来的跨越。","reason":"推荐理由：Data Agent是当前数据智能化的关键方向，火山引擎官方对BI与AI融合困境的剖析，可帮助从业者理解下一代数据分析产品的设计逻辑。","category":"agent","category_label":"Data Agent","vendors":["火山引擎"],"topics":["ChatBI","Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"heat":36,"quality_score":80,"trend_score":0,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":80,"shelf":"evergreen","pinned":true,"published":"2025-07-24T16:00:21+08:00","first_seen":"2026-08-10T01:26:27.487315+08:00","original_url":"https://developer.volcengine.com/articles/7530534221058211903","items":[{"source":"主编收录"}],"source_badge":"收录"},{"event_id":"36e5214115ac","zh_title":"RAG和Reference都叫知识库？搭Skill别选错","zh_summary":"本文用生活化类比拆解RAG与Reference两类AI知识库的本质区别：RAG是先搜后答的自动搜索引擎，Reference是按人定规则调用的手动文件柜。通过退货政策PDF案例，清晰对比了两者工作流程与适用场景，帮助数据从业者理解知识库底层机制与选型要点。","reason":"RAG与Reference是Data Agent落地中的常见概念，理解二者区别有助于数据从业者设计更可靠的Agent知识调用方案。","category":"agent","category_label":"Data Agent","vendors":[],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":20,"quality_score":45,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":45,"shelf":"evergreen","pinned":false,"published":"2026-08-09T23:08:53+08:00","first_seen":"2026-08-09T15:48:53+08:00","original_url":"https://www.woshipm.com/ai/6441990.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"63b7989f4b33","zh_title":"Stripe用图搜索与状态机自动化数据库修复","zh_summary":"Stripe工程团队近日分享了如何将全球基础设施建模为图，结合图搜索算法与状态机，自动计算并执行数据库事故修复方案。该方法旨在减少人工干预，提升数据库运维的自动化水平。","reason":"数据库基础设施的自动化修复是数据平台领域的重要实践，对关注数据运维与平台稳定性的从业者具有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":[],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-08-09T14:55:00+08:00","first_seen":"2026-08-09T14:55:00+08:00","original_url":"https://www.infoq.com/news/2026/08/database-remediation-graph/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"ed8330108532","zh_title":"金融监管Harness实践：知识与数据驱动Agent稳定运行","zh_summary":"中软融鑫总工程师于浩军在 AICon 2026 深圳站分享金融监管报送中的 AI Agent 实践。该场景要求数据零容错，97%准确率远远不够，通用大模型的幻觉与口径漂移是核心风险。方案用知识底座、数据底座、受控状态机和全链路可追溯四机制约束 Agent，目标是“宁可不答、不能答错”的确定性输出。适合 RegTech、金融 AI 平台和强合规 Agent 开发者参考。","reason":"强合规、零容错场景下如何约束 Agent 的语义、数据与推理路径，对 Data Agent 的可靠性、可追溯和落地设计有直接参考价值。","category":"agent","category_label":"Data Agent","vendors":["中软融鑫"],"topics":["Data Agent","风险管理"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"work_tags":{"taxonomy_version":"work-tags-v1","product_objects":["知识与上下文","指标与语义"],"use_cases":["Agent构建","生产评估与运营"],"decision_concerns":["准确性与语义一致性","可靠性与评估"]},"heat":41,"quality_score":82,"trend_score":7,"star":true,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":82,"shelf":"evergreen","pinned":false,"published":"2026-08-08T18:00:00+08:00","first_seen":"2026-08-08T18:00:00+08:00","original_url":"https://www.infoq.cn/article/hQp9boye2rpPH7ZWUvXL?utm_source=rss&utm_medium=article","items":[{"source":"InfoQ 中文"},{"source":"InfoQ 中文"}],"source_badge":"RSS"},{"event_id":"f4962a2fa921","zh_title":"AI秒级出报表，为何业务仍来不及？","zh_summary":"AI将报表生成提速到秒级，但业务链路中的等待可能让分析失去意义。SoFi的546个失败会话与Blend的新产品Autopilot Analytics Agent，共同指向一个被忽视的指标：行动窗口。文章建议从业务结果反推产品设计，用剩余窗口、Time to Intervention和窗口命中率重新定义数据产品优先级。","reason":"文章提出“行动窗口”这一数据产品设计新视角，结合SoFi与Blend案例，对数据从业者重新思考分析时效与业务干预价值有启发。","category":"product","category_label":"数据产品","vendors":["Blend","Glassbox"],"topics":["Data Agent","数据人"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"heat":32,"quality_score":72,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":72,"shelf":"evergreen","pinned":false,"published":"2026-08-08T23:08:30+08:00","first_seen":"2026-08-08T15:37:30+08:00","original_url":"https://www.woshipm.com/ai/6442626.html","items":[{"source":"人人都是产品经理"}],"source_badge":"RSS"},{"event_id":"460d5283bb04","zh_title":"开放数据基础设施需用上下文工程统一数据用例","zh_summary":"Fivetran产品布道师Charles Wang撰文指出，单一事实来源不仅来自数据集中化，还必须从数据中构建上下文。他结合Fivetran与dbt Labs的托管数据湖服务（MDLS），说明开放表格式、持续同步与元数据发布如何支撑统一架构。文章强调AI系统缺乏隐性知识，必须通过上下文工程让信息显式、结构化、可信且可检索。他将上下文工程分为四类需求，并首先提及语义与血缘。","reason":"数据从业者需关注如何将统一数据架构与AI系统对齐，上下文工程正成为语义层与Data Agent落地的关键实践。","category":"platform","category_label":"AI 数据平台","vendors":["Fivetran","dbt Labs"],"topics":["语义层","湖仓"],"product_ids":["dbt"],"focus":{"id":"semantic-layer","label":"语义层","priority":2,"practical":true},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-08-07T08:00:00+08:00","first_seen":"2026-08-07T23:06:58+08:00","original_url":"https://www.fivetran.com/blog/open-data-infrastructure-needs-context-engineering-to-unify-data-use-cases","items":[{"source":"Fivetran Blog"}],"source_badge":"RSS"},{"event_id":"05b5c328b16d","zh_title":"Databricks谈大规模AI编码成本管理","zh_summary":"Databricks博客指出，AI编码工具虽能带来数量级效率提升，但成本指数增长不可持续。为兼顾广泛访问与成本可控，他们与Stripe、Coinbase、Uber、Ramp等企业交流，总结出多项成本管理技术，并开源了Omnigent和Unity AI Gateway等关键组件。","reason":"数据从业者可从头部数据平台的实际经验中，了解AI编码及Agent场景下的成本控制方法，对构建数据Agent和AI数据平台有直接借鉴意义。","category":"platform","category_label":"AI 数据平台","vendors":["Databricks"],"topics":["平台AI化"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-08-07T19:50:39+08:00","first_seen":"2026-08-07T19:50:39+08:00","original_url":"https://www.databricks.com/blog/managing-ai-coding-costs-scale","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"9f1a279db0dc","zh_title":"Databricks解读AI助手：从SQL生成到数据治理","zh_summary":"Databricks博客介绍了企业级AI助手的技术架构，涵盖大语言模型、检索增强生成和智能体框架。文章强调深度集成数据目录与治理策略的重要性，并援引市场数据称2025年全球AI助手市场规模为191亿美元，预计2035年达1141亿美元。该文对数据团队评估ChatBI与分析Agent具有参考价值。","reason":"文章来自Databricks官方博客，直接面向企业数据团队的AI助手能力构建，涉及SQL生成、仪表板构建与数据治理，是Data Agent与AI数据平台交叉领域的关键实践参考。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["ChatBI","Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-08-07T19:44:24+08:00","first_seen":"2026-08-07T19:44:24+08:00","original_url":"https://www.databricks.com/blog/what-is-an-ai-assistant","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"08162567f084","zh_title":"什么是Agentic Workflows？Databricks解读智能代理工作流","zh_summary":"Agentic workflows是AI驱动的流程，智能代理通过推理、工具使用和反馈的持续循环，自主规划、执行并优化多步骤任务。与传统自动化不同，代理在运行时动态调整策略并选择工具，而非遵循固定脚本。企业采用这类工作流可提升效率与扩展性，但需配合强治理、生产级基础设施和明确的业务目标。本文来自Databricks博客，是理解Data Agent落地模式的关键参考。","reason":"Agentic Workflows是Data Agent（分析代理）的核心运行范式，数据从业者需理解其机制以设计自主数据分析流程。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-08-07T05:36:15+08:00","first_seen":"2026-08-07T05:36:15+08:00","original_url":"https://www.databricks.com/blog/agentic-workflows","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"d42105556279","zh_title":"什么是工具调用？Databricks解读AI Agent核心机制","zh_summary":"工具调用（Tool Calling）是AI模型与外部工具、API和系统交互的机制，使聊天机器人进化为能执行真实操作的AI Agent。Databricks在博客中详解了其工作流程，并介绍Agent Bricks平台提供受治理的工具调用构建环境，原生支持Model Context Protocol（MCP）与Unity Catalog治理。","reason":"这是数据领域厂商Databricks对AI Agent关键技术的官方解读，数据从业者需理解工具调用如何连接模型与企业数据系统。","category":"agent","category_label":"Data Agent","vendors":["Databricks"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-08-07T05:31:30+08:00","first_seen":"2026-08-07T05:31:30+08:00","original_url":"https://www.databricks.com/blog/what-is-tool-calling","items":[{"source":"Databricks Blog"}],"source_badge":"RSS"},{"event_id":"a64173b0e40c","zh_title":"SageMaker Unified Studio与Lake Formation实现湖仓细粒度访问控制","zh_summary":"AWS官方博客介绍如何结合IAM Identity Center、Lake Formation基于标签的访问控制（TBAC）以及SageMaker Unified Studio的信任身份传播，为大规模企业湖仓构建自动化的最小权限访问治理架构。方案使用CDK部署，通过LF-Tags对数据分类，将IAM Identity Center组映射到标签策略，并在查询时跨分析引擎强制执行权限，解决表级权限手动管理带来的权限漂移与审计困难问题。","reason":"数据平台治理团队可参考该架构，利用标签与身份中心自动化的细粒度权限控制，降低湖仓规模扩大后的合规风险与运维成本。","category":"platform","category_label":"AI 数据平台","vendors":["AWS"],"topics":["湖仓"],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-08-07T00:17:59+08:00","first_seen":"2026-08-07T00:17:59+08:00","original_url":"https://aws.amazon.com/blogs/big-data/scaling-fine-grained-access-control-for-enterprise-lakehouse-using-sagemaker-unified-studio-and-aws-lake-formation/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"017baad77d72","zh_title":"Amazon MWAA与Airflow 3.0实现事件驱动跨账户编排","zh_summary":"AWS大数据博客介绍了如何在Amazon MWAA上使用Airflow 3.0构建事件驱动的跨账户管道编排。传统跨环境协调依赖轮询或传感器，存在延迟和可靠性问题。通过Airflow 3.0的基于资产的调度和Asset Watchers，结合Amazon SQS作为消息代理，可实现近实时触发，将编排延迟从分钟级降至秒级，并减少worker资源消耗。","reason":"数据工程师可了解如何在多账户MWAA环境中用Airflow 3.0和SQS替代轮询，提升管道响应效率与可靠性。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-08-07T00:16:39+08:00","first_seen":"2026-08-07T00:16:39+08:00","original_url":"https://aws.amazon.com/blogs/big-data/event-driven-pipeline-orchestration-with-amazon-mwaa-and-airflow-3-0/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"ae39e628c113","zh_title":"七招控制Snowflake CoCo AI成本","zh_summary":"Snowflake CoCo能将自然语言转化为实际工作，自动运行SQL、执行多步骤流程并在每轮调用大模型，token消耗会直接转化为credits费用。缺乏管控的团队可能迅速推高成本。Snowflake提供了从SQL、Snowsight或CoCo内部管理的完整成本控制体系，核心思路是三步：看清花费、优化默认运行配置、强制执行硬性限制。","reason":"数据从业者若使用CoCo这类分析Agent，必须理解其token计费模式与治理手段，避免AI成本失控，本指南给出了可落地的控制框架。","category":"agent","category_label":"Data Agent","vendors":["Snowflake"],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-08-06T23:29:35+08:00","first_seen":"2026-08-06T23:29:35+08:00","original_url":"https://medium.com/snowflake/7-ways-to-control-your-snowflake-coco-ai-spend-91fe829fce82?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"d461dff20c65","zh_title":"从分析工程师到上下文工程师","zh_summary":"dbt Labs 发文探讨企业 AI 部署从“为仪表盘建模数据”转向“为 Agent 建模上下文”。文章以自身为例，起初直接使用供应商 MCP 连接 Gong 等数据源，导致单次通话分析消耗高达 5 万 Token（约 0.25 美元），总数据量超 5 亿 Token。他们随后将原始数据摄入数仓并通过建模总结，以降低成本和掌控上下文层。","reason":"数据从业者应关注这一从 analytics engineering 到 context engineering 的范式转变，它直接关系到 AI Agent 如何高效、可控地连接企业数据资产。","category":"agent","category_label":"Data Agent","vendors":["dbt Labs","Gong","Salesforce"],"topics":["Data Agent","语义层"],"product_ids":["dbt"],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-08-06T21:00:00+08:00","first_seen":"2026-08-06T21:00:00+08:00","original_url":"https://www.getdbt.com/blog/from-analytics-engineer-to-context-engineer","items":[{"source":"dbt Blog"}],"source_badge":"RSS"},{"event_id":"4c9db581d5c6","zh_title":"从毫秒到微秒：Valkey架构模式助力现代AI数据层","zh_summary":"Dumanshu Goyal在演讲中讨论了如何为AI特征存储等低延迟工作负载优化数据层。他借鉴NASA航天飞机的经验，指出代理架构会带来隐藏CPU成本、尾部延迟升高和爆炸半径风险。他展示了直接访问型Valkey架构如何实现微秒级延迟、提升弹性并大幅降低基础设施成本。","reason":"Valkey作为Redis的开源替代，其架构模式直接关系到AI特征存储等数据基础设施的性能与成本，值得数据从业者关注。","category":"platform","category_label":"AI 数据平台","vendors":[],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-08-06T17:34:00+08:00","first_seen":"2026-08-06T17:34:00+08:00","original_url":"https://www.infoq.com/presentations/valkey-architecture-patterns/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"26c7d5691708","zh_title":"运行时无关的AI工作流：兼顾生产持久性与快速评估","zh_summary":"本文提出一种运行时无关的AI工作流模式，用于解决生产环境持久性与评估迭代速度之间的矛盾。通过将业务逻辑与运行环境解耦，同一套代码可以在生产与评估中运行，避免版本漂移。作者认为正确架构应让默认路径即最优路径。","reason":"该模式直接适用于Data Agent类应用的工程实现，帮助数据从业者构建既可靠又能快速迭代的AI分析工作流。","category":"agent","category_label":"Data Agent","vendors":[],"topics":["Data Agent"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":true},"heat":27,"quality_score":60,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":60,"shelf":"evergreen","pinned":false,"published":"2026-08-06T17:00:00+08:00","first_seen":"2026-08-06T17:00:00+08:00","original_url":"https://www.infoq.com/articles/ai-workflow-pattern/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering","items":[{"source":"InfoQ（AI/数据工程）"}],"source_badge":"RSS"},{"event_id":"04a9eab02673","zh_title":"掌握Snowflake RBAC：可扩展安全访问控制实战指南","zh_summary":"Snowflake中的RBAC设计往往始于简单授权，但一年后可能面临权限混乱、管道因孤立权限中断、ACCOUNTADMIN被用于日常任务等困境。Snowflake官方推荐采用3层角色架构来应对访问控制失控。本文提供了一套从核心原则到基础设施的RBAC构建、管理与加固框架，帮助数据团队实现可扩展且安全可控的访问权限。","reason":"数据从业者应关注如何系统化设计RBAC，避免权限膨胀与敏感数据暴露，确保数据平台的安全合规与可运维性。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-08-06T03:01:01+08:00","first_seen":"2026-08-06T03:01:01+08:00","original_url":"https://medium.com/snowflake/mastering-snowflake-rbac-a-practical-guide-to-scalable-secure-access-control-ba4c297b5ef5?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"5ce50d8a33b1","zh_title":"编码智能体的价值取决于它对数据的了解程度","zh_summary":"数据工程师尝试用编码智能体处理SQL时，确实能获得帮助：样板代码被削减，脚手架搭建更快。但一个更棘手的 frustration 是，智能体生成的代码看似正确——语法有效、符合惯例——却不适用于实际环境。它不知道哪些表是生产表、哪些 schema 受治理、RBAC 结构如何，导致产出仍需人工重塑。","reason":"数据从业者应关注：这直击 Data Agent 落地的核心瓶颈——智能体对数据环境上下文的理解不足，影响生成代码的可交付性。","category":"agent","category_label":"Data Agent","vendors":["Snowflake"],"topics":["Data Agent","语义层"],"product_ids":[],"focus":{"id":"data-agent","label":"数据 Agent","priority":0,"practical":false},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-08-05T04:56:04+08:00","first_seen":"2026-08-05T04:56:04+08:00","original_url":"https://medium.com/snowflake/your-coding-agent-is-only-as-useful-as-what-it-knows-about-your-data-7da50cd93a15?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"5a003e60d050","zh_title":"Snowflake可观测性成熟度三级框架解析","zh_summary":"Snowflake提出三级可观测性成熟度框架，帮助数据团队从“作业是否跑通”迈向数据和AI全链路可追溯。框架覆盖 freshness SLA、质量SLA、跨业务单元成本管理以及模型决策追踪，并强调Snowflake原生可观测性能力尚未被多数团队充分利用。适用于AI驱动的数据管道与行业合规场景。","reason":"数据从业者可借此审视自身可观测性建设阶段，理解Snowflake原生能力如何支撑AI管道治理与合规追溯。","category":"platform","category_label":"AI 数据平台","vendors":["Snowflake"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-08-05T03:01:01+08:00","first_seen":"2026-08-05T03:01:01+08:00","original_url":"https://medium.com/snowflake/a-three-level-observability-maturity-framework-for-snowflake-808e49b79e65?source=rss----34b6daafc07---4","items":[{"source":"Snowflake Engineering（Medium）"}],"source_badge":"RSS"},{"event_id":"663664951a62","zh_title":"Delivery Hero迁移至OpenSearch Service：径向搜索优化语义检索","zh_summary":"Delivery Hero自2024年起将语义搜索用于杂货垂直领域，从基于SpringBoot和Lucene 9.9的原型系统迁移至Amazon OpenSearch Service。他们采用径向搜索替代传统k-NN搜索，并与词法检索结合，构建高性能、低成本且灵活的混合搜索系统。该方案在Kubernetes上实现生产级部署，支持大规模产品相关性检索。","reason":"该案例展示了数据平台中语义搜索与向量检索的工程实践，对使用OpenSearch或关注检索基础设施的从业者具有参考价值。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon OpenSearch Service"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-08-04T23:55:01+08:00","first_seen":"2026-08-04T23:55:01+08:00","original_url":"https://aws.amazon.com/blogs/big-data/transforming-search-at-delivery-hero-a-migration-journey-to-opensearch-service-with-radial-search/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"},{"event_id":"5f584be1ab5d","zh_title":"Amazon Redshift跨区域灾难恢复策略解析","zh_summary":"AWS官方博客介绍了Amazon Redshift跨区域灾难恢复（DR）的核心概念、需求评估框架，并深入探讨了三种主要DR策略：Active-Passive、Active-Active和混合方法。文章针对每种策略详细说明了架构、权衡、实施指导和成本考量，帮助企业根据工作负载做出明智决策。现代企业越来越依赖Redshift处理关键分析负载，多区域DR已成为合规与业务连续性的重要要求。","reason":"数据平台工程师和架构师需了解Redshift跨区域容灾设计，以保障分析业务连续性与合规性。","category":"platform","category_label":"AI 数据平台","vendors":["AWS","Amazon Redshift"],"topics":[],"product_ids":[],"focus":{"id":"other","label":"其他数据动态","priority":5,"practical":false},"heat":23,"quality_score":50,"trend_score":0,"star":false,"editorial_pick":false,"curated_at":null,"discovery_source":"","importance":50,"shelf":"evergreen","pinned":false,"published":"2026-08-04T00:22:56+08:00","first_seen":"2026-08-04T00:22:56+08:00","original_url":"https://aws.amazon.com/blogs/big-data/amazon-redshift-multi-region-disaster-recovery/","items":[{"source":"AWS Big Data Blog"}],"source_badge":"RSS"}]}