Delta Share Connection in NSAW Loads Only Metadata (Tables + Columns but No Data)

Question

Hi everyone, I’m integrating Delta Sharing Connect with Oracle Analytics / NSAW, and the Delta Share connection behavior seems inconsistent with what NSAW is supposed to support. I’m hoping for some clarification or guidance. What I’m Doing I’m connecting to a 3rd party application to get data into NSAW using: Connection Type: Delta Share (Bearer Token) Authentication: Bearer token from application Delta Sharing Server URL: https://nvirginia.cloud.databricks.com/api/2.0/delta-sharing/metastores/a… This URL clearly uses the Unity Catalog–based Delta Sharing format (notice the /metastores/ portion). ✅What Works The connection saves successfully in NSAW . NSAW loads the share, including: Schema names Table names Column names ✅ There is no error on connection creation ✅ The credential works perfectly in Power BI, which loads data without issues. ❌ What Does NOT Work When I create a dataset in NSAW: All columns display “Missing or Null” Preview grid shows no rows When opening Edit Definition, no attributes appear at all It appears as if NSAW can see the table metadata but cannot read the underlying Parquet data files So, the connection is accepted, but data retrieval fails completely. My Questions: Does Oracle Analytics / NSAW currently support Unity Catalog–based Delta Sharing endpoints that contain /metastores/? If not, does NSAW require the classic Delta Sharing endpoint (ending in /delta-sharing/) only? Is the behavior I’m seeing — schema loads but data does not load — expected when using a Delta Share connect? Should I request 3rd party application to generate a classic-style Delta Share credential? dataset.png Environment Details NSAW Connection Type: Delta Share Authentication: Bearer Token Delta URL: Unity Catalog format (…/metastores/) Power BI: Works perfectly with the same token and URL NSAW: Loads metadata only, no data rows Any guidance from Oracle specialists would be extremely helpful, especially around Delta Sharing. Thank you,

Aljan Patrick Mendoza-Oracle · Accepted Answer

Hi User_DI6UJ, Let’s go through what’s officially documented about Oracle Analytics (OAC / NSAW) support for Delta Sharing and how it aligns with the behavior you’re currently observing. This should help you decide the best next step with your third-party data provider. 1. What the Oracle Documentation Says According to Oracle’s published guides on connecting to Delta Sharing sources in Oracle Analytics Cloud: * You can create a Delta Share connection by importing a JSON profile provided by your share provider. * Supported authentication methods include Bearer Token, which is also the method used by Databricks. * The documentation confirms that Oracle Analytics supports the Delta Sharing protocol for certain data sources (e.g., Autonomous Database) to visualize shared data. However, there’s no specific mention that Oracle Analytics or NSAW currently supports Unity Catalog–based Delta Sharing endpoints — that is, endpoints using URLs like: .../delta-sharing/metastores//... The documentation examples appear to reference only the classic Delta Sharing format (without the /metastores path). 2. Comparing This with What You’re Seeing Here’s what’s happening in your setup: ✅ You’re able to create the connection successfully. ✅ The credentials work, and metadata (schemas, tables, columns) loads correctly. ❌ When creating a dataset, no rows appear, and all columns show as “Missing or Null.” ❌ In Edit Definition, attributes do not appear. Your share provider uses a Unity Catalog–based URL (/metastores/). This indicates that the share is coming from Databricks Unity Catalog rather than a “classic” Delta Sharing endpoint. This aligns with a likely scenario: Oracle Analytics can connect well enough to read metadata, but not actual data — suggesting a compatibility gap with Unity Catalog shares, rather than a configuration issue on your end. 3. Answers to Your Specific Questions Does NSAW support Unity Catalog–based Delta Sharing endpoints? There’s no explicit documentation stating that NSAW supports these endpoints. Based on current information, such configurations are not officially confirmed as supported. Does NSAW require a “classic” Delta Sharing endpoint (without /metastores/)? Yes, the examples and references in Oracle’s materials point to the classic Delta Sharing pattern — typically ending in /delta-sharing/. This format appears to be what NSAW expects for full functionality. Is it expected that you can see metadata but no data? Yes — that’s consistent with an unsupported endpoint type. NSAW can connect and list metadata, but when it tries to read the data (Delta/Parquet files), it encounters an unsupported structure or format. Should you ask your third-party provider for a classic Delta Sharing credential? Yes, that would be the best next step. Ask your provider to generate a classic (open) Delta Sharing endpoint, without the Unity Catalog path structure. 4. Recommended Next Steps 1. Confirm with Oracle Support: Provide details such as your endpoint URL, authentication method, NSAW version, and the observed behavior (metadata visible but no data). Ask directly: “Does NSAW support Delta Sharing endpoints that use Unity Catalog (/metastores/)?” 2. Check with Your Data Provider: * Can they provide a classic-style Delta Sharing endpoint (ending in /delta-sharing)? * Confirm that the shared data is from standard Delta tables, not Unity Catalog–specific features. * Ask them to verify that the dataset includes actual rows when accessed via other tools (e.g., Power BI). 3. Test with a Known-Compatible Share: If possible, connect NSAW to a simpler, known-working Delta Sharing endpoint to confirm that the issue is indeed specific to Unity Catalog. 4. Review Logs / Version Info: Check NSAW logs or diagnostics for any warnings during dataset creation (e.g., “Unsupported table format”). Also, make sure your NSAW instance is running the latest release. 5. Summary Based on Oracle’s current documentation and your testing results: * NSAW supports Delta Sharing in general, but likely only the classic implementation. * Unity Catalog–based endpoints (/metastores/) are not yet confirmed as supported. * The behavior you’re seeing — metadata loads, but no data — matches what would happen if NSAW connected to an unsupported share type. Recommended Action: Ask your provider for a classic-style Delta Sharing endpoint and confirm compatibility with Oracle Support for Unity Catalog endpoints. Reference Documentations : https://docs.oracle.com/en/cloud/paas/analytics-cloud/acsds/connect-data-using-delta-sharing.html https://docs.oracle.com/en/middleware/bi/analytics-server/user-oas/connect-data-using-delta-sharing.html https://docs.oracle.com/en/cloud/paas/analytics-cloud/acsds/connect-data-using-delta-sharing.html