All Apps and Add-ons

Splunk DB Connect rising input creation problem

nembela
Path Finder

Hi,

I have the following problem with rising input creation. If I try to add the following query as a rising input, I receive an error:

SELECT *
FROM DIARY
WHERE DIARY_DATE > ?
AND TABLE_ID = 3
ORDER BY DIARY_DATE ASC

But the following query works:

SELECT *
FROM DIARY
WHERE DIARY_DATE > ?
ORDER BY DIARY_DATE ASC

"Step 4" fails when I click "next" on the "New input" screen, however the query runs fine. db_connect.PNG

According to the documentationit is permitted to use complex WHERE clauses:

"Use other advanced SQL features in the WHERE clause—for example a CASE statement."

Do you have any idea what went wrong here?

 

Thanks,

László

 

 

Labels (2)
Tags (2)
0 Karma
1 Solution

nembela
Path Finder

It turned out that it was a bug in DB connect (DBX-5327) that was fixed in 3.4.2

View solution in original post

0 Karma

nembela
Path Finder

It turned out that it was a bug in DB connect (DBX-5327) that was fixed in 3.4.2

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Under the heading of "dumb things to try that just might work" try swapping the order of the where clause.

SELECT *
FROM DIARY
WHERE TABLE_ID = 3
AND DIARY_DATE > ?
ORDER BY DIARY_DATE ASC
---
If this reply helps you, Karma would be appreciated.
0 Karma

nembela
Path Finder

Thanks for the suggestion. I tried to exchange the conditions but it did not help. The result was the same.

0 Karma
Get Updates on the Splunk Community!

AI for AppInspect

We’re excited to announce two new updates to AppInspect designed to save you time and make the app approval ...

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...