Once more into the breech #120
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was
linked to
issues
Nov 15, 2024
This was referenced Nov 15, 2024
Closed
jzonthemtn
reviewed
Nov 15, 2024
| * OpenSearch runs at http://localhost:9200 | http://chorus-opensearch-edition.dev.o19s.com:9200 | ||
| * OpenSearch Dashboards runs at http://localhost:5601/app/home | http://chorus-opensearch-edition.dev.o19s.com:5601/app/home | ||
| * OpenSearch Data Prepper runs at http://localhost:2021/ | http://chorus-opensearch-edition.dev.o19s.com:2021/ | ||
| * Quepid runs at http://localhost:3000 | http://chorus-opensearch-edition.dev.o19s.com:3000 | ||
| * Quepid runs at http://localhost:4000 | http://chorus-opensearch-edition.dev.o19s.com43000 |
There was a problem hiding this comment.
Wrong port number and missing :, i.e. :4000
jzonthemtn
reviewed
Nov 15, 2024
| 1. We have removed the kata `001_optimize_a_query.md` until SMUI is back. | ||
| 1. Waiting for OpenSearch 2.18 and UBI 2.18 with the fix for _msearch and pipelines. |
jzonthemtn
reviewed
Nov 15, 2024
There was a problem hiding this comment.
Yep, that's Javascript. :)
jzonthemtn
reviewed
Nov 15, 2024
| this.session_id = session_id; | ||
| this.client_id = client_id; | ||
| this.user_id = ''; | ||
| this.timestamp = Date.now(); |
There was a problem hiding this comment.
Does this match the specification?
strict_date_time in OpenSearch mapping. "yyyy-MM-ddTHH:mm:ss.SSSZ"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an attempt to simplify the front end build stack and see if we can't get more reliability.
Swap to port 3000. webpacker wants 3000, it insists on 3000, and no matter how much I try, if we aren't on 3000, we get weird websocket errors on port 3000 because it wants to do magic autoloading. So, gave up, accepted reality, and swapping the UI to port 3000 and let Quepid go live on 4000! This is the opposite of our other Chorus setups ;-).
I DO now have hot reload all working just fine.
Introduced
reactivesearchwhich is based on the Chorus ES edition. The core functionality works great.I am working on pure JS, no TypeScript, classes for UBI. I have in
./src/ubi/two classes:UbiEventandUbiEventAttributes. I am taking the opportunity to go through them and align them with the UBI 1.2 spec. Even making sure the order of the properties matches whats in the spec ;-).Right now I have Add to Cart working. It logs in the console the event. It does NOT publish that event anywhere. I figure I get the event's logging in the Console and then can add the sending of the events.