marklogic
Here are 115 public repositories matching this topic...
Thank you for submitting an issue!
If this is a bug, please use the bug template below. If this is an enhancement request, please use the RFE template below. Before submitting your issue, please do us a favor and search currently open issues. If your issue already exists, please make a comment there advocating your issue be addressed sooner.
Bug Template
The issue
Short des
-
Updated
May 29, 2019 - JavaScript
The link in the JavaDoc comments for PojoQueryBuilder:
Is generating a broken link pointing to appendix B of the Rest Developer's guide in the JavaDocs.
Several possible ways:
- using mlpm directly (not convenient as you need to specify port,user,password
- using roxy deploy modules (need to uncomment deploy_packages in deploy_modules section of deploy/app_specific.rb)
- using roxy deploy packages (works out of the box)
[Swagger](http://swagger.io/) is a standard for documenting the function of rest interfaces. It would be nice to be able to auto-generate the swagger files from annotations in the XQuery functions. These annotations could be placed along side the current RXQ annotations.
We would need a report that generated the swagger docs for each REST endpoint.
I am glad to help out on this.
-
Updated
May 4, 2017 - TypeScript
-
Updated
Jun 25, 2020 - Java
-
Updated
Jun 16, 2020 - Java
This is something of a catch-all to replace #83 as we are not following the original sprints
Would we be better off moving the documentation out of the code and into the Wiki tab?
Copied from marklogic-community/ml-gradle#525 . Something in the set of Database Java classes isn't happy about that XML, need to figure out the issue and hopefully it's just a simple tweak to those classes so that the XML is unmarshalled correctly.
Add support for running MarkLogic Roxy/Unit tests.
-
processor.test-- API -
processor.impl.roxy.test-- https://github.com/marklogic-community/roxy -
processor.impl.roxy.test-- https://github.com/marklogic-community/marklogic-unit-test
NOTE: Both roxy and marklogic-unit-test provide the same test API.
-
Updated
Apr 15, 2020 - Java
-
Updated
Jun 26, 2020 - Python
When creating a query, if you specify a document by clicking the Browse MarkLogic button, an error is displayed when there really isn't one. Note: it doesn't prevent you from continuing, but rather is visible when there isn't really an error and might be confusing to a user.
To recreate:
- Click "Edit Config" from the top nav bar
- Click the "Create a Query" button
- Click the "Choose a repr
Clicking on the trash icon should always clear the search
Sid reported:
- search for "GEM"
- click on a demo tile for detail view
- from detail view, click trash icon —> it goes back to 3 results
- i can't get out of the search and "Show all demos" button doesnt work
I think the issue may be that the SearchModel service is not accessible from the detail controller. We may need to inject it
Once the compiler is ready (well it could be possible now as well to be honest), we can (if there is demand for), create Graphs to design REST Extensions to serve data. We can use those graphs to generate REST Extensions. Investigate whether there is demand for this.
Some ideas:
An Input block with GET/POST/PUT/DELETE output node.
An output node with Content/StatusCode/StatusMessage.
marklogic-spring-boot (1.0.0-rc)
When I click on a facet it turns it into the following search
{"range-constraint-query":{"constraint-name":"accountId","range-operator":"EQ","value":["4"],"range-option":[]}}]}}that causes the following error:
REST-INVALIDPARAM Found search:value but expected seach:range-option*
If I re-arrange to:
{"range-constraint-querIn the documentation for Matching Options here:
https://marklogic-community.github.io/smart-mastering-core/docs/matching-options/
the upper JSON example (under "Configuring Options") shows camelCase property names, e.g.:
scoring/add/propertyName
the lower JSON example (under "How Scoring Works") shows hyphenated property names, e.g.:
scoring/add/property-name
I believe camelCase
XCC Session.commit() has changed in 9.0.1 to now return boolean instead of being void.
XQSync Session implements the Session interface and must be updated in order to be compatible with XCC 9.0.1 (and later).
com.marklogic.ps.Session is not abstract and does not override abstract method commit() in
com.
As a developer
I want to Insert a fragment into an existing document
So that I can insert fragments on a batch of documenst
I created a version of this class but it needs to be updated: MarkLogicPatchItemWriter
Given the follow
Looking at the below lines of code the first argument being passed to assert-equal seems to be the message, when it should be the last argument passed to assert-equal:
-
Updated
Mar 27, 2020 - TSQL
Improve this page
Add a description, image, and links to the marklogic topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the marklogic topic, visit your repo's landing page and select "manage topics."
Is your feature request related to a problem? Please describe.
There are existing data in one DB which I need to harmonise and customise data using data hub.
What is the user-facing scenario that prompted this gap in functionality?
Existing data is in one DB, need the best practice to further harmonise and customise such data using data hub.
Describe the solution you'd like
A